ContractSpec Sandbox
Unlogged local preview (no auth, no analytics, no external providers)
A deterministic sandbox for knowledge brain, operating graph, identity, permissions, realtime replay, runbook, and receipt evidence loops.
Sandbox
Support → Product
Deterministic sandbox
No provider calls
No production writes
Replayable
Evidence included
AI-native company work with permissions, redaction, replay, and evidence.
CompanyOS turns messy workflows into explicit operating graphs, lets agents act only within scoped permissions, blocks unsafe actions, replays every step, and exports evidence receipts.
Start with Support → Product: a customer support signal becomes a product gap while sensitive data is redacted, unsafe actions are blocked, PM approval is required, and the run exports a receipt.
4
Scenarios
13
Graph nodes
13
Replay events
0
Production writes
Move from story to receipt, governance, replay, architecture, and links without changing systems.
What changes when CompanyOS becomes the operating layer.
Before CompanyOS
• Work hidden in tools
• Agents act against vague context
• Permissions unclear
• Data exposure risk
• No replay
• No proof
After CompanyOS
• Explicit operating graph
• Scoped agent capabilities
• Redaction and approval gates
• Replayable execution
• Exportable evidence receipt
The demo follows one inspectable path from graph to replay to receipt.
Graph defines constraints
Signals, actors, policies, approvals, and evidence are explicit before action.
Replay executes against constraints
Allowed, redacted, blocked, and approval-required decisions are inspectable.
Receipt proves execution
The final JSON receipt links actions, policies, redactions, approvals, and run ID.
Default scenario: support-to-product
A customer support signal becomes a product gap. The agent proposes work, CompanyOS redacts sensitive data, blocks unsafe actions, requires PM approval, replays the run, and exports a receipt.
Every journey maps to the same reusable CompanyOS graph model.
Source records
Graph nodes
Graph edges
Permission policy
Identity review
Replay events
Evidence receipt
This is
• Deterministic sandbox proof for CompanyOS-owned AI OS flows.
• Replayable evidence that graph, permissions, approvals, and actions align.
• A production-shaped architecture with providers intentionally disabled.
This is not
• Not a provider integration demo.
• Not a credentialed workflow.
• Not allowed to write to production systems.
Production path: replace sandbox fixtures with certified provider adapters after the same policy gates pass.
Sandbox fixtures
→
Shared graph primitives
→
Permission + identity gates
→
Replay timeline
→
Evidence receipt JSON
→
Production adapter seam
Fixture data is labeled as deterministic sandbox data; all journeys use the same shared core.