Repository navigation
id: Path to Phase 12 — ordered prerequisite queue (CI trust → validation → journal → visibility → remaining F11) #1235
Description
Path to Phase 12 — the ordered work queue
This issue is the single ordered queue for everything that must land before Phase 12 feature work starts. The roadmap (planning/roadmaps/id.md) points here; the repo queue claims work in this order (packet priorities encode the same sequence); the Phase 12 epic is #534.
How work is picked (so nobody has to guess)
- Tier 1 — this list, top to bottom. Labels:
priority/high+now. Queue packets carry descending priorities matching the step numbers below, so the worker claims step 1 before step 2. - Tier 2 — Phase 12 (label
next): id: F12.1 apply wiring — module install + schedules reconciliation #807 F12.1, id(world): F12.2 world forking and templates #556 F12.2, id(world): F14.6 builder and moderator authority through session frames (F12.3 remainder) #835 F12.3 remainder, id: F12.4 provider registry — capabilities as manifest + provider components #1061 F12.4, id: F12.5 first new providers — kv, blob, http.fetch, notify #1062 F12.5, id: F12.6 audit log and OpenTelemetry export #1063 F12.6, id: F12.7 ABI specification and conformance suite #1064 F12.7, id: F12.8 guest SDKs — Rust + Zig/AssemblyScript, component-model decision #1065 F12.8, id: F12.9 program upgrade with state migration and rollback #1066 F12.9, id: F12.10 fair scheduling and per-account quotas #1067 F12.10, id: F12.11 delta and binary frames (screen patches, resume tokens) #805 F12.11, id(world): F12.12 many worlds per node: 1,000 idle / 100 active with a per-world memory budget #557 F12.12, id: F12.13 journal replication (read replicas over a signed stream) #806 F12.13, id: F12.14 portals — cross-world messaging by mutual grant #1068 F12.14, id: F12.15id world dev: watch, rebuild, hot-swap, fixture replay, fuzz harness #558 F12.15, id: F12.16id world doctor#559 done F12.16, id: F12.17 trust and provenance — module signatures against an admin trust list #1069 F12.17, id(world): F12.18 denial-of-service test suite in CI #560 F12.18. Designs run through id: Phase 12 designs to run through the research workflow #534 first. - Tier 3 — Phase 13 + ideas (
priority/low): id: Phase 13 F13.3 SSH-over-iroh reachability (and iroh-over-SSH fallback) #785–id: Phase 13 F13.8 multi-server, multi-client topology; client-only mode always supported #790, id: long-term — group encryption and authorization (BeeKEM / p2panda-encryption) #1070–id: idea — migrate the web UI from HTMX to Datastar #1073.
The order, and why
CI trust comes first because every validation verdict below is only as good as the test signal it reads. Validations then run in phase order — each audit produces the gap list the following work clears, and the earlier phases are the foundation the later ones extend. Journal compatibility (#227) precedes Phase 12 because worlds-as-data builds on the journal format.
- Step 1 — Stabilize shared-state failures in Firefox E2E CI #229 Stabilize shared-state failures in Firefox E2E CI — DONE 2026-10-26 (queue worker, PR test(id): per-spec-file e2e isolation for the Firefox shared-state cluster (#229) #987, issue auto-closed on merge)
- Step 2 — Bulk LogSync test retries a mid-stream reset instead of explaining it #241 Bulk LogSync test retries a mid-stream reset instead of explaining it (flaky CI test) — DONE 2026-10-28 (issue closed)
- Step 3 — id(ci): F11.4 fast CI lane under 15 minutes #551 F11.4 fast CI lane under 15 minutes — DONE 2026-10-27 (issue closed)
- Step 4 — id: validation — Phases 0–8 + platform completion acceptance audit #1075 Validate Phases 0–8 and the platform-completion brief (audit + tests) — DONE 2026-10-27 (issue closed)
- Step 5 — id: validation — Phase 9 portable platform #1076 Validate Phase 9: portable screens, Roc libraries, collaboration (audit + tests) — DONE 2026-10-27 (issue closed)
- Step 6 — id: validation — Phase 10 worlds as places #1077 Validate Phase 10: profiles, capability ceilings, roles, fixtures (audit + tests) — DONE 2026-10-27 (issue closed)
- Step 7 — id: validation — delivered Phase 11 items (claimed-done audit) #1078 Validate the delivered Phase 11 items (audit + tests) — DONE 2026-10-27 (queue task 1259 audit complete, issue closed with the closeout table: 7 of 9 items verified by named passing tests; F11.4 regression filed as id(ci): F11.4 regression — fast-lane median PR feedback is 19m09s over the last ten runs (exit: under 15m) #1401, F11.5 partial tracked in id: F11.5 injected-clock exit criterion not literally met — polling sleeps remain in world tests #1326, F11.10 enforcement gap filed as id: F11.10 large-module split has no automated enforcement — add a production file-size check to the fast lane #1438)
- Step 8 — Define rollback compatibility for world profile journal entries #227 Define rollback compatibility for world profile journal entries — DONE 2026-10-27 (issue closed)
- Step 9 — id(world): F11.7 host metrics, Prometheus endpoint and tracing spans #553 F11.7 host metrics, Prometheus endpoint and tracing spans — DONE 2026-10-30 (PR feat(id): add admin-protected prometheus metrics and tracing spans #1715 merged; endpoint and tracing spans)
- Step 10 — id(ci): F11.8 benchmark harness with committed baselines #539 F11.8 benchmark harness with committed baselines — DONE 2026-10-27 (issue closed)
- Step 11 — id(world): F11.9 bytes-per-frame baseline table #542 F11.9 bytes-per-frame baseline table — DONE 2026-10-27 (PR test(id): F11.9 bytes-per-frame baseline for checked-in examples (#542) #1429 merged after CI passed)
- Step 12 — id(roc): F11.15 smaller example modules (wasm-opt -Os, strip, <=400 KB) #555 F11.15 smaller example modules (wasm-opt -Os, strip, ≤400 KB) — DONE 2026-10-27 (PR id(roc): F11.15 smaller example modules — wasm-opt -Os + strip, all 7 rebuilt ≤400 KB (#555) #1453 merged after CI passed)
- Step 13 — id(roc): F11.18 pin the Roc compiler for checked-in example modules and rebuild them in CI #541 F11.18 pin the Roc compiler for checked-in example modules and rebuild them in CI — DONE 2026-11-03 (PR id(roc): pin and rebuild checked-in example modules (#541) #3883 merged)
- Step 14 — id(world): F11.16 replay self-check (
id world verify) #544 F11.16 replay self-check (id world verify) — DONE 2026-10-27 (issue closed) - Continuous — id: Phase 12 designs to run through the research workflow #534 Phase 12 design workflow (designs land ahead of each F12 item's implementation)
Working rules for whoever picks these up
- One issue per validation phase is deliberate: each audit's job is to verify its phase against its plan, add the missing tests, and file a separate issue for every gap found — the follow-ups are the real work list, and they join this queue by label (
priority/high+nowwhile Phase 12 is blocked on them). - Drop rule: any step that proves blocked, wrong, or superseded gets parked or closed with a note saying why, and the queue moves on. Never silently stall. Closing a step as superseded is always allowed; no permission needed.
- If a step's audit finds the phase is NOT actually delivered, say so plainly on that issue and file the missing work — that is the audit succeeding, not failing.
Dashboard: org Project #4, Area id-train, Horizon Week. Mirrored in the Grist Program roadmap ("id — Path to Phase 12").
Metadata
Metadata
Assignees
Labels
Package/app: id (pkgs/ or apps/ in this repo)Large: multi-day or open-ended; expect staged check-insMeta-issue grouping multiple items (org Project Type=Epic)New feature or capability requestIntake review done: acceptance criteria, links, and normalized labels addedFully doable remotely: design, config, code, cloudOrg Project gate: active priority — orchestrator adds to the boardImportant and time-sensitiveFiled directly by a humanQueue packet kind: verify, reproduce, and route this item
Activity
developing-today commentedon Oct 27, 2026
CODE-367
dezren39 commentedon Oct 27, 2026
Queue state (2026-10-26 ~23:05 CDT): all 14 steps are enqueued in
repo-health-code-pilotas triage packets at priority 90 (top of the design scale; the pre-existing queue standard is 70), enqueued in step order — task ids run #1247–#1268 in the agent queue. The worker claims highest-priority first, so tier 1 now preempts the older id-web bug queue; within the tier, this checklist + the sequence comments on #1075–#1078 carry the order. Each issue also carriesqueue/queued.dezren39 commentedon Oct 27, 2026
Intake review
Related: Epic #534 (Phase 12), steps: #229 (Step 1), #241 (Step 2), #551 (Step 3), #1075–#1078 (validation steps), #227 (journal compatibility).
Notes: This is the ordered prerequisite queue itself — a coordination artifact as much as a work item. It already carries priority/high + effort/l + the epic label; this pass added acceptance criteria and
meta/enrichedonly. Note Step 3 (#551) currently has a queue blocker: its canonical triage dedupe key is held by an inert shadow-queue task (flagged by the fleet monitor this run for operator repair).Risks: The list decays if step issues close without this checklist being updated — whoever closes a step issue should tick it here in the same pass.
Suggested approach: No separate implementation: work the steps top-down through the queue; review this list in the fleet's regular reporting.
dezren39 commentedon Oct 27, 2026
Correction + queue verification (2026-10-26 ~23:45 CDT, via direct DB read of agent.claim_repo_task): the claim order is priority ASC, then created_at ASC — lower priority number = claimed sooner. My earlier note on this issue ('priority 90, highest first') was exactly backwards: 90 is the LAST band. Fixed in the database: the 13 open steps now hold priorities 10–22 in step order (step 2 #241 = 10 … step 14 #544 = 22), ahead of the entire existing queue (next band is 30). Step 1 (#229) completed tonight by the queue worker (PR #987) and is checked off. Two enqueue lessons recorded: the dedupe key for #229 collided with its own completed Oct 25 task, and #551's triage key collided with a completed shadow-queue investigation (agent task 1064), so #551 was re-issued under the fix key as task 1283. Verified from agent.tasks: the head of repo-health-code-pilot is now steps 2–14 in order.
12 remaining items
developing-today commentedon Nov 3, 2026
agent-note:v1
state: reviewed (coverage loop-back)
Coverage pass 2026-11-03, loop-back review: this issue was re-reviewed (drift / overlap / already-handled / stale / blockers / ordering) so every open issue in the four repos is reviewed and in the system. Verdict: still live; in the system as task 7223 (triage, queued, priority 50) in repo-health-code-pilot. Labels audited and synced. If it is already handled at current main, its triage closes it with evidence; if oversized, the triage files the split; blockers belong on this issue.
Found via: coverage loop-back 2026-11-03
dezren39 commentedon Nov 3, 2026
Lane code-j claimed task 7223 (triage of issue #1235); execution lane is opencode, so task 7223 is handed off to the opencode claimant, which launches the bound session that drives task 7223 to its terminal state. Issue #1235 is still OPEN with no hard-stop labels (verified fresh this shift).
dezren39 commentedon Nov 4, 2026
agent-note:v1
state: picked-up
queue: repo-health-code-pilot
task: 7223 (triage, worker repo-worker-code, lane c29174f1-48e0-4b13-b4ff-9b73ab67e9ab)
by: openchamber-scheduled-lane
at: 2026-11-04T02:07Z
Claimed for a fresh state check of the Phase 12 prerequisite order; issue is open and carrying the queue claimed/in-progress labels.
dezren39 commentedon Nov 4, 2026
agent-note:v1
state: triaged
queue: repo-health-code-pilot
task: 7223 (triage, worker repo-worker-code, lane c29174f1-48e0-4b13-b4ff-9b73ab67e9ab)
by: openchamber-scheduled-lane
at: 2026-11-04T02:15Z
Triage of #1235 at origin/main 3237ef8
Every prerequisite step on the ordered list is closed. Verified with GraphQL issue state on 2026-11-04 (UTC ~02:0x).
Step 1 (#229) was already done. Continuous item #534 (Phase 12 design epic) is still OPEN, as expected.
Blockers named: none. The prerequisite queue has no open blocker.
Stale state, not changed here (other lanes own those labels):
Recommendation: the queue order has been consumed. #1235 can close, or stay open as the Phase 12 index until #534 lands. That is Drew's call, so the issue is left open.
dezren39 commentedon Nov 4, 2026
agent-note:v1
state: triaged
queue: repo-health-code-pilot
task: 7223 (triage, worker repo-worker-code, lane c29174f1-48e0-4b13-b4ff-9b73ab67e9ab)
by: openchamber-scheduled-lane
at: 2026-11-04T02:20Z
Correction / completion evidence for the earlier triage note: #553 comments about the remaining slices predate PR #1715. Fresh GitHub state confirms PR #1715 merged 2026-10-30; it implements the admin-token Prometheus metrics endpoint and per-command tracing spans and says Fixes #553. #553 is complete, not an outstanding blocker; its queue/queued and status/in-review labels are stale. #541 PR #3883 is also merged (2026-11-03), despite older parked notes. #542 PR #1429 and #555 PR #1453 are merged; all remaining listed prerequisites are closed.
I refreshed the checklist above: steps 1-14 are complete with close dates and merge evidence; continuous #534 remains OPEN (last checked 2026-11-04; current roadmap still treats Phase 12 designs as in progress). #1235 stays open as the index until #534 / Phase 12 lands. No follow-up task is needed.
dezren39 commentedon Nov 4, 2026
agent-note:v1
state: done
queue: repo-health-code-pilot
task: 7223 (triage, worker repo-worker-code, lane c29174f1-48e0-4b13-b4ff-9b73ab67e9ab)
by: openchamber-scheduled-lane
at: 2026-11-04T02:22Z
Triage complete. Steps 1-14 are all complete; the checklist was refreshed with closure dates and merged PR evidence. Phase 12 design epic #534 remains open/in progress, so #1235 remains open as its index. Removed the queue/claimed, status/in-progress, and work/assigned lifecycle labels from this issue now that task 7223 is terminal.