shoney/writeonce
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
writeonce/docs/stories/language-runtime-database/01-principles-doc.md
shoney.arickathil 1fe808b7a4 docs(stories): add readiness, retire status: refine, sweep all 47 iterations 
- `readiness: ready | refine` is a SECOND axis, orthogonal to status.
  `ready` = the brainstorm is complete and the decisions are LOCKED (a spec
  approved, or the forks explicitly confirmed). `refine` = open forks remain
  and it cannot be planned yet
- `status: refine` RETIRED because it carried both meanings at once, so a held
  iteration with an approved spec (language 18, 26) was indistinguishable from
  one nobody had thought about. status is now purely where the WORK is:
  done | in-progress | pending | hold — `pending` was already the board's own
  rendering word, so nothing new was invented
- all 47 iterations classified from EVIDENCE in their own text, not by guess:
  "the four forks are SETTLED" / "spec + plan approved" / "Approved spec:" for
  ready; "Forks the spec must settle" / "no spec exists yet" for refine. Every
  shipped iteration is ready by definition. 19 done, 5 in-progress, 15
  pending, 8 hold; 27 ready, 20 refine
- two iterations moved refine -> in-progress rather than -> pending: language
  31 and 34 are absorbed into 24 and work on them is literally happening, which
  the board already showed as 🔄 while their frontmatter said otherwise. That
  disagreement is now gone
- board legend, board-views' frontmatter contract, and two new Dataview
  queries updated — the useful one being `readiness: ready AND status:
  pending`, the startable set

WHAT THE NEW AXIS IMMEDIATELY SURFACED: of 15 pending iterations, exactly ONE
is startable — databasev2 4, io_uring group-commit, whose forks were confirmed
settled 2026-08-20. Everything else pending needs a brainstorm first. That was
invisible while one key carried both meanings, and it is now on the board.

Also caught by the sweep, unrelated to readiness but found by cross-checking
frontmatter against the board: SIX duplicate rows. Every iteration moved into
databasev2 was still listed in the LANGUAGE pending table under its retired id
(23, 32, 33, 20, 21, 27) as well as its new one. Stale copies removed. And two
databasev2 rows made claims the sweep contradicts — iteration 1 was billed
"startable today" while its forks are open, and 6 still called itself the
ceiling-raiser after 2 took that role.

Docs only. linkcheck 0 broken / 0 anchors.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
2026-08-27 16:54:45 +02:00

2 KiB
Raw Blame History

iteration status readiness
1 done ready

Iteration 1 — the principles doc

Format: product/story-iteration-template. Part of Story — one language, one runtime, one database, one binary.

Goals

  • The repo gains docs/00-principles.md: one page stating the twelve writeonce principles — the doctrine every later iteration links back to instead of re-arguing.
  • The twelve: one binary is the whole system; zero dependencies (kernel primitives only); memory safety without a GC tax (MVS ownership, opt-in @gc, per-shard collection); no inheritance ever; thread-per-core shards with ownership moves; the runtime never stops (blue-green slots, embedded source); RAM authoritative + WAL durable; samples force the grammar; Linux is the target; capabilities are typed builtins (no FFI); plain diagnostics are the product; the runtime is a recipe box.

Acceptance Criteria

  • What to achieve?
    • Given a new contributor opening docs/,
    • when they read docs/00-principles.md,
    • then each principle is a short statement plus a one-line why plus a link to the spec or doc that enforces it, and no principle contradicts a locked spec decision.
  • What to achieve?
    • Given CLAUDE.md's "Where to read next" list,
    • when the iteration lands,
    • then it contains one pointer line to the principles doc and nothing else about it changed.

Out Of Scope

  • Rewriting or relocating existing doctrine text in specs/plans — the doc links, it does not duplicate.
  • Any .wo example content (iterations 2+ own code-adjacent artifacts).

Info

  • docs/ numbering starts at 01-problem.md; the 00- slot is free and reads as "start here".
  • Spec governing this slice: docs/superpowers/specs/2026-08-07-logwatcher-sample-and-principles-design.md §3.

Proposed Solution

  • Author the page with the twelve principles in the order listed in the governing spec; verify every link resolves; add the CLAUDE.md pointer line; record the commit draft in .dev/commit.md.