What is fixed?
Separate IMPOSSIBLE, OPEN, and CLOSED(c), without turning determinacy into permission or desirability.
Research instrument · browser local · frozen semantics, evolving interface
Consequence Closure Inspector
See whether a machine action's specified consequence is already determined, preserve the exact counterexample when it is not, and challenge the semantic obligations, Route, and assurance boundary behind the result.
Open the current InspectorChallenge exact results, recompute evidence cuts, compare boundary transitions, and export a deterministic assurance record.
Frozen v0.5.0Open the exact archival browser release tied to the software record.
Semantic engineInspector v0.5.0 · Core v0.1.0
Current executionEphemeral Web Worker
Evidence transportBrowser memory only
Runtime networkNone
One assurance object
Do not just read the verdict. Try to break it.
Why is it open?
Inspect a concrete materiality witness, switch among exact inclusion-minimal obligation families, and replay removal witnesses.
What closes the gap?
Change the current evidence cut, recompute exact compatible realizations, and inspect a declared model-relative Establishment Route.
Where does the claim stop?
Keep Core exactness, source preservation, P0/P1/P2, cut adequacy, commissioning, and source truth visibly separate.
Recorded contrasts
Start where the distinction matters.
MaterialityAuthority revocation remains OPENA revoked grant and observed revocation still leave one earlier capability path unresolved. Inspect the witness, exact obligation, and probe Route.
OperativityAdministrative state is not the effectOpen the Linux administrative case, then compare it with the operative seal that blocks the same pre-existing write path.
Paired controlAuthority and resource can splitInspect a controlled OAuth state where authority reports inactivity while the protected action path still accepts the same token.
Current surface and frozen record
Let the interface evolve without rewriting the published result.
The current hosted surface delegates semantic analysis to the exact frozen v0.5.0 engine and Core v0.1.0, but moves that computation into a Web Worker and adds a stronger interaction layer for challenge, comparison, progressive rendering, and inspection-record integrity checks. The frozen five-file v0.5.0 browser release remains separately available and byte-pinned.
This split is deliberate. The DOI-backed release remains a stable, reproducible research artifact while the current interface can improve without pretending that a later presentation layer was part of the archived release.
- Inspector
- v0.5.0 frozen semantics
- Core
- v0.1.0
- Technical Note DOI
- 10.5281/zenodo.22095709
- Software DOI
- 10.5281/zenodo.22095595
- Public inputs
- Closure profile · authority trace · OAuth evidence · Keycloak commissioning summary
- Export
- risu-consequence-closure-inspection/v2
Claim boundary
The interface can make a formal result easier to interrogate. It cannot manufacture source conformance, infer P2 from a model Route, authenticate external truth from a digest, or enlarge a bounded commissioning claim.