Consequence assurance at the action cut
Turn an uncertain consequence into a result you can challenge.
Open a semantic profile, authority trace, OAuth evidence record, Keycloak commissioning summary, or exported inspection record. The current surface keeps the frozen v0.5.0 semantics intact while making the counterexample, obligation certificate, route, boundary, and before-after transition easier to interrogate.
Reference records
Start with a real boundary contrast.
Each record isolates a different reason that administrative state, operative effect, or source evidence can diverge.
Challenge mode
Attack the assurance claim.
Inspect the materiality witness, switch among exact inclusion-minimal obligation families, replay each removal witness, then change the evidence cut and recompute the result.
Closure route
From semantic obligation to realizable change.
A valid route uses only declared Establishments and closes every reachable leaf. Declared cost ranks routes only after semantic validity has been established.
Assurance boundary
See exactly where the claim stops.
Core exactness, source transfer, P0/P1/P2 preservation, cut adequacy, and commissioning evidence are different layers. The Inspector keeps them separate.
Comparison
Compare the consequence before and after the distinction changes.
Use the baseline and current hypothetical cut, load a second local artifact, or open a recorded commissioning pair. Comparison is descriptive: each side is analyzed independently under its own declared boundary.
Source and provenance
Follow the result back to the bytes and declaration.
Content digests support identity and replay. They do not authenticate external truth. Source derivation and preservation claims remain explicit.