V1 launches
26·06·2026
We are building the website for MySynergy — a packaging company focused on packaging engineering, rapid prototyping and supplier coordination.
We run our own work on an agentic workflow, so the website goes up the same way the rest of our work does. The build log below this hero is everything we have shipped along the way.
000
Days
00
Hours
00
Minutes
00
Seconds
Counting down — Hong Kong time, UTC+8
13 entries · last updated 30 APR 2026
You found mysynergy.technology — our public face. We are about eight weeks out from V1 going live, so for now this is a countdown clock and a build log.
The countdown above is real. The build log below this card is what we have shipped so far. We would rather show what we are doing than tell you what we plan to do.
If you are a candidate for the 2026 internship: applications open 1 May 2026, 20:00 HKT.
The application portal — three candidate-facing stages plus an agent-API path — is one Cloudflare Worker, one set of static pages, and a few KV + R2 buckets. No app server. No operator standing by during traffic. The form itself does the receiving.
We tested every stage end-to-end today, including the 90 MB video upload path, the magic-link expiry, and the duplicate-submit gate (it returns a clean 410 instead of a duplicate row).
Applications open tomorrow night at 20:00 HKT. We will be quiet on the platform for the first 24 hours and watch what real candidates do with it.
Brand Guide v1.1 ships four format types programmatically — report, deck, memo, letter — from a single template stack. Pandoc + WeasyPrint + a Python-driven slide builder.
Anyone on the fleet can produce a polished client artifact in minutes, not hours, and it always looks like ours.
Stream D added an internship track: two builders, 90 days, Hong Kong + Shenzhen. Recruit, contract, train.
The recruitment build became a sub-program in its own right — pre-90 work to lock terms. The first concrete training track for the agentic-workflow operating model.
A Claude Code instance — Anthropic's Opus 4.7 model running through the Claude Code CLI — joined the fleet on 10 April.
Wrote what we would ship in 90 days as a Gantt: about 65 tasks across four streams and 9 keystone milestones. Stream A is acquisition (website, intake, client portal); B is build (intake-to-workflow, requirement brief, NPI execution, intelligence layer); C is coordination (sheet structure, KPI dashboards, supplier coordination); D is training and adoption (internship, onboarding, supplier training).
The countdown above this card targets the V1 launch milestone in stream A.
A compliance daemon — the relay enforcer — now watches every send across every channel: agent message, email, Smartsheet comment, Telegram, file delivery. Each send must match a pre-logged request.
Stage 1 is detect-only — when a byte goes out without authorization, the daemon flags it within seconds. Stage 2 is wired but not turned on; when armed, it kills the offending session and requires re-authorization.
The harness is the fleet's seatbelt.
Custom plugin tooling shipped that lets every OpenClaw agent post comments, attach files, and update rows on the workspace directly — no human relay.
Smartsheet API call → OpenClaw plugin → executed in seconds. Any agent that needs to log evidence or coordinate now does so on the same surface where its work is tracked.
Each agent now has a structured memory directory under tight rules: how memories are written, the four types (user, feedback, project, reference), when to update vs delete.
The memory governance doctrine sits beside the agents. They use it. They challenge it when it's wrong.
Each agent in the OpenClaw fleet got a mechanical capability profile — what files it can read, which tools it can call, what shell commands it can execute. The restriction lives in OpenClaw config and is enforced at the gateway.
Agents cannot escalate themselves. Privilege creep, automated.
Three more sheets joined the workspace within 48 hours: a daily journal, a master audit log, and a registry that tracks every internal markdown document by lifecycle state.
Smartsheet webhooks were added across the workspace so any change anywhere fires an event back into the OpenClaw gateway. Auditability becomes ambient.
The first internal Smartsheet went live. Every build since — software, doctrine, recruitment, even this build log itself — gets its own row, with a forced PLAN → BUILD → VERIFY shape and evidence attached as markdown.
About 80 builds have followed in the 5 weeks since. The team that produces them is a small fleet of AI agents — a mix of Claude Sonnet and OpenAI models — orchestrated by the OpenClaw gateway.
OpenClaw — the agent fleet's orchestration framework — came alive at 20:41 SGT on 5 March 2026.
Telegram joined the same evening as the founder's mobile channel: pings the fleet from anywhere, fleet pings back when something needs attention. From here on, the team runs from a phone.