Macro-5 Staging Object: Error Candidate — R2-B2 (2026-06-19)

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

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

NON_EXECUTABLE_TD_CANDIDATE. Conceptual object only. Do not create a real object.

---

0. Status and non-authorization

STATUS: PASS — engineering / design-only. The error conceptual object: a structured fail-closed record. Engineering PASS ≠ authority PASS. Default: HOLD.

1. Purpose

Describe how a run represents failure: a no-op + a structured reason.

2. Sources / evidence read

Macro-4 B2 error contract (D31); error model (19); bad-input no-digest-pass rule (Macro-4 D53). Main process, no reader-agents.

3. Accepted baseline (carried)

Failure = no stamp for that row/stage + a failure record; never a fabricated pass.

4. Evidence / analysis — error candidate

Aspect	Description (no schema)
role	the fail-closed outcome of a stage that cannot pass
field family	candidate-error-code, candidate-reject-reason, stage, entity-ref
behavior	no candidate stamp; append failure to staging evidence
disqualifier	a stamp/certify on bad input = fail-open (F-OPEN-1…4)

5. Candidate / requirement / gate / result

The error object guarantees every failure is observable and reversible (it is part of the run's delete unit). It is a role, not a table; no error is produced here.

6. Owner-gated future work

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

7. What remains unresolved

Concrete error codes and the ambiguous-partial case (BI-4) are future TD.

8. Ready for GPT/Codex review

Yes — Codex should confirm the error object is fail-closed and never a silent pass.