writeonce/docs/stories/language-runtime-database/04-single-binary-e2e.md
shoney.arickathil c0b0dbb846 docs: audit all markdown against the code, fix findings, flatten status folders
- README: shipped concurrency/HTTP/WebSockets sat in the roadmap as "not yet
  available"; "no package manager" contradicted [deps]; the deps example
  would not have compiled (the key IS the module name)
- runtime/README: leads with wovm, wo-rt.c demoted to a historical section;
  dropped 2 nonexistent recipes, crates/rt, @gc refcounting, 13 suites -> 18
- employee + log-watcher READMEs claimed "does not compile"; both are gates
- error catalog: +10 emitted codes incl WO-E250, the only diagnostic the
  shipped query surface raises; recorded why the sweep rotted
- language-surface: group-by parses, then the typechecker refuses it
- 00-code-review + 00-link-audit re-run; history kept, not rewritten
- 48 dead Rust-era exploration links de-linked rather than re-pointed (their
  prose names the retired plan by number); successor map -> discarded.md
- 08-project-structure: compiler/plan/ never existed; corpus has 9 dirs, 5 empty
- releasing.md: dropped a --draft step the workflow never had
- new docs/00-doc-audit.md: findings + disposition, incl one row where the
  audit was wrong and the doc it accused was right
- status folders removed: 34 stories flat, status only in frontmatter; 252
  links recomputed from resolved paths; board/board-views/structure retaught
- story 24 -> in-progress, since frontmatter is now the only truth
- new iteration 38: fs mutation verbs + net.connect, the two capability
  families no iteration owned
- new iteration 39: gofiber/fiber v3.5.0 parity study. The ledger called
  CSRF/sessions unblocked by iteration 34's HMAC, but the runtime has no
  source of randomness at all
- linkcheck skips .dev/.superpowers: 0 broken paths, 0 bad anchors

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
2026-08-26 19:20:22 +02:00

59 lines
2.3 KiB
Markdown

---
iteration: "4"
status: done
---
# 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).