From unknown stack to defensible operating proof.
GuardState lets an operator experience the product before a sales process: inspect, challenge, scan, instrument, govern, prove, share, diligence, and commission—with every authority claim bounded by evidence.
One path. No authority shortcuts.
Every step produces evidence or exposes a gap. None of these product surfaces independently authorizes capital movement.
Inspect
Open the labeled Mission Control demonstration and reconstruct a financial action across identity, data, policy, provider truth, reconciliation, and economics.
Open inspect →Challenge
Inject deterministic failure cases and inspect the evidence, reason code, decision, digest, and resulting state.
Open challenge →Scan
Map agents, AIBOM, authority, capital reach, evidence gaps, and commissioning architecture without uploading source or secrets.
Open scan →Save
Create a workspace boundary for versioned findings, policies, incidents, and evidence. External persistence remains readiness-gated.
Open save →Instrument
Emit signed OBSERVE telemetry through the SDK or Edge; installation and reporting never grant execution authority.
Open instrument →Govern
Bind Passports, Mandates, policy, approvals, circuits, and provider capability into the effective Authority Envelope.
Open govern →Prove
Generate a trace and Evidence Pack that preserve known, inferred, conflicted, stale, and unavailable evidence separately.
Open prove →Share
Use expiring, viewer-scoped, revocable evaluation artifacts. Production sharing requires durable revocation storage.
Open share →Diligence
Review security, deployment, assurance, release provenance, and explicit owner-controlled blockers.
Open diligence →Commission
Select deployment, identity, evidence storage, provider, and support requirements before any boundary is called available.
Open commission →Expand
Promote controls through evaluation, replay, blast-radius delta, independent review, CANARY, and ACTIVE evidence.
Open expand →Intelligence proposes. Mandates constrain. Independent controls authorize.
Providers execute. GuardState correlates and proves the outcome. A model, agent, scanner, trace, evaluation, or dashboard cannot grant execution authority.
CHANGE → EVALUATE → REPLAY → REVIEW → CANARY → ACTIVE
Capability, AIBOM, Mandate impact, historical controls, and blast-radius delta remain digest-bound to the reviewed policy version.