Macro-5 B2 Candidate Error Contract Refinement — R2-B2 (2026-06-19)

Date: 2026-06-19 · Workstream: R2-B2-MACRO-5-STAGING-BUILD-AUTHORIZATION-PACKAGE-2026-06-19 (Deliverable 35 of 110) · Editorial revision: rev1 Class: B2 error contract refinement · READ-ONLY · NON-ENACTING · NON-AUTHORIZING · B2-ONLY · NO write performed.

Metadata convention. Editorial revision (rev1) only. AgentData storage revision/content_length authoritative at read time.

---

0. Status and non-authorization

STATUS: PASS — engineering / design-only. Refines the Macro-4 B2 error contract; fail-closed preserved. Engineering PASS ≠ authority PASS. Default: HOLD.

1. Purpose

Carry the fail-closed error contract forward for the workbench context.

2. Sources / evidence read

Macro-4 B2 error contract (D31, BI-1…12); error candidate (26); bad-input no-digest-pass rule (Macro-4 D53). Main process, no reader-agents.

3. Accepted baseline (carried)

On failure: no stamp + a structured failure record; never a fabricated pass; fail-open is disqualifying.

4. Evidence / analysis — refinement (build-context only)

Clarification	For the workbench build
every BI-n	resolves to no candidate stamp + a candidate_error_code + an evidence append
ambiguous (BI-4)	mark ambiguous; Owner-gated review; never certify
Điều 0-G unresolved (BI-5)	SOURCE_RECOVERY_REQUIRED; no stamp
disqualifier	a stamp/certify on bad input = fail-open (F-OPEN-1…4) → reject the design

5. Candidate / requirement / gate / result

The refinement preserves the fail-closed mapping with no new behavior. No error path is executed here.

6. Owner-gated future work

Wiring the error path to a built audit sink is Owner-gated; forbidden now.

7. What remains unresolved

BI-4 / BI-12 remain BAD_INPUT_BEHAVIOR_UNCLEAR.

8. Ready for GPT/Codex review

Yes — Codex should confirm every BI-n stays a fail-closed no-op.