shoney.arickathil
59f884e1f8
- 08 landed in discarded/ by mis-drop, swept into prior commit with two dead links; corrected to stories/.../in-progress/ per intent - 11 joins it (one arc, active slice) - board doctrine: active stories bucket named; all links re-verified Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2 KiB
In progress — the 8+11 arc, stage 3: the transparent DB actor
Status: 🔄 in progress (started 2026-08-21) — first slice of the concurrency chain stage 3 → 22 → 31 → 24 → 23. Board: ../00-status.md.
This folder holds ONE marker doc: the slice being executed right now, so the active work is findable without reading the board. When the slice lands, the board's done section takes the record and this file is deleted — the plan and stories stay the authority.
What
Stage 3 (Tasks 7–8) of the plan of record,
superpowers/plans/2026-08-20-shard-fiber-arc.md:
engine calls off the owner shard become message sends with parked
replies. A correctness fix, not an optimization — rt.db is set only on
the primary (runtime/src/main.c), worker VMs are zero-initialized, so
any DB statement off the primary traps WO_T_DB today.
Why now
Developer decision 2026-08-21: correctness before measurement. Fixing the hole first lets iteration 22's single benchmark campaign cover single- AND multi-shard honestly.
Stories
- 8 — shard-actor runtime (stage 3 is its remaining scope)
- 11 — fibers
(substance landed stages 1+2; closes with this slice — note:
fsstill blocks instead of parking, land it here or re-scope 11's criterion explicitly at close)
Definition of done
- Plan Tasks 7–8 checked off; full battery green (
just woc-test,just oop-e2e,just deps-accept,just web-app,just log-watcher,just employee,just fibers) — multi-shard DB answers byte-identical to single-shard, WAL ack-after-durable unchanged. - Stories 08 + 11 move to
stories/language-runtime-database/done/together; board updated in the same change. - Next slice: iteration 22 (measurement backbone) replaces this file.