# Dependency graphs — iterations and framework features > Companion to [00-status.md](stories/00-status.md) (states live THERE; this page > carries the edges). An arrow `A --> B` means **A must exist before B**; > a dashed arrow is a scope DIRECTIVE, not a technical dependency. Use it > to pick the next implementation: anything whose incoming arrows are all > green is startable today. Rebuilt 2026-08-20 from a sweep of every > story/spec/plan markdown (the "misses" pass: iteration 17's outgoing > edges, the concurrency chain, the post-12 parked drain, 9b→10, > 14's gap fan-out, 20's fiber caveat). ## 1. Story iterations ```mermaid flowchart TD classDef done fill:#1a7f37,color:#fff,stroke:none classDef parked fill:#6e7781,color:#fff,stroke:none classDef specd fill:#0969da,color:#fff,stroke:none classDef open fill:#eac54f,color:#000,stroke:none FOUND["1–6 foundation: doctrine, VM, compiler, binary, surface, stdlib"]:::done I7["7 log-watcher proof"]:::done I7b["7b inferred GC + per-shard mark-sweep"]:::done I9["9 database engine"]:::done I9b["9b @table + query"]:::done I15["15 deps package manager"]:::done I16["16 web framework v1 core"]:::done I17["17 library kind + internal/ (PARKED — spec+plan ready, branch library-internal)"]:::parked FWREORG["framework internal/ reorg + check mode (kills the --emit workaround; WO-E108/E109 reserved)"]:::parked I18["18 framework v2: transaction{} + cache/flags/jobs (spec APPROVED — the next implementation)"]:::specd I9c["20 cross-program tables (half-built)"]:::open I9d["21 keypair attach auth (half-built; crypto+handshake already on its branch)"]:::open I9e["22 durability + throughput baseline ✅ 2026-08-21"]:::done I8["8 shard-actor runtime ✅ 2026-08-21"]:::done I9f["23 io_uring group-commit"]:::open I10["10 HTTP service layer (lowers onto the framework)"]:::open I11["11 fibers ✅ 2026-08-21"]:::done I12["12 blue-green deploy"]:::open I13["13 metaprogramming @derive"]:::open I14["14 skillhost workload (demoted)"]:::open I9g["27 query grammar corpus (likely collapses)"]:::open GAPS["14's gap fan-out: bounded subprocess, stdin/stdout transport, fs metadata, FFI-vs-out-of-process"]:::open DRAIN["post-12 parked drain: pub(read)/using/#if, WO-E225, ADT roster, group-by"]:::parked FOUND --> I7 FOUND --> I9 I7 --> I7b I9 --> I9b I9b --> I15 I15 --> I16 I15 --> I17 I16 --> I17 I17 --> FWREORG I9 --> I18 I16 --> I18 I9 --> I9c I9c --> I9d I9c --> I10 I9b --> I10 I16 --> I10 I9b --> I9e I7b --> I8 I9e --> I9f I8 --> I9f I8 --> I11 I9 --> I12 I10 --> I12 I9g --> I14 I7 --> I14 I14 --> GAPS I12 -.scope directive.-> I13 I12 -.scope directive.-> DRAIN ``` Reading it: **18 is the only spec-approved open node with all prerequisites green — the next implementation.** After 18: 20/21 and 22 are startable (chosen order: 20/21 first — half-built branches rot). 17 unparks on directive: its prerequisites landed, its spec+plan wait on branch `library-internal`, and its landing brings the framework reorg node with it. 13 and the parked drain sit behind 12 by the 2026-08-08 scope directive (dashed), not by any technical edge. ## 2. The concurrency chain (iterations 8 / 23 / 11 and everything they gate) The runtime's concurrency work is the single biggest unlocker — every ⏸ row in the framework ledger and two v2 follow-ons hang off it. ```mermaid flowchart TD classDef rt fill:#8250df,color:#fff,stroke:none classDef gated fill:#eac54f,color:#000,stroke:none classDef v2 fill:#0969da,color:#fff,stroke:none I7b2["7b per-shard collector (done — the precondition 8 waited on)"]:::rt I8x["8 shard-actor runtime: thread-per-core, ownership-move messages"]:::rt I9fx["23 io_uring group-commit (batch = the shard tick)"]:::rt I11x["11 fibers: reduction-budget preemption, blocking builtins park"]:::rt I9ex["22 baseline (numbers 8/23 sign against)"]:::rt KEEPAL["keep-alive parking retired (close-when-idle policy dies; parked fds)"]:::gated H2C2["h2c HTTP/2 cleartext (spec §C: also needs 23)"]:::gated STREAM2["request body streaming + backpressure"]:::gated SRESP2["streaming responses + explicit commit point"]:::gated CANCEL2["per-request cancellation propagation"]:::gated PUBSUB2["pub/sub + WebSockets (rejected until here)"]:::gated ASYNC9C["20 async attach statements (rejected-for-now alternative)"]:::gated TIMEOUTS2["idle timeouts become schedulable (net seam still needed)"]:::gated FIBJOBS2["fiber-scheduled jobs (replaces drain-on-request; queue table stays)"]:::v2 CANCELRB["cancellation → transaction rollback"]:::v2 I18x["18 transaction{} + jobs"]:::v2 I7b2 --> I8x I9ex --> I9fx I8x --> I9fx I8x --> I11x I8x --> KEEPAL I11x --> KEEPAL I8x --> H2C2 I9fx --> H2C2 I11x --> H2C2 I11x --> STREAM2 I11x --> SRESP2 I11x --> CANCEL2 I8x --> PUBSUB2 I11x --> PUBSUB2 I11x --> ASYNC9C I11x --> TIMEOUTS2 I11x --> FIBJOBS2 I18x --> FIBJOBS2 I11x --> CANCELRB I18x --> CANCELRB CANCEL2 --> CANCELRB ``` ## 3. Framework v1 — remaining ledger items Three gates recur: **net seams** (runtime `net` builtins), the **crypto fork** (bitwise operators + hex literals landed with iteration 36, so digests are now expressible in pure `.wo` — pure-`.wo` vs C-builtin is story 34's brainstorm before the slice), and the **concurrency chain above** (its gated nodes are not repeated here). ```mermaid flowchart TD classDef gate fill:#8250df,color:#fff,stroke:none classDef ready fill:#1a7f37,color:#fff,stroke:none classDef blocked fill:#eac54f,color:#000,stroke:none CORS["CORS middleware"]:::ready SECH["security-headers middleware"]:::ready HOSTV["host validation"]:::ready STRICT["strict-parsing audit (dup/conflicting Content-Length)"]:::ready WILD["wildcard segments *rest"]:::ready PREC["specificity precedence"]:::blocked GROUPS["route groups"]:::ready CTX["req.ctx bag"]:::ready XFF["X-Forwarded-For/-Proto parsing"]:::ready ACCEPT["Accept-driven negotiation"]:::ready NETSEAM["GATE: net runtime seams (timeouts, unix socket, peer address) — story 35 owns"]:::gate TMOUT["read/write/idle timeouts"]:::blocked UNIX["unix socket binding"]:::blocked PEERV["trusted-proxy PEER verification"]:::blocked CRYPTO["GATE: story 34 crypto — C builtins vs pure-.wo (bitwise landed with 36, both possible; brainstorm decides); carriers (Bytes, base64) landed with 19"]:::gate SHA["SHA-256/512, HMAC, CRC32"]:::blocked ETAG["ETag + conditional requests"]:::blocked COOKIE["signed cookies"]:::blocked CSRF["CSRF"]:::blocked SESS["session integrity"]:::blocked HOOKV["webhook verification"]:::blocked JWT["JWT HS256 (HARD STOP after)"]:::blocked RADIX["radix-tree routing"]:::blocked I9E3["GATE: router scan unmeasured — 22's harness landed but benched the DB, not the router; perf-targets entry first"]:::gate STORAGE["storage-integration rows: migrations (future story), eager loading + tenant roots (query-surface work, 9-series)"]:::blocked WILD --> PREC NETSEAM --> TMOUT NETSEAM --> UNIX NETSEAM --> PEERV CRYPTO --> SHA SHA --> ETAG SHA --> COOKIE SHA --> CSRF SHA --> SESS SHA --> HOOKV SHA --> JWT I9E3 --> RADIX ``` Green nodes (CORS, security headers, host validation, strict-parsing audit, wildcards, route groups, `req.ctx`, XFF parsing, Accept negotiation) need nothing — startable in any order, gated by `just web-app`. Note: 21's keypair crypto is its own C implementation (already on branch `keypair-auth`) — it neither waits for nor feeds the crypto-fork gate. ## 4. Framework v2 (iteration 18) — internal order ```mermaid flowchart TD classDef piece fill:#0969da,color:#fff,stroke:none classDef indep fill:#1a7f37,color:#fff,stroke:none classDef later fill:#eac54f,color:#000,stroke:none TXN["transaction{} (engine undo log + language block)"]:::piece JOBS["jobs.wo: wf_jobs + enqueue + JobRunner + idle() drain"]:::piece DEMO["web-app demo: transactional order+confirm, GET /jobs, flags route"]:::piece CACHE["cache.wo: TTL + FIFO"]:::indep FLAGS["flags.wo: wf_flags + read-through map"]:::indep TPRMW["txn-per-request middleware (v1 ledger's storage row; single-thread OK)"]:::later TXN --> JOBS JOBS --> DEMO FLAGS --> DEMO TXN --> TPRMW ``` Cache and flags are dependency-free warm-ups; `transaction { }` is the critical path (the only engine + language work); jobs compose on it; the demo and gate close it. Fiber-scheduled jobs and cancellation→rollback appear in graph 2 — they need iteration 11 as well as 18. ## Maintenance rule When an iteration or slice lands, update its node's class here in the same change that moves the board row — the two documents answer different questions (status vs. edges) and drift kills both.