AdOS
One governed operating system for marketing work.
AdOS connects work and outcomes through shared identity and evidence. Current alpha: Google Ads read-only monitoring. Bucket creation is available; provider writes and rule changes are not. Workspace shell: Preview. Further capabilities: Planned.
Governed work
Provider reality
Measured outcomes
Learn more
- Identity and evidence
- Clients, brands, accounts, campaigns, and outcomes keep stable identity. Every number can name the evidence that explains it.
- Governed work
- Briefs, reviews, incidents, and launches become named jobs with owners, states, and receipts instead of scattered threads.
- Provider reality
- Discovery never implies authority. Assignment, capability observation, and approval are separate, explicit steps before anything is written.
- Measured outcomes
- Spend, impressions, clicks, CPA, ROAS, conversion, revenue, and lifetime value attach to the objects that produced them.
What is real today
We label each capability rather than implying readiness we cannot prove.
- AvailableEvidence ledger and immutable action history
Built and tested in this product.
- AvailableBidGuard approval queue: reviewing, approving, and dismissing proposed actions
Built and tested. Not enabled against live ad accounts.
- AvailableGoverned Bucket creation
Available in this Space. Rule-based only; no provider writes.
- PreviewRule changes, pause/resume, and archive in the product
Not available yet; Bucket posture stays read-only.
- PreviewWorkspace shell and operator surfaces in active alpha
Alpha; changing, not supported yet.
- DeferredAdditional AdOS lenses beyond the current alpha surface
Described, not built. Do not plan work around it yet.
Learn more
“Available” means the capability is built and tested in this product. It does not mean it is enabled against your live ad accounts. Any write to a provider still runs the discovery, assignment, approval, and audit path before it takes effect.
- Evidence ledger and immutable action history: Evidence writes are server-side commands with an append-only ledger and their own test suite.
- BidGuard approval queue: reviewing, approving, and dismissing proposed actions: ApprovalQueueClient is the one component with BIDGUARD_COMMANDS_AVAILABLE = true; it posts to the Space-scoped action feed.
- Governed Bucket creation: The Guardrails modal uses the Space-scoped v2 Bucket command with operator access and an idempotent request identity.
- Rule changes, pause/resume, and archive in the product: BucketDetailClient keeps pause, resume, and archive unavailable; guardrail creation only proposes approval and provider writes remain approval-gated.
- Workspace shell and operator surfaces in active alpha: The shell is the merged AdOS surface; lens depth is still landing. The surface will change and is not supported.
- Additional AdOS lenses beyond the current alpha surface: No lens beyond the ones this site links exists in the route tree. Do not plan work around it yet.
Start with spend protection.
BidGuard is the first AdOS product. Any change to live spend waits for approval and audit.