Current public sanitized packetFour controlled synthetic casesData-driven controlled batchBrowser-side SHA-256 and parity checks
1 · Decision Explorer
Choose the movement the AI attempted to cause.
The Explorer displays the packet’s authoritative Decision API result and the pre-decision intent, legitimacy, authority and evidence conditions that informed it. Semantic Projection remains explanatory and cannot replace the Decision API.
Loading
Loading proof case…
- Workflow
- —
- Attempted movement
- —
- Potential protected effect
- —
LOADING
- Release authorized
- Release status
- —
- Routed to
- —
- Gate result
- —
Delegated Authority—
Evidence sufficiency—
Route—
Buyer-readable reason—
Intent Horizon
Is this proposed action still faithful to the original mission?
- R7 status
- —
- Semantic distance
- —
- Threshold
- —
- Decision effect
- —
- Prohibited boundary crossed
- —
- Horizon / sequence
- —
- Original intent proof
- —
Governing Basis
Are the conditions that make this action legitimate still current?
- Basis status
- —
- Lawful continuation
- —
- Basis changed
- —
- Revalidation
- —
- Rebind
- —
- Fresh decision
- —
- Basis proof
- —
Layered Authority
- Source Authority
- Eligible / quarantined
- Capability Authority
- Operation / target
- —
- Delegation / validity
- —
Evidence Custody
- Evidence sufficiency
- —
- Provenance
- —
- Integrity
- —
- Custody
- —
Upstream Runtime-State Attestation
——
OntoGuard can accept bounded, freshness-aware upstream state without adopting an LLM, agent, planner, multi-agent system, robotic system, world model or future substrate as a second authorization authority.Longitudinal Intelligence
- Semantic Curvature
- —
- Comparable history
- —
- Governance Spectrum
- —
No-bind / proof status—
Protected effect formed—
Downstream commit—
Authorization token—
Human review required—
Consequence Custody—
—
- Movement
- —
- Governing basis
- —
- Frozen input
- —
- Decision
- —
- Boundary event
- —
- Grant / NO-BIND
- —
- Receipt
- —
- Manifest
- —
2 · Governed Event Lifecycle
Eight stages connect proposal to consequence and closure.
Every lifecycle value comes from the current public packet or the selected packaged controlled case.
3 · Controlled Batch Proof
Four proposed movements. One conservative roll-up.
The chart, counts, aggregate result, human-attention total, filters, and table are computed from the same controlled-case data. Each case keeps its own Decision API and R7 horizon; batch membership is not one R7 trajectory or Semantic Curvature history.
0cases
Aggregate decision—Any BLOCK controls; otherwise ESCALATE controls; all ALLOW is required for aggregate ALLOW.
Aggregate release—Authorized only when every case is release-authorized.
Human attention—Cases requiring review or blocked from release.
Proof postureControlled batchNot customer production activity or a real-time activity counter.
Showing all controlled cases.
| Case | Attempted consequence | Decision | R7 posture | Release | Proof |
|---|
4 · Browser-Side Verification
Do not take the packet on faith.
Browser-side integrity and parity verification. Fetch the public manifest first, verify listed SHA-256 hashes, and compare authoritative decision/release/no-bind fields plus available maturity, R7, governing-basis and Consequence Custody bindings. This is not the complete independent OntoGuard DAP verification harness and is not an external digital signature.
No files are uploaded. Verification runs in this browser against same-origin public assets.
Verification resultNot run0 files checked · 0 verified
- Manifest loadWaiting
- Listed SHA-256 hashesWaiting
- Decision parityWaiting
- Release-status parityWaiting
- No-bind parityWaiting
- Current-event maturity parityWaiting
- Controlled-fixture maturity parityWaiting
- R7 status / threshold parityWaiting
- Governing-basis identity parityWaiting
- Consequence-custody status parityWaiting
Public capability boundary
What this Explorer proves—and what it does not claim.
OntoGuard governs the proposed state transition independently of whether it originated from an LLM, agent, planner, multi-agent system, robotic system, world model or future intelligence substrate. The Decision API remains the sole ALLOW / BLOCK / ESCALATE authority.
Shown here
- Authoritative Decision API action
- R7 intent posture and pre-decision role
- Governing-basis continuity
- Source / capability authority posture
- Release state and route
- NO-BIND / Consequence Custody
- Current-event maturity
- Controlled Full-Seam L4 evidence
- Semantic Curvature status
- Controlled batch posture
- Browser-side packet integrity and parity
Requires customer integration
- Production endpoint enforcement
- Actual customer production route inventory
- Production non-bypassability evidence
- Production-endpoint fail-closed evidence
- Customer-connected route replay evidence
- Production bypass-attempt evidence
- Real reviewer and downstream outcome closure
- Protected production endpoint proof
Not claimed
- Universal production L5
- External digital signing
- Customer validation
- Automatic compliance
- Live model-weight mutation
Move from public proof to your workflow
Which AI-proposed movement should OntoGuard govern first?
Start with 10–25 representative prompts, responses, outputs, or logs. No internal document upload is required for the first assessment.