Trust & Transparency
What our products touch in your environment, what they don't, and how to remove them. This is for the reader who wants to understand before committing — you should.
What the QM wizard modifies — and what it doesn't
The setup wizard writes to four places: BOOT.md (per agent), INBOX.md (per agent), mission_manifest.json, and one openclaw.json config patch. Nothing else. No model assignments, no gateway config, no secrets. Every section the wizard adds carries an attribution block that identifies it, explains why it's there, links to the docs, and tells you how to remove it.
Scope boundary — what QM will never touch
QM never acquires gateway access. It cannot touch your credentials, secrets, model router config, or agent workspaces outside the INBOX and DONE protocol scope. When a fix requires gateway access, QM escalates to a human instead of acting. That's a design constraint, not a capability gap.
Attribution standard — every change is labeled
Every section QM writes into your files includes:
<!-- ACME QM: added by setup wizard --> <!-- Required for Quartermaster task tracking to function correctly. --> <!-- Reference: https://acmeagentsupply.com/docs/qm/done-protocol --> <!-- To remove: delete this section and uninstall QM. -->
You open your own files, you see exactly what changed, why it's there, and how to undo it. No unexplained modifications.
How to remove any ACME product cleanly
Uninstall is documented, not assumed. For QM: delete the attributed sections in BOOT.md and INBOX.md per agent, revert the openclaw.json config patch, and remove the mission files. Git history shows every change QM made — use it to verify the revert is complete. For other products: each has a documented removal path in the Reference Stack.
Questions about what a specific product touches? support@acmeagentsupply.com