Proof-Carrying Rescue Suite v0

The v0 rescue suite is complete.

Forge now emits one manifest for all four proof-carrying rescue lanes:

forge rescue --suite --strict

That command writes the manifest, replay result, markdown summary, and dev-facing Explorer fixture:

reports/proof_carrying_rescue_suite_v0_2026_05_26.json
reports/proof_carrying_rescue_replay_v0_2026_05_26.json
reports/proof_carrying_rescue_suite_v0_2026_05_26.md
reports/proof_carrying_rescue_explorer_fixture_v0_2026_05_26.json

The interactive software inspection surface lives at:

https://monogate.dev/explorer/rescue-suite

The Four Lanes

Boundary event	Rescue operator	Rescue event	Obligation
`domain_wall`	`log_domain_lift`	`log_domain_rescue`	`PositiveCoordinateObligation`
`overflow_wall`	`guard_clamp`	`guard_rescue`	`OutputSafetyObligation`
`phantom_attractor`	`precision_escape`	`interior_sample`	`PrecisionSensitivityObligation`
`saturation_shelf`	`saturation_deshelf`	`corner_concentration`	`ClampInvariantObligation`

Each lane has:

a Forge EML source fixture
a trace-emitting tool
a generated JSON/Markdown report
tests
a MachLib packet bridge
a public research note

What v0 Means

v0 does not mean the optimizer is production-rewriting programs through these rescues. It means Monogate now has a complete evidence vocabulary for the first four boundary events:

raw boundary event
  -> named rescue operator
  -> packet witness
  -> MachLib obligation bridge

The next phase is unification: use the manifest as the stable artifact for Explorer, dashboards, future electronics courseware, and deeper MachLib proofs.

For the practical contract, see How to Read the Rescue Suite.

React