1. Verify acquisition independently
The public customer path accepts only a successful marketingos.acquisitionReceiptVerification.v1 file from the independent Acquisition Bootstrap. A receipt taken from the same archive is not sufficient.
OpenClaw Founding Partner Preview
Attach OpenClaw to the installed MarketingOS product.
The direct Agent Pack installer is a Founding Partner Preview and maintainer path, not the official customer path. The later customer path starts with an independently verified Acquisition Receipt, installs the product through Install-MarketingOS, and then attaches OpenClaw through the stable MarketingOS-Manage launcher. The public signed release is not available yet.
2. Install MarketingOS as a product
Install-MarketingOS receives the absolute Acquisition Verification path. The Product Manager verifies the publisher and release bytes again, installs into the protected version store, and creates stable launchers. It does not run the product from the download or a source checkout.
3. Complete onboarding through the stable launcher
Start the installed version through Start-MarketingOS in the stable product path. Create the company, brand, offers, audiences, websites, goals and KPIs before attaching a runtime.
4. Attach OpenClaw with exact paths
The existing OpenClaw agent calls the stable MarketingOS-Manage launcher with attach-runtime, --runtime openclaw, and its absolute home, MarketingOS workspace root and CLI paths. The same contract applies through MarketingOS-Manage.sh on macOS and Linux.
5. Transactional validation instead of a dry run
The stable Product Manager has no --dry-run option for attach-runtime. It checks the acquisition binding, product state, runtime paths, ownership and SiteOne inside the transactional attachment and stops on failure.
6. Keep the direct installer in preview
Install-MarketingOS-Agent-Pack.cmd and Install-MarketingOS-Agent-Pack.sh belong to the Founding Partner Preview and maintainer diagnostics. They are not the later public customer entry point.
7. All eleven specialist routes are locally verified
The current isolated OpenClaw 2026.6.10 run installs the orchestrator and eleven specialists from the present source. Every route reads one synthetic .example source and produces a matching action, receipt and evidence record. SiteOne is available to every route. Fifty five invalid variants are rejected. externalWrites remains 0.
8. Keep lifecycle work in the installed product
Update, rollback, recovery and detach-runtime use the stable product launchers. Stable uninstall removes verified MarketingOS entries only. The existing main agent, foreign workspaces and other runtime data remain intact.
Continue
Review the boundaries before installation
The Proof Ledger shows the current 11 of 11 source record and separates it from the open signed customer release.