Macro-2 Host-Cron Decision Memo — R2-B2 (2026-06-19)
Macro-2 Host-Cron Decision Memo — R2-B2
Date: 2026-06-19 · Workstream: R2-B2-MACRO-2-OWNER-DECISION-PREREQ-CLOSURE-READINESS-2026-06-19 (Deliverable 7 of 45) · Editorial revision: rev1
Class: host-cron decision-readiness memo · READ-ONLY · NON-ENACTING · NON-AUTHORIZING · RECOMMENDATION_ONLY — NOT AUTHORITY · NO cron created · NO channel selected · NO write performed.
Metadata convention. Editorial revision (rev1) only. AgentData storage revision/
content_lengthauthoritative at read time; not pinned here.
Host-cron lock. Decision-readiness for host cron as a candidate channel. Creates no cron entry, selects no channel.
RECOMMENDATION_ONLY — NOT AUTHORITY — OWNER_GATE_REQUIRED — FUTURE_TECHNICAL_DESIGN_REQUIRED.
0. Status and non-authorization
STATUS: PASS — engineering / decision-prep. A decision-readiness memo for host cron: fresh state, strengths, risks, proof obligations. It creates no cron and selects nothing.
Engineering PASS ≠ authority PASS. Default disposition: HOLD. No cron create/edit; no channel selection; no DB write/DDL/DML; no TD; no blocker resolved; v0.1 not overwritten; v0.2 not authority.
Evidence basis — FRESH_READONLY_EVIDENCE (2026-06-19 RQ-14) + INHERITED_KB_EVIDENCE (CAV-3/CAV-4 snapshot-only). Reading discipline: main process, no reader-agents.
1. Purpose
Answer macro question 3 (host cron half) — can host cron be recommended more strongly without becoming authority? — as a decision-readiness memo.
2. Sources / evidence read
The 30-file host-cron recheck; the Mega-Gate host-cron-vs-agent-api brief + channel proof obligations; R2a §6 (host cron wiring); the fresh RQ-ledger. Read directly, main process.
3. Accepted baseline (carried)
Host cron = candidate; the proven sibling-scanner channel (dot-orphan-scanner, dot-nrm-*, dot-hc-executor); carries no birth entry; the 0 6 slot is dot-nrm-lifecycle.
4. Evidence / analysis (FRESH 2026-06-19)
wf_host_crontab_snapshot= 54 entries; 0 birth/inspect/certify; 1 nrm-lifecycle (RQ-14) — unchanged; readable & unwired.- Tool boundary (CAV-3/CAV-4): no live
crontab -l/systemctltool; the DB-captured snapshot is the authoritative read-only window; no overclaim beyond it.
Strengths (for the Owner to weigh, not a selection): lowest blast radius (one net-new entry, removable); the proven channel for the sibling scanner DOTs; matches the inspector's periodic-scan nature; a birth entry would be a single cron line invoking a governed producer.
Risks/cons: opaque to in-DB observability (visible only via the snapshot); not transactional with PG writes; depends on a governed S2 owner (the cron must invoke a governed producer, not a manual script — else it degrades to the rejected manual one-shot).
5. Decision-readiness result (recommendation-only)
Host cron is a strong candidate on blast-radius and precedent, weaker on observability/transactionality. Stronger framing ≠ selection. Read-only first obligation met (snapshot readable, birth-free); remaining obligations (producer actually runs, idempotency, per-run S7) are write-gated after selection. No cron created; no channel selected. OWNER_DECISION_REQUIRED.
Proof obligations before host cron could be wired (Owner-gated): (HC-1) S2 owner assigned; (HC-2) a governed producer exists for the cron to invoke; (HC-3) idempotency proven; (HC-4) per-run S7 evidence incl. channel id; (HC-5) Điều 32 authorization.
6. Owner-gated future work
| Future work | Gate | Forbidden now? |
|---|---|---|
| Add a birth-inspector host-cron entry | Điều 32 + S2 owner | Yes |
| Select host cron as the channel | Owner decision (recommendation-only) | Yes |
7. What remains unresolved
- Host cron carries no birth entry; wiring is write-gated.
- Live host state beyond the snapshot not readable (CAV-3/CAV-4).
- Blockers — all OPEN.
8. Ready for GPT/Codex review
Yes — as a host-cron decision memo.
Core rule: host cron = candidate, lowest blast radius, proven sibling channel (54/0-birth FRESH); recommended-more-strongly as a comparison, not a selection; no cron created, no channel selected.
Default disposition: HOLD. Engineering PASS ≠ authority PASS. All blockers remain OPEN.