Intended
READ + WRITE
Proposed
Platform / AI state
Approval is the reference. Production keeps moving.
The existing product foundation preserves approved baselines and candidate changes. The longer-term five-state architecture is designed to compare intended, declared, deployed, observed and approved state without inventing missing telemetry.
Pilot scope requires verification
Interactive architecture preview
Explore the five statements of AI state.
Choose a configuration change, inspect all five states and expand provenance for any value. This is a sample interface, not a live system or a currently qualified five-state connector.
STEERLANE / FIVE-STATE RECONCILIATION / SAMPLE DATA
Conceptual state compiler
One agent. Five different statements of truth.
Compare an approved reference with a proposed and declared change. A missing observation remains unknown; it never becomes a silent pass.
Selected Tool authority: The declared permission widens beyond the approved read-only scope.. Verify deployed authority, run least-privilege checks and route the change for human review.
credit_data_permission
Unapproved changeDeclared
READ + WRITE
Differs from approval
Deployed
UNKNOWN
Not established
Observed
UNKNOWN
Not established
Approved
READ ONLY
Approved reference
Provenance · Declared
READ + WRITE
Example source manifest
A configuration declaration is not proof of deployment.
Semantic discrepancy
The declared permission widens beyond the approved read-only scope.
Declared authority differs from the approved baseline. Deployment and observation have not been established.
Governed next action
Verify deployed authority, run least-privilege checks and route the change for human review.
This example does not generate evidence or execute an approval.
All values are authored examples of five-state reconciliation, not live system observations. Current product functionality centers on baseline, candidate changes and assurance reasoning; cross-vendor state ingestion requires separate connector qualification.
The boundaries matter.
Steerlane should tell a reviewer which state is authoritative for a specific question, where that state came from and what is still unproven.
An accepted baseline retains its reviewed configuration, evidence references and approval history.
A version in a source manifest does not alone prove what is running in production.
Missing deployment or runtime evidence must remain explicit; absence is not conformance.
Start with a real approval problem.
We scope pilots to capabilities verified in the product at the time of evaluation, not the entire future roadmap.