Gates — The Consequence Dial

Corroboration counting v2

Count = DISTINCT run_id × DISTINCT provenance-fingerprint pairs. NEVER file dates. N proposals from one run are one run; N proposals citing one source are one source — the poisoned-corroboration hole closes at the deterministic layer, where injection can't reach. Days appear only as a staleness ceiling (observations older than day_ceiling discarded before counting); no other day arithmetic exists in the library. The v1 day-collapse bug is dead: consecutive means consecutive qualifying runs, never calendar-day adjacency (audit R6). Malformed proposals are killed, never bucketed (audit R3).

Cooldowns — damping decoupled from thresholds v2

A direction key that executed cannot re-fire, and its reversal key (REV:<key>, via the reversals map) cannot fire, for K epochs (default K=2) — denominated in evidence epochs, not days. The cooldown starts on completed execution, not on gate pass. SUPPRESSED ≠ BLOCKED: a cooldown-suppressed key returns SUPPRESSED_BY_COOLDOWN, which never feeds the deadlock clock (audit R8) — a working gate must not escalate to the arbiter because its own damping held. This is what makes threshold-1 building safe.

Consumption — no standing re-execution v2

A direction that executes is marked consumed and cannot re-qualify from pre-consumption (stale) evidence — the v1 standing re-execution bug is fixed (audit R2). Re-qualification requires fresh observations with epoch > consumed_epoch. Consumption is written by the executor alongside record_execution; the gate checks it before counting. Consumed keys report as CONSUMED — distinct from blocked and suppressed.

Graduation — evidence predicates only v2

Each ramp phase carries machine-checkable graduate_when predicates over gate state and declared metric files: counts, streaks, rates, population-stability tests, named events, readiness flags. Time-elapsed predicates are REJECTED at config load. On criteria met: phase bump, append to ramp-events.jsonl, ledger alarm at info. Demotion on regression uses the same path in reverse; both are auditable ramp events.

The console — authority from location v2

force_pass / hold / demote / phase_override, read from data/gates/console/<gate>.json — writable only by the command center and ML, OUTSIDE the worker-writable tree, enforced by filesystem permissions and verified by the self-knowledge sweep. Authority flows from where the file lives and who can write there, never from what a proposal says. Force-passed keys enter qualified with forced:true and full ledger mirroring; single-shot entries are consumed after use. The console CANNOT clear a values-floor block. Always available, never necessary.

AUTO_PASS — deleted, not migrated DELETED

v1's playbook gate auto-passed any proposal whose YAML contained source: human — an injection-grade bypass: a field inside attacker-influenceable worker output granting instant bypass; one successful injection defeats the gate entirely (audit R4). Gone by construction: provenance must be attested by the ingesting sensor, never declared by the proposer (self-declared provenance is stripped); authority-passes are console force-pass entries outside the worker-writable tree; and the library exposes no hook for any proposal-content-triggered bypass — a gate script found reading proposal fields for pass/skip decisions is a self-knowledge finding.

strategy-consensus

threshold

3

day_ceiling

14 (staleness only)

stakes

Y Y n n n

phases

build @ 2 graduate_when: {"baselines_exist": ["market-baselines"], "pass_streak": 3}
steady @ 3

additive-knowledge

threshold

2

day_ceiling

30 (staleness only)

phases

build @ 1 graduate_when: {"new_key_rate_below": {"pct": 5, "consecutive_cycles": 3}}
steady @ 2

playbook

like

additive-knowledge

worker-retire

threshold

4

day_ceiling

30 (staleness only)

min_provenance

2

reviewer

True

stakes

Y Y n n n

rich-media-opportunity

threshold

2

day_ceiling

7 (staleness only)

params

{"daily_cap": 50}

strategy-consensus-reversals-example

like

strategy-consensus

reversals

shift-to-comparison-content ⇆ shift-to-editorial-content; expand-video-embeds ⇆ reduce-video-embeds