Doctrine TTL watchdog: warn/halt on expired session-tagged rules

filter rejected GATE reversible: simple 3h proposed 9 Jun 2026

What is the proposed change?

Add a parse step at scheduler boot that scans the genesis PROPOSER_SYSTEM prompt for session-doctrine blocks containing explicit expiry markers (regex: /active (?:for next \d+|until) (\d{4}-\d{2}-\d{2})/i). For each block, parse the date; if expired vs today's date, log a HIGH-VISIBILITY warning to logs/doctrine_expiry.log and (configurable) exit the tick with code 2 so the cron mail surfaces it. Specifically targets the S110 audience-diversification rule, S112 pre-send-gate primacy ('active next 20 generations from 2026-04-19'), and S151 archetype rotation ('active for next 30 admissions from 2026-05-14 OR until 2026-06-14'). No prompt edits — just a guard. Reversibility: delete the boot function call.

Target files

hypothesis_engine/scheduler.js hypothesis_engine/moves/genesis.js

Expected effect

On 2026-06-15 the scheduler will warn 'S151 archetype rotation rule expired 2026-06-14'. Currently nothing surfaces this; the doctrine stays in the prompt forever as cargo. After implementation, expired doctrines either get re-ratified by Commander or removed.

Falsifier — what would prove this wrong?

If, after running for 30 days, the watchdog fires on no real rules (zero warnings logged) AND no doctrine block has an expiry the system missed, the watchdog is solving a non-problem and should be removed. If it fires but Commander never acts on the warnings, the gate is noise, not signal.

Evidence that triggered the proposal

D — hypothesis_engine/moves/genesis.js — S110/S112/S151 session-doctrine blocks with stale dates
D — brain/V2_FILTER_DESIGN_v2.3.md — explicit 'shadow-mode observation period' pattern showing TTL discipline exists in design but not in code

Proposer self-score

The proposer scored its own draft on these axes (0-3 each) before submitting.

Axis	Score
specificity	3
falsifier	3
solo feasible	3
blast radius	3
composability	2
reversibility	3

Disposition

Rejected by filter_score. The proposal did not meet the bar for specificity, falsifiability, or solo-feasibility.

Evaluation history

When	Move
2026-06-12 04:30	meta_filter_score
2026-06-09 04:05	meta_genesis