Macro-3 Channel Host-Cron Proof Plan — R2-B2 (2026-06-19)

Date: 2026-06-19 · Workstream: R2-B2-MACRO-3-OPTION-D-OWNER-DELEGATE-DECISION-PACKAGE-2026-06-19 (Deliverable 11 of 60) · Editorial revision: rev1 Class: channel proof plan (host cron) · READ-ONLY · NON-ENACTING · NON-AUTHORIZING · proof obligations only — NOT run · NO write performed.

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

Proof-not-run lock. These are obligations to be satisfied in a future Owner-gated TD, not tests run here. Running any of them now would be ACTUAL_TD_DRIFT / forbidden mutation → HOLD.

---

0. Status and non-authorization

STATUS: PASS — engineering / decision-prep. Lists what host cron must prove before it could carry a B2 birth job. Engineering PASS ≠ authority PASS. Default: HOLD.

1. Purpose

Define the obligations that close host-cron's risks (D9) — so "candidate" can one day become "proven", under Owner gate.

2. Sources / evidence read

Macro-2 channel proof-gap closure, host-cron memo; inspect-producer TD-prep proof obligations. Main process, no reader-agents.

3. Accepted baseline (carried)

A channel is proven only against the B2 producer's contract: staging-first, fail-closed, idempotent, one-column-per-inspector, no certify/canonical.

4. Evidence / analysis

Today host cron has 0 birth jobs (FRESH); none of the below is satisfied.

5. Recommendation / matrix / result — proof obligations (HC-PO)

#	Obligation	Closes
HC-PO-1	Runs staging-first, never against prod birth_registry	NT (no-prod-touch)
HC-PO-2	Producer fail-closed on any unresolved rule (no stamp on failure)	HC-R4
HC-PO-3	Idempotent re-runs; no double-stamp	HC-R3
HC-PO-4	Writes only inspect_pen/stamp/gate, one column per inspector, strict PEN→STAMP→GATE order	B2 lock
HC-PO-5	Emits an external audit log per run (compensating for HC-R1)	HC-R1/R2
HC-PO-6	Rollback = remove crontab line + documented; no residue	delete-fast

6. Owner-gated future work

Satisfying HC-PO-1…6 happens in the actual B2 TD + staging build (Owner-gated), not here.

7. What remains unresolved

None satisfied; host cron remains an unproven candidate.

8. Ready for GPT/Codex review

Yes — Codex should add any missing obligation, especially around observability parity with agent-api.