Understand demo mode
What the DEMO badge means, and what demo mode does and doesn't change.
If your tenant is in demo mode, everything you see is honestly labeled — this page explains what that label does and does not mean.
Steps
- Recognize the DEMO badge. If your tenant runs in demo mode, you'll see
a
DEMO DATAorDEMO FEEDbadge on surfaces running on seeded data, and a demo note on the Setup checklist's zone bar. If you don't see any DEMO badges, your tenant isn't in demo mode — every real operator is provisioned with demo mode off and stays off. - Know what it changes. Demo mode changes two things only: which data provider answers (a seeded DEMO provider instead of a live one), and whether a human sign-off step auto-completes. It never changes gate logic and never fakes a verdict.
- Read
PENDING_VERIFICATIONcorrectly. A demo tenant's compliance gates land onPENDING_VERIFICATIONwith a DEMO badge — never a fakeVERIFIEDor "compliant." A gate that would hard-fail (suppressed) still blocks in demo mode exactly as it would for a real tenant. - Read
DEMO-AUTOcorrectly. When a human gate auto-completes in demo mode, it's recorded in the same immutable ledger a real tenant's approval would use, taggedDEMO-AUTO— an honest, auditable stand-in for a human click, not a silent skip. - Know how it's turned on. Demo mode is a per-tenant flag set when a tenant is provisioned — it isn't a toggle in the console. A real operator is never switched into demo mode; if you believe your tenant is incorrectly flagged, raise it with the Obsidian Jet team.
Never describe a demo-mode result as "compliant" or "approved" — the platform doesn't make that claim from seeded or modeled inputs, in demo mode or otherwise.
TODO-SHOT: screenshot of a DEMO badge on a compliance gate and the Setup zone-bar demo note, from the demo tenant.