Roadmap
Installers, business context, the Control Surface and the technical outcome chain are built. OpenCLAW and Hermes have each passed a read only source assignment. Hermes installs twelve directly callable skills and binds specialist roles to native leaf sessions. Runtime parity remains partial because persistent named specialist agents and custom child roles do not exist there. Next come recurring runtime reports, secure private network access and defensible customer workflows.
OpenCLAW and Hermes have verified dry runs, ownership boundaries, updates, backups and controlled uninstalls. OpenCLAW installs twelve named agents. Hermes installs twelve named skills with their own slash commands and package pointers plus one team bundle.
Company, brand, offer, audiences, markets, goals and KPIs live in a versioned local workspace. New actions bind revision and hash. Light mode, dark mode and independent mobile layouts are implemented.
The loopback client reads WorkspaceContext V2, verifies revision and hash, creates local R2 draft assignments and reads sources, evidence and receipts. OpenCLAW reported runtime identity, sessions, capabilities and all twelve agent states with externalWrites 0. A recurring check in from normal runtime work remains open beyond this first technical report.
The orchestrator handed a revision and hash bound assignment to the Tech SEO specialist and synthesized the result. The run passed 22 checks without an external write.
marketingos-tech-seo triggered the live website read from its context-bound assignment, connected Action, Receipt and Evidence, and returned the synthesis. All 37 checks passed with externalWrites 0.
The Tech SEO path is proven with a real source, Action, Receipt and Evidence. Next come more specialist routes and recurring runtime reports. Persistent named specialist agents are not a Hermes promise because the runtime provides native leaf child sessions only.
The API and Control Surface expose complete provenance from a verified action through its receipt and observation to the outcome. The first real run confirms HTTP 200 and deliberately remains inconclusive about business impact.
The HTTPS private network design is built. Windows trust, the exact firewall rule and a real phone test remain.
The first reversible writes will only open with concrete scope, preview, approval, backup, restore path, receipt and post-change verification. Google, Bing, CMS, Git, tickets, outreach and budgets remain separate permission domains.
Pilot partners bring a domain, sources, accountable owners and a recurring marketing workflow. We measure handover quality, cycle time, errors, executions and later outcomes. Public product claims will come only from those observations.
Continue
OpenCLAW is installed and tested end to end. The guide explains the current path.