Read-Only Channel Liveness Proof-Gap Matrix

Date: 2026-06-18 · Workstream: LEGO-PILOT-SLICE-0-R2-B2-READONLY-EVIDENCE-OWNER-PATH-MACRO-2026-06-18 (Deliverable 15 of 30) · Editorial revision: rev1 Class: read-only proof-gap matrix (channel obligations) · READ-ONLY · NON-ENACTING · NON-AUTHORIZING · RECOMMENDATION_ONLY — NOT AUTHORITY · NO channel selected · NO write performed.

Metadata convention. Editorial revision (rev1) only. AgentData storage revision/content_length authoritative at read time; not pinned here.

Proof-gap lock. This packet states, per channel, which proof obligation is now read-only-met (FRESH) vs which remains write-gated/OOB. It proves nothing further, installs nothing, selects nothing.

---

0. Status and non-authorization

STATUS: PASS — engineering / read-only. A per-channel matrix mapping the Mega Gate channel proof-obligations to their fresh read-only status. Engineering PASS ≠ authority PASS. Default disposition: HOLD. No channel selected/wired/installed/promoted; no write; no TD; no blocker resolved.

Evidence basis — FRESH_READONLY_EVIDENCE (Deliverables 11–14) + WG/OOB for the rest. Reading discipline: main process, no reader-agents.

---

1. Purpose

Show exactly how much of each channel's proof obligation is now satisfiable read-only (so an Owner channel decision is not blocked on obligations that can only be met after a build). §4 is the matrix.

The one rule: the read-only first obligations of the two candidates are now FRESH-met; the write-gated obligations (the producer firing, the queue draining, the extension installing) are met after selection, behind their own gates. This does not select a channel.

---

2. Sources / evidence read

Deliverables 11–14 (fresh per-channel evidence); Mega Gate channel-proof-obligations (the per-channel obligation list + provability classes R/O / OOB / WG). Read directly, main process.

---

3. Accepted baseline (carried)

Provability classes (Mega Gate): R/O read-only-provable; OOB out-of-band; WG write-gated. Shared evidence floor (every channel, build-time/WG): S7 run-evidence incl. channel id; producer idempotency.

---

4. Channel liveness proof-gap matrix (FRESH read-only status)

Channel	First obligation (read-only-provable)	Fresh status	Remaining obligations	Class
host cron	birth entry present in wf_host_crontab_snapshot	read-only MET — snapshot readable; no birth entry (54/0; D11) → "not wired today" is proven read-only	producer actually runs; idempotency; per-run S7	WG
agent-api executor	dot_agent_api_contract birth row + persisted master-switch readable	read-only MET — 2 contracts readable, 0 birth-bound; switches OFF (D12)	transient switch confirm; dispatch run; no-lane-coupling proof	OOB (transient) + WG
pg_cron	pg_extension shows pg_cron	read-only MET (negative) — pg_cron absent (D13) → cannot be a channel without an install	install; cron.job entry; per-run S7; removal/rollback	DEC + WG
job_queue worker	live heartbeat readable	read-only MET — heartbeat readable; idle since 2026-05-26; outbox undrained (D14)	enable + prove draining; end-to-end consume; undrained-queue guard	WG
manual one-shot	n/a (rejected as standing channel)	n/a	—	rejected

Reading (recommendation-only). The two candidates (host cron, agent-api) have their read-only-provable first obligations FRESH-met: the snapshot and the contract+switches are readable and show the current (unwired, fail-closed) state. This is exactly the evidence an Owner channel selection needs — the rest (the producer actually firing) is met after the build, behind its own gate. pg_cron and job_queue need a write (install / enable) before almost anything further is provable — consistent with their risky/future-gated disposition. No channel is selected.

---

5. Classification / result

• Read-only-met: the first obligation of all four standing channels (positive for candidates' readability; negative for pg_cron absence; idle for queue).
• Write-gated remaining: every "did it actually run / drain / install" obligation + the shared S7-channel-id + idempotency floor.
• OOB remaining: the agent-api transient master-switch value.
• No channel selected; CHANNEL_AUTHORITY_DRIFT guarded.

---

6. Owner-gated future work

Future work	Gate required	Forbidden now?
Meet any write-gated obligation (run/drain/install)	Điều 32 + build	Yes
Confirm agent-api transient switch (OOB)	Owner out-of-band (read-only)	Yes (not done here)
Select a channel	Owner decision (recommendation-only)	Yes

---

7. What remains unresolved

• Every channel's write-gated obligations remain unmet (no producer/build exists).
• agent-api transient switch OOB.
• Blockers — all OPEN.

---

8. Ready for GPT/Codex review

Yes — as a read-only proof-gap matrix.

Core rule: the candidates' read-only first obligations are FRESH-met; the write-gated/OOB obligations remain owed after selection; no channel selected as authority.

Default disposition: HOLD. Engineering PASS ≠ authority PASS. All blockers remain OPEN.