Loop Hardening Contract

Use this contract after loop-readiness-review when repeated delivery needs tighter execution evidence. It is a review and packet format, not a runner or scheduler.

1. Harness Stripping

Remove harness complexity only through an isolated, one-component experiment:

1. Record the component, its intended failure mode, and its operating cost.
2. Capture a representative baseline for completion, verification, cost, and failures.
3. Disable exactly one non-safety component between runs, never during a live run.
4. Repeat the same bounded case and classify REMOVE, RESTORE, HARMFUL, or INCONCLUSIVE.
5. Retain the evidence and human settlement decision.

Never strip sandboxing, budgets, stop conditions, human gates, root verification, or protected-data boundaries.

2. Runtime-Path Sprint Packet

Freeze this packet before execution: