Macro-3 Channel Host-Cron Final Case — R2-B2 (2026-06-19)

Date: 2026-06-19 · Workstream: R2-B2-MACRO-3-OPTION-D-OWNER-DELEGATE-DECISION-PACKAGE-2026-06-19 (Deliverable 7 of 60) · Editorial revision: rev1 Class: channel case (host cron) · READ-ONLY · NON-ENACTING · NON-AUTHORIZING · CHANNEL_AUTHORITY_DRIFT guard · NO channel selected · 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 / decision-prep. The strongest honest case for host cron, without selecting it. Engineering PASS ≠ authority PASS. Default: HOLD.

1. Purpose

Give the Owner the best argument for host cron so the channel decision is informed, not defaulted.

2. Sources / evidence read

Macro-2 host-cron decision memo, weighted comparison; FRESH wf_host_crontab_snapshot=54/0-birth. Main process, no reader-agents.

3. Accepted baseline (carried)

host cron = candidate, NOT selected; lowest-blast-radius option; channel is internal to B2 and replaceable.

4. Evidence / analysis

For host cron: (a) lowest blast radius — a single crontab line, isolated from the app runtime; (b) proven — already the sibling-scanner channel, so the operational pattern is precedented; (c) trivial rollback — delete the line; (d) no new service surface — nothing to promote, no contract to bind; (e) fastest path to a staging pilot. Best when the Owner values simplicity and replaceability over observability.

5. Recommendation / matrix / result

Recommend host cron only if the Owner prioritizes simplicity / replaceability / faster pilot / lowest blast radius. Not selected here. Pair with the host-cron risk map (D9) and proof plan (D11) before any use.

6. Owner-gated future work

Wiring a birth job into host cron is Owner-gated and would be staging-first, fail-closed, idempotent, one-column-per-inspector; forbidden now.

7. What remains unresolved

Observability/auditability gap vs agent-api is real and unmitigated (see D9).

8. Ready for GPT/Codex review

Yes — Codex should test whether "proven sibling-scanner channel" over-claims readiness for a birth producer.