commit aa2b1e0d7c3a084710f87f8b327513dfda3f2a67
parent b1750da444c7298dc78788cbc98daaac0e2de934
Author: I Mean I'm Just Saying <imeanimjustsaying@kiwifarms.st>
Date: Sun, 13 Sep 2026 08:56:28 -0400
plans: gate A passed on the production editor, and phase 1 lands
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Diffstat:
1 file changed, 18 insertions(+), 0 deletions(-)
diff --git a/plans/one-core-phase-1.md b/plans/one-core-phase-1.md
@@ -1547,3 +1547,21 @@ where it read *Idle*.
fixture site so the export webServer answers 200. `git add -A` in this repo
stages that symlink into the commit and carries the panic into the worktree —
add by path.
+
+## Gate A — PASSED 2026-09-13
+
+Run by the operator on the production editor (the primary checkout serving the
+`one-core/phase-1` tip `e74f005`, restarted with `-H 0.0.0.0`), with
+`autoQueue.digest.enabled: true` and the lane's strict tree narrowed to one leaf,
+`{ "type": "channel", "value": "ObviousRises-rumble" }`; `held: false`; no
+`autoQueue.backfill` block added. The operator reports **every assertion of the
+gate held**: the Auto-digest section read *Runner running*, the pass dispatched
+units and the channel's `backfill.digest.missing` fell, the mid-pass restart
+brought the runner back unaided with Recent picks continuing, and Hold/resume left
+it *running* with `Idle — the lane is held`. The per-step numbers (units
+dispatched, missing before/after, any observed yield) were not written down at the
+time; add them here if they were kept.
+
+Consequence: the 1.3 retirements stand, and the 2026-09 integration
+(`integrate/2026-09-storage-priority`, Phase 2 included) fast-forwards to `main`.
+Gate B (the backfill lane on production) is still owed before that lane is armed.
