Consequence Closure v1.0.0
This release establishes the first frozen public research baseline for Consequence Closure, a carrier neutral assurance framework for determining whether the consequence of a concrete machine action is fixed by the evidence available at a declared action cut.
The release includes RISU Technical Note 2026-03, Consequence Closure: Semantic Assurance at the Machine Action Boundary, together with Consequence Closure Inspector v0.5.0 and the frozen source, validation records, evidence summaries, replay materials, manifests, and verification tooling that support the accompanying research artifact.
Technical Note
DOI: 10.5281/zenodo.22095709
Consequence Closure Inspector v0.5.0
DOI: 10.5281/zenodo.22095595
The technical note develops consequence closure at a declared action cut, replayable materiality witnesses, inclusion minimal semantic obligations, realizable Establishments, closure Routes, and a P0/P1/P2 hierarchy for preserving closure, obligation, and Route claims across source to Core compilation.
A frozen differential against the official Cedar 4.12.0 runtime confirmed exact P1 over the declared bounded surface with zero post outcome semantic repair. Separate Linux, SQLite, filesystem, OAuthLib, and Keycloak commissioning exercises test operative effect semantics, prospective route selection, and frozen checker transfer at real action cuts.
The reported results remain qualified to their declared boundaries. The Cedar result does not establish general equivalence for Cedar or P2. The commissioning results do not establish general carrier neutrality. The Inspector preserves results, witnesses, replay identity, and assurance qualifications without strengthening the claims it displays.
To verify the frozen Inspector release, run:
cd inspector
node verify-release.mjs
This release is frozen. Any later correction or extension will be published as a separately versioned release so that this public baseline remains reproducible and independently inspectable.