docs: in-progress/ marker — arc stage 3 is the active slice

- one marker doc, deleted on landing; board doctrine names the
  second folder exception
- board In-progress row was stale (nothing active + dead anchor);
  now points at marker + arc plan tasks 7-8

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This commit is contained in:
shoney.arickathil 2026-08-21 06:19:03 +02:00
parent 2bd42b4a2f
commit f691818c4b
3 changed files with 50 additions and 5 deletions

View file

@ -12,7 +12,8 @@ banner and this board change. ONE exception by directive (2026-08-20):
story iteration files move physically — landed ones into
`stories/language-runtime-database/done/`, brainstorm-needing ones into
`refine/`, held ones into `hold/` (2026-08-21); ready/in-flight stay at
the root. Every plan and phase doc opens with a
the root. Second exception (2026-08-21): the active slice's one marker
doc lives in `docs/in-progress/` and is deleted when the slice lands. Every plan and phase doc opens with a
`> **Status:**` banner linking back here; normative contracts
(`plan/oop-vm/`), exploration studies, reference docs and the
discarded/learnings registers carry none by design.
@ -197,11 +198,11 @@ that sequences its tasks. Read one, approve, then the next starts.
| Track | Item | Where |
| -------- | --------------------------------------------------------------------------- | ---------------------------------------------------------- |
| Language | nothing active — the framework v1-polish slice landed 2026-08-20 (branch framework-v1, awaiting merge); next per the order: brainstorm 20/21's forks | [order](#implementation-order-re-sequenced-2026-08-20--code-review-pass) |
| Runtime | **the 8+11 arc, stage 3: transparent DB actor** — first slice of the concurrency chain (2026-08-21) | [marker doc](in-progress/2026-08-21-arc-stage-3.md) · [arc plan Tasks 7–8](superpowers/plans/2026-08-20-shard-fiber-arc.md) |
Off-goal work is parked; the goal (2026-08-20) is the web framework as a
polished micro-framework v1 — iteration 17 (library kind + `internal/`) is
parked with its spec + plan ready on branch `library-internal`.
The active slice's marker doc lives in [`in-progress/`](in-progress/) —
one file, deleted when the slice lands. Everything else pending is the
concurrency chain (see *Pending* below); the held tail is in `hold/`.
### Landed 2026-08-14 — the compile-and-run milestone

View file

@ -0,0 +1,44 @@
# 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](../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`](../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](../stories/language-runtime-database/08-shard-actor-runtime.md)
(stage 3 is its remaining scope)
- [11 — fibers](../stories/language-runtime-database/11-fibers.md)
(substance landed stages 1+2; closes with this slice — note: `fs`
still 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.