shoney/writeonce
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
writeonce/docs/stories/language-runtime-database/done/04-single-binary-e2e.md
shoney.arickathil 2a4c304378 docs: stories foldered by state — done/ and refine/ 
- done/ (11): 1, 2, 3, 4, 6, 7, 7b, 9, 9b, 15, 16 — landed iterations
  (9/9b remainders live in the post-12 drain list, not in the files)
- refine/ (8): 9c, 9d, 9e, 9f, 9g, 11, 13, 14 — everything marked
  "no spec yet / brainstorm before planning"
- root keeps: 00-story (index), 05 (partial, plan 8 open), 8/10/12
  (specs or plans exist), 17 (parked, spec+plan approved), 18 (next)
- every cross-reference re-pathed and VERIFIED resolving: board, specs,
  plans, employee-list README, story table, intra-story links (moved
  files' relative links deepened one level; done/7b's 9e pointer now
  crosses to refine/)
- pre-existing dead link noted, not touched: refine/11-fibers.md points
  at docs/plan/exploration/fibers/00-fibers.md which does not exist
  (predates the move)

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

2.2 KiB
Raw Blame History

Iteration 4 — single binary end-to-end

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

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).