Block new authority
Retirement begins after the root can no longer initiate new business. That is a starting premise, not the closure verdict.
BOUNDED AGENT CLOSURE · FROZEN ENGINE · 8 BOUNDARY CASES
Agent Closure Inspector
Stopping an autonomous agent from creating new work does not tell you whether the consequences it already created are finished.
This instrument follows the consequences still attributable to a retiring agent, applies the terminal condition each consequence actually requires, and shows whether the available evidence supports bounded closure, exposes a known blocker, or leaves the answer unresolved.
Follow consequences
Traverse evidence-backed DERIVED_FROM lineage so a descendant job or commitment does not disappear behind an already-quiet parent.
Apply the right ending
Extinguish, settle, transfer, and retain are different terminal dispositions. Closure does not mean deleting everything.
Confirm stability
Coverage, attribution, fresh observation, source stability, and final-pair semantic convergence are required before CLOSED.
Four useful contrasts
The cases are designed to break simple closure rules.
The corpus is most useful when read as a set of opposing examples. A success response can still fail. A surviving object can still be terminal. A clean graph can still be unknown. One clean scan can still be too early.
Success is not the postcondition.
A cancel operation reports success while the schedule remains present, active, and linked to the retiring root.
INCOMPLETESurvival is not necessarily failure.
An active object can be closed relative to the old root when responsibility has moved to an accepted successor.
CLOSEDSilence is not evidence of closure.
No known blocker appears, but a required source cannot establish complete coverage.
UNKNOWNClean once is not stable.
A later retry enters the consequence cone, so closure waits until the terminal semantic state is confirmed again.
CLOSED AFTER CONFIRMATIONPrivate evidence
Public cases are hosted. Your evidence stays local.
Choose a conforming JSON evidence bundle. A browser-targeted build from the frozen v0.3 verifier evaluates it in memory on this device. The file is not uploaded to RISU or persisted by the Inspector. For archival reproduction, the canonical Node verifier remains available through the local Inspector.
Preparing browser-local evaluator.
Frozen corpus · phase1-freeze-v0.3
Eight boundary cases
Each card is a generated evaluation from the frozen verifier. Open a case to inspect its decisive reasons, attributable lineage, source coverage, scan history, and certificate when one exists.