Macro-4 Draft Object Check Contract — R2-B2 (2026-06-19)

Date: 2026-06-19 · Workstream: R2-B2-MACRO-4-STAGING-WORKBENCH-IO-CONTRACT-TD-ENTRY-GATE-2026-06-19 (Deliverable 15 of 90) · Editorial revision: rev1 Class: draft object check contract · READ-ONLY · NON-ENACTING · NON-AUTHORIZING · CONCEPT-ONLY · NO test run · NO write performed.

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

---

0. Status and non-authorization

STATUS: PASS — engineering / design-only. How a draft object is checked in isolation, fail-closed. Engineering PASS ≠ authority PASS. Default: HOLD.

1. Purpose

Define the "checked separately" property: a draft is verified against a controlled fixture before it is trusted, and a check failure never leaks or fabricates.

2. Sources / evidence read

Inspect-producer PO-9 (tested-in-isolation); bad-input/delete-fast plan §3 (adversarial method)/§11 (AC-1…10); operating-rules ("PASS/FAIL không có số liệu" anti-pattern). Main process, no reader-agents.

3. Accepted baseline (carried)

A draft check is an engineering result on a disposable surface; even a passing check is never an Owner authorization to promote.

4. Evidence / analysis — check contract

Property	Requirement
Isolation	checked alone on a controlled fixture (feed sample rows, read candidate inspect_*)
Fail-closed	invalid input never stamps/certifies/canonicalizes/produces a PASS
Evidence	a check reports PASS only with counts/ids/paths (no silent PASS; AP-CLOSE)
No-decide	check evidence records; it never approves or gates
No-test-here	this macro defines the check contract; it runs no check (producer MISSING)

5. Contract / requirement / matrix / result

A draft passes only if it meets the bad-input oracle (Deliverables 49–53) on the disposable surface and emits evidence; a PASS-without-evidence is itself a fail-open. No check is evaluated in this macro.

6. Owner-gated future work

Running a draft check requires a built producer + staging — Owner-gated; forbidden now.

7. What remains unresolved

All check behavior is conceptual (BAD_INPUT_BEHAVIOR_UNCLEAR until built).

8. Ready for GPT/Codex review

Yes — Codex should confirm the check is fail-closed and that no check is claimed as run.