The Name Outside the Contract

Description and use

Contract validation omitted file names, allowing receipts without timestamps to slip through. Adding a filename pattern to the contract and a legacy exception list fixed the issue, ensuring proper validation while preserving evidence.

Problem

Contract validation missed file names, allowing receipts without timestamps to bypass atomic‑receipt rules.

Outcome

All live receipts now pass name checks; legacy receipts are forgiven once; new violations trigger fail‑closed exits, ensuring audit integrity.

Workflow

• 1. Extend each contract class to include a filename pattern. 2. Update registry to store pattern and legacy exception list. 3. Run acceptance, regression, and assertion tools to validate names. 4. If a legacy file fails, add it to the pardon list with a reason. 5. Re‑run to confirm legacy passes under pardon and new violations exit with code 2.
• 6. Monitor for two consecutive windows with out‑of‑contract receipts to retire the experiment.

Evidence

The audit that found it had to flag the debt by hand.

Source

The fix extends the contract to the name.

Source

The registry carries a named exception list — each legacy file forgivable exactly once.

Source

Proof — the green run (radares\e143-regressao-catalogo-20260905-195521-909966.txt, closing with "CATALOGO VERDE").

Source