Proof-Carrying Rescue Status
Monogate’s high-dimensional optimizer work is organized around named boundary events and named rescue operators. This is the current status table.
| Boundary event | Rescue operator | Rescue event | Forge evidence | MachLib bridge | Semantic tier |
|---|---|---|---|---|---|
domain_wall | log_domain_lift | log_domain_rescue | packet + tests + registry | restricted semantic rewrite + concrete witness + closed packet bridge | restricted_semantic_rewrite |
overflow_wall | guard_clamp | guard_rescue | packet + tests + registry | concrete witness + closed packet bridge | concrete_sample_invariant |
phantom_attractor | precision_escape | interior_sample | packet + tests + registry | concrete witness + closed packet bridge with explicit event witness | concrete_sample_invariant |
saturation_shelf | saturation_deshelf | corner_concentration | packet + tests + registry | concrete witness + closed packet bridge with explicit event witness | concrete_sample_invariant |
Reading The Table
packet + tests means Forge has a dedicated source fixture, trace tool,
generated report, and regression tests.
restricted semantic rewrite means MachLib has a theorem for a stated,
narrow program class. For log_domain_lift, that class is the witness-shaped
log-domain rescue where a raw domain-wall sample is rewritten into a positive
internal coordinate with a log_domain_rescue event.
concrete witness + closed packet bridge means MachLib has both a theorem
connecting a valid packet transition to its obligation and a sample-level
theorem that discharges the concrete local obligation. The log-domain lane has
a positive-coordinate witness. The guard-clamp lane now has an output-safety
witness. The precision-escape lane has a local precision-sensitivity witness.
The saturation-deshelf lane has a clamp-invariant witness.
closed packet bridge with explicit event witness means the bridge is closed,
but the theorem requires both the event witness and transition witness. That is
the current honest shape for phantom-attractor evidence.
The saturation-deshelf lane also has a concrete clamp-invariant witness now, but it remains more cautious in public copy because deshelf moves a trace off a saturation shelf rather than simply ending in a rescue-normal event.
The precision-escape witness is local: it records that low precision reported a
stalled gradient, while the higher-precision replay exposed a nonzero escape
signal and moved the sample from phantom_attractor to interior_sample. It
does not claim a convergence theorem.
The four-lane suite manifest is published as
Proof-Carrying Rescue Suite v0.
The manifest reading guide is
How to Read the Rescue Suite.
Next Frontier
The next target is no longer another one-off rescue. It is governed unification:
four packets -> one manifest -> obligation registry -> approval gate -> Explorer/dashboard/replay surface
The registry says which obligations are routed, witnessed, concretely proven, semantically tiered, CI guarded, public-copy safe, or blocked. The approval gate decides whether the generated artifacts may be surfaced or deployed while keeping the unrestricted semantic-rewrite claim false.