shoney.arickathil
1fe808b7a4
- `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>
60 lines
2.3 KiB
Markdown
60 lines
2.3 KiB
Markdown
---
|
|
iteration: "4"
|
|
status: done
|
|
readiness: ready
|
|
---
|
|
|
|
# Iteration 4 — single binary end-to-end
|
|
|
|
> Format: `product/story-iteration-template`. Part of
|
|
> [Story — one language, one runtime, one database, one binary](00-story.md).
|
|
|
|
## Goals
|
|
|
|
- The two halves meet: `woc` emits `.wob` images the VM's loader accepts,
|
|
a conformance corpus pins language behavior from both sides, and
|
|
`woc build` produces the story's headline artifact — one self-contained
|
|
executable.
|
|
- This is the milestone where "a new language with arithmetic and garbage
|
|
collection" is demonstrably real: source in, running binary out.
|
|
|
|
## Acceptance Criteria
|
|
|
|
- What to achieve?
|
|
- **Given** the pricing demo's logic subset,
|
|
- **when** `woc` compiles it on a developer laptop,
|
|
- **then** compilation finishes in under 100 ms and `wovm` runs the
|
|
resulting module with correct output.
|
|
- What to achieve?
|
|
- **Given** the three-kind conformance corpus (runs with expected
|
|
stdout; must-fail-compile with expected `WO-E###`; must-trap with
|
|
expected trap code),
|
|
- **when** the harness runs the full suite,
|
|
- **then** every fixture lands in its expected bucket and ASan/Valgrind
|
|
report zero errors across the suite.
|
|
- What to achieve?
|
|
- **Given** `woc build` on a sample project,
|
|
- **when** the produced binary is copied to a machine with no OCaml, no
|
|
compiler, nothing but Linux,
|
|
- **then** it runs with no arguments and behaves identically.
|
|
|
|
## Out Of Scope
|
|
|
|
- Anything beyond the milestone grammar (iteration 5 grows the surface).
|
|
- Hot reload / deployment mechanics (iteration 11 — but the self-exec
|
|
trailer this iteration ships is its foundation).
|
|
|
|
## Info
|
|
|
|
- The loader's validation battery is the executable spec: every image
|
|
`emit` produces must round-trip through it — the golden rule both
|
|
test suites enforce.
|
|
- The corpus becomes the spine every later iteration extends (lang, sys,
|
|
db, actor fixture kinds already scaffolded under `tests/corpus/`).
|
|
|
|
## Proposed Solution
|
|
|
|
- Execute the existing plan: `compiler/plan/2026-08-01-wob-emit-e2e-single-binary.md`
|
|
(emitter with ownership lowering + drop maps + vtables, corpus harness,
|
|
pricing corpus, ownership/trap corpora, gc pump e2e, `woc build` trailer,
|
|
`just oop-accept` gate over the five spec success criteria).
|