Macro-5 Staging TD Candidate Contract Map — R2-B2 (2026-06-19)

Date: 2026-06-19 · Workstream: R2-B2-MACRO-5-STAGING-BUILD-AUTHORIZATION-PACKAGE-2026-06-19 (Deliverable 15 of 110) · Editorial revision: rev1 Class: non-executable staging TD candidate (contract map) · 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. No SQL/DDL/migration/rollback script/command/schema file/table. Mapping only.

---

0. Status and non-authorization

STATUS: PASS — engineering / design-only. Maps each candidate object to the standard IO envelope + B2 contracts. Engineering PASS ≠ authority PASS. Default: HOLD.

1. Purpose

Show the candidate objects compose only through the explicit IO contracts (no hidden coupling).

2. Sources / evidence read

Macro-4 standard IO envelope (D19) + minimal template (D28); B2 contracts (D29–35); object model (14). Main process, no reader-agents.

3. Accepted baseline (carried)

Blocks connect only through explicit, versioned contracts; the envelope standardizes shape, not content.

4. Evidence / analysis — object → envelope mapping

Candidate object	Envelope surface	B2 contract
input candidate	input_surface	D29
output candidate	output_surface (candidate-only)	D30
error candidate	error_surface	D31
evidence candidate	evidence_surface	D32
delete candidate	rollback_surface / delete_fast_unit	D33
owner candidate	owner_surface / authority_gate	D34
promotion blocker	promotion_surface (forbidden now)	D27/D35
production firewall	forbidden_surfaces	D35

5. Candidate / requirement / gate / result

Every candidate object lands on exactly one envelope surface; there is no shared mutable surface and no cross-object implicit mutation. Composition is by reference (output_surface→input_surface), never a central store. Any centralization = IO_CONTRACT_OVERREACH → HOLD.

6. Owner-gated future work

Binding any surface to runtime is Owner-gated; forbidden now.

7. What remains unresolved

The contract is shape-complete; runtime binding is future TD.

8. Ready for GPT/Codex review

Yes — Codex should confirm the mapping keeps each object per-surface and non-centralizing.