Proof Ledger
On 10 July 2026, MarketingOS ran through two real runtime paths. OpenCLAW installed marketingos plus eleven named specialist agents. Hermes installed one orchestrator skill and eleven directly callable specialist skills. Its Tech SEO assignment bound the exact role contract to a native leaf session, read the live website with HTTP 200 and connected Action, Receipt and Evidence. Both source runs kept externalWrites at 0. They prove the technical chain, not rankings, demand, conversion or customer impact.
The installation manifest lists twelve MarketingOS agents in separated workspaces below ~/.openclaw/workspace-marketingos/. The existing main agent remained outside that namespace. SiteOne 2.5.1 was detected as the managed crawler.
The end-to-end run started the marketingos agent through the OpenCLAW runtime. Its workspace and MarketingOS skill loaded. Three read-only tool calls completed without failure. The receipt reports externalWrites 0.
The repository contains runtime manifests for OpenCLAW and Hermes, specialist roles, workflows, evidence files, execution packages, approval gates, receipts, outcome checks and claim gates. This proves that product components exist, but it does not prove customer value.
Both installers have a dry run, ownership guard, update, backup and controlled uninstall. The Hermes evidence used the real CLI from the official Hermes Agent 0.18.2. Foreign state remained unchanged.
The MarketingOS orchestrator started marketingos-tech-seo in its own child session and passed WorkspaceContext revision 2 with its hash. The specialist read the current website, created Action, Receipt and Evidence, and returned its analysis to the orchestrator. All 37 checks passed and externalWrites remained 0.
A new website read action under context revision 2 created a receipt and evidence. An observation and outcome were stored with complete provenance. HTTP 200 is proven. The outcome stays inconclusive with ten percent confidence because it says nothing yet about visibility, demand or customer impact.
Hermes loaded twelve named skills and the team bundle. delegate_task bound the installed Tech SEO role contract to a native leaf session. The assignment read the live website with HTTP 200 and connected Action, Receipt and Evidence. The source run passed 35 checks with externalWrites 0.
The specialist skills are installed and directly callable. Hermes does not turn them into persistent named specialist agents or custom child roles. The proven Tech SEO run covers this one path and does not automatically prove all eleven specialist routes.
A local dry run or receipt with externalWrites 0 does not prove a website change. Claims about time saved, visibility, leads or revenue require a real customer workflow, safe execution and measurements from the right period.
Continue
The roadmap separates the proven OpenCLAW and Hermes source runs from recurring operation, live writes and reliable impact measurement.