Read-Only pg_cron / Extension Evidence Recheck (2026-06-18)
Read-Only pg_cron / Extension Evidence Recheck
Date: 2026-06-18 · Workstream: LEGO-PILOT-SLICE-0-R2-B2-READONLY-EVIDENCE-OWNER-PATH-MACRO-2026-06-18 (Deliverable 13 of 30) · Editorial revision: rev1
Class: read-only channel evidence (pg_cron) · READ-ONLY · NON-ENACTING · NON-AUTHORIZING · NO extension install · NO write performed.
Metadata convention. Editorial revision (rev1) only. AgentData storage revision/
content_lengthauthoritative at read time; not pinned here.
pg_cron lock. Read-only re-confirmation that pg_cron is not installed. It installs no extension, selects no channel. pg_cron remains risky/future-gated.
0. Status and non-authorization
STATUS: PASS — engineering / read-only. Fresh confirmation: pg_extension does not include pg_cron. Engineering PASS ≠ authority PASS. Default disposition: HOLD. No extension install; no channel selection; no DB write/DDL/DML; no TD; no blocker resolved.
Evidence basis — FRESH_READONLY_EVIDENCE (FQ-5). Reading discipline: main process, no reader-agents.
1. Purpose
Re-confirm read-only that pg_cron is absent (so dot_tools.cron_schedule metadata is inert and pg_cron is not a standing scheduler). §4 records the readback.
The one rule: pg_cron is risky/future-gated; installing it is a net-new extension (an infra write), Owner-gated. Reading pg_extension does not install it.
2. Sources / evidence read
Deliverable 1 (FQ-5); R2a §6 (no pg_cron; dot_tools cron is inert metadata); Mega Gate channel-proof-obligations (pg_cron obligation = install + pg_extension shows it). Read directly, main process.
3. Accepted baseline (carried)
R2a (INHERITED): pg_extension = btree_gist, pgcrypto, plpgsql, postgres_fdw — no pg_cron; so no in-DB scheduler runs any dot_tools.cron_schedule.
4. Read-only evidence observed (FRESH, 2026-06-18)
FQ-5 — pg_extension: btree_gist (1.7), pgcrypto (1.3), plpgsql (1.0), postgres_fdw (1.1) — pg_cron NOT present. Unchanged from R2a. The 0 6/0 */6 schedules in dot_tools remain inert metadata (no in-DB scheduler exists to run them).
5. Classification / result
- pg_cron = risky/future-gated (unchanged); read-only obligation confirmed: the extension is absent.
- No extension installed; no channel selected. Almost nothing about pg_cron as a channel is provable until it is installed (a write) — consistent with its risky/future-gated disposition.
6. Owner-gated future work
| Future work | Gate required | Forbidden now? |
|---|---|---|
| Install pg_cron | Điều 32 + infra/extension approval | Yes |
Bind a cron.job to a birth inspector |
Điều 32 (after install) | Yes |
7. What remains unresolved
- pg_cron absent; install is a write, Owner-gated.
- Blockers — all OPEN.
8. Ready for GPT/Codex review
Yes — as a read-only pg_cron recheck.
Core rule: pg_cron is not installed (FRESH); dot_tools cron metadata is inert; risky/future-gated; no install, no channel selected.
Default disposition: HOLD. Engineering PASS ≠ authority PASS. All blockers remain OPEN.