shoney.arickathil
6e997759e5
- five stories status: done; 00-story records the one-run landing - spec History: three implementation amendments (Signal record not scalar, caller-owned stdio fds, handler-latch instead of signalfd) - board NEXT PLAN entry with measured findings (zero transport code added; the tty-across-the-socket handover proven; the double-raw refusal restoring the terminal — the "bug" that was the design working); section rows flipped; graph nodes green - CODE-LOGIC.md: the runtime-v2 section - full belt quoted on the board: suites 0 fail both flavors (test_proc 193/0, test_term 60/0), woc 557/0, subprocess 12/0, site 23/0 Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> (cherry picked from commit bc1b4f070693eb755ad6a9fd0c853fb3e2bda347)
3.4 KiB
Story — runtime-v2: the runtime beyond sockets
The fifth track. Where databasev2/ takes
the database beyond RAM, this track takes the I/O plane beyond sockets:
processes, terminals and signals — the third of the native surface
the runtime never learned. Iterations 8/11/35 taught it sockets, the
program-mode stdlib taught it files, and iteration
42 (bounded
subprocess, ✅ on master 2026-09-01) opened this arc from inside the
language track before the arc had a name.
Numbering restarts at 1 and is local to this track; frontmatter carries
track: runtime-v2. Status rules are the repo's, unchanged.
The problem, stated once
A shard's plane multiplexes fds it created itself — listeners, accepted
sockets, and (since 42) the pipe/pidfd bundle of a one-shot child. That
is not enough for any program whose job is other programs: a long-lived
child's output has no path into an actor, a pseudo-terminal cannot be
allocated or resized, a signal cannot become a message, a tty the
process was GIVEN cannot be adopted into raw mode, and an fd cannot
cross a unix socket. Five seams, each builtin-sized, each in
runtime/src/ with a types.ml table row as its entire compiler cost
(the 42 precedent — no emit.ml change).
The iterations
| # | Iteration | What it adds |
|---|---|---|
| 1 | streaming subprocess | a long-lived child as a first-class peer: output in, stdin out, exit as a notice |
| 2 | PTY | openpty, controlling terminal, resize ioctls — a child that believes it owns a terminal |
| 3 | signals as events | SIGWINCH/SIGCHLD/… as mailbox messages — the seam 42 deferred to its real consumer |
| 4 | termios adoption | the process's OWN tty into raw mode and back — adopting a terminal it was given |
| 5 | fd passing | SCM_RIGHTS over unix sockets — detach/attach's foundation, and the Wayland stage's later |
ALL FIVE LANDED 2026-09-02, one execution run (plan:
2026-09-01-runtime-v2.md;
three implementation amendments in the spec's History). Gates:
test_proc 193/0 + test_term 60/0 inside a fully green ASan suite on
both dispatch flavors, woc-test 557/0, subprocess-accept 12/0,
site-accept 23/0. The board's NEXT PLAN entry carries the findings.
All five were readiness: ready since the track-wide brainstorm
(spec,
2026-09-01), which also settled the build order: only 1 → 2 is chained
(spawn_pty extends spawn's plumbing); 3, 4 and 5 are startable alone,
today — the pull-transport decision (a child is fds; the net verbs
drive them) broke the old 1→2→3 chain. Edges live in
dependency graph section 6; each
iteration writes its own implementation plan when it starts.
The driving workload
wmux/ — the terminal multiplexer — consumes all
five; that track owns the product, this one owns the seams. Sibling
consumers per iteration are named in each story (skillhost 28, the zen
CDP driver, the alacritty Wayland stage). The doctrine carried over from
42: every resource a ceiling, every violation a refusal by name, no
zombie and no orphan ever, .dev/reference/tmux as the measured
reference.