KB-716C

Read-Only Channel Substrate Evidence Summary (2026-06-18)

6 min read Revision 1
laws-newR2-B2R2-D2channel-substrateread-only-evidencefresh-readonlyrecommendation-onlynon-authorizing2026-06-18

Read-Only Channel Substrate Evidence Summary

Date: 2026-06-18 · Workstream: LEGO-PILOT-SLICE-0-R2-B2-READONLY-EVIDENCE-OWNER-PATH-MACRO-2026-06-18 (Deliverable 10 of 30) · Editorial revision: rev1 Class: read-only channel-substrate roll-up · 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.

Channel-authority lock. This packet summarizes the fresh read-only substrate state for the candidate/risky channels. It selects, wires, installs, promotes nothing. RECOMMENDATION_ONLY — NOT AUTHORITY — OWNER_GATE_REQUIRED — FUTURE_TECHNICAL_DESIGN_REQUIRED. Any wording that reads as a selection is CHANNEL_AUTHORITY_DRIFT → HOLD.


0. Status and non-authorization

STATUS: PASS — engineering / read-only. A roll-up of the fresh channel-substrate evidence (Deliverables 11–14) and what it means for an eventual Owner channel decision. Engineering PASS ≠ authority PASS. Default disposition: HOLD. No channel selected/wired; no pg_cron install; no contract promotion; no worker enable; no DB write/DDL/DML; no TD; no blocker resolved.

Evidence basis — FRESH_READONLY_EVIDENCE (FQ-5/10/15/16/17/18/19). Reading discipline: main process, no reader-agents.


1. Purpose

Answer macro question 5 (has the channel substrate evidence changed or remained as inherited?) at the summary layer. §4 rolls up the four channel-substrate rechecks; §5 states what it means for the (Owner-only) channel decision — recommendation-only.

The one rule: the channel is a replaceable internal of B2 (B2-AC-7); reading its substrate does not select it. The substrate is fail-closed for any standing birth channel today.


2. Sources / evidence read

Deliverable 1 (FQ ledger); Deliverables 11–14 (host cron, agent-api, pg_cron, queue); Mega Gate channel files (R2-D2 recommendation, host-cron-vs-agent-api brief, channel-proof-obligations). Read directly, main process.


3. Accepted baseline (carried)

5-channel classification (Mega Gate, recommendation-only): host cron = candidate; agent-api executor = candidate; pg_cron = risky/future-gated; job_queue worker = risky/future-gated; manual one-shot = rejected as standing channel. Substrate fail-closed (INHERITED).


4. Read-only evidence observed (FRESH, 2026-06-18)

Channel Fresh substrate state Prior (INHERITED) Change Deliverable
host cron wf_host_crontab_snapshot = 54 entries; 0 birth/inspect/certify; 1 nrm-lifecycle (the 0 6 slot) 54 entries, no birth entry none D11
agent-api executor container Up 2 weeks (healthy), :8090; 2 contracts (DOT_KG_EXPLAIN DRY_RUN + VERIFY), 0 birth-bound; switches OFF Up 13 days; 2 KG contracts; 0 birth none (still healthy, still 0 birth) D12
pg_cron not in pg_extension (btree_gist/pgcrypto/plpgsql/postgres_fdw) not installed none D13
job_queue worker queue.worker.enabled=false, queue.job_substrate.enabled=false; queue idle since 2026-05-26; event_outbox=215,597 undrained disabled/idle; outbox ~215,588 none (outbox +9) D14
manual one-shot n/a — rejected as standing channel rejected none (D11–14)

Summary: the channel substrate is unchanged from the inherited baseline and remains fail-closed for any standing birth channel — but the candidates' read-only-provable first obligations are now FRESH-confirmed (host-cron snapshot readable & birth-free; agent-api contract readable & birth-free; pg_cron absent; queue idle). This is exactly the evidence an Owner channel decision needs, validated read-only.


5. Classification / result (recommendation-only)

  • Both candidates remain candidates; neither selected. Their read-only first obligations (Deliverable 15) are met; their write-gated obligations (the producer actually firing) are met only after a build, behind their own gate.
  • pg_cron / job_queue stay risky/future-gated (a write — install/enable — is needed before almost anything is provable).
  • manual one-shot stays rejected as a standing channel (the only legitimate residual one-shot is B5, separate).
  • No channel is selected, wired, installed, promoted, or built. The host-cron-vs-agent-api value judgment remains the Owner's (Deliverable 26 carries the recommendation-only framing).

6. Owner-gated future work

Future work Gate required Forbidden now?
Select a channel Owner decision (recommendation-only inputs in D12/D15/D26) Yes
Wire host cron / bind+promote agent-api / install pg_cron / enable worker Điều 32 (+ master-switch / contract / extension per channel) Yes

7. What remains unresolved

  • Channel not selected (CHANNEL_AUTHORITY_DRIFT guarded); substrate fail-closed.
  • Liveness for a birth channel is unprovable until one is wired (write-gated).
  • Transient master-switch/GUC layer OOB (Deliverable 9/12).
  • Blockers — all OPEN.

8. Ready for GPT/Codex review

Yes — as a read-only channel-substrate summary.

Core rule: the channel substrate is unchanged and fail-closed; the candidates' read-only first obligations are FRESH-confirmed; no channel selected as authority; the decision stays the Owner's.

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

Back to Knowledge Hub knowledge/dev/laws-new/newlaws/consolidation/readonly-channel-substrate-evidence-summary-2026-06-18.md