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 954aacc9a5 docs: story frontmatter + Dataview board views 
- 28 story files gain YAML frontmatter: iteration id, status
  (mirrors folder), chain position (7 files, positions 1-6)
- board-views.md: Dataview queries (not-done, by-status lanes,
  chain order, active); Kanban caveat — view only, frontmatter
  is source of truth, folder move + status key change together
- board points at the views

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-08-21 12:17:50 +02:00

2.3 KiB
Raw Blame History

iteration status
4 done

Iteration 4 — single binary end-to-end

Format: fiberloom 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).