shoney.arickathil
02b4b13a52
The branch was 17 ahead / 25 behind with 11 conflicting files, and drifting further: db.c had been rewritten twice on master since (group commit, then compaction). Resolved rather than rebased so both histories stay legible. Conflicts, and how each was settled: - db.c: BOTH semantics kept. Master's fatal path and compaction check now sit behind the branch's `table_is_durable` predicate, in all three inline arms — a volatile table reaches neither the barrier nor the compaction check - db-bench sample: every mode from both sides (growth, growth-verify, randread, replayseed, wmix) and ONE `boot` mode, which both sides had added independently - db-bench.py: all six legs kept. Both sides had also grown the same WAL-size helper under different names; collapsed into one - perf-targets: the branch's §5 (RAM ceiling) then master's §6/§7 — master's numbering had already assumed a §5 it did not have - story frontmatter: master's `status` (the landing truth) plus the branch's `readiness` axis. 03 would have read `done` + `refine`, which is a contradiction — it was brainstormed and landed on master, so `ready` - board: both standup blocks newest-first; master's chain rows (a superset); the branch's databasev2 1-2 rows with master's 3-4. Fixed a stray `|` in master's row 3 - baseline: master's, then REGENERATED from a full campaign — 143 metrics, 132 checks, 0 failures with both sides' legs present TWO HALF-EXPOSED FEATURES FIXED, because the merge rule is that master gets no feature that is honoured in name only: - `resident: keys` PARSED, set a .wob flag, and did nothing: rows stayed fully resident. A developer could declare a 120 GB table keys-resident, watch it compile, and be OOM-killed. The loader now REFUSES it with a message naming what to write instead, until tasks 5c/5d land. The compiler still parses it and its AST golden still passes, so the grammar work stays tested - `durable: false` was honoured ONLY on the inline path. wo_db_exec_req had no guard at all, so a volatile table written from an actor on a worker shard would still be logged — precisely porch's session-table case, and precisely what iteration 2 exists to provide. All three request-path arms now carry the same predicate. Found by reading the merged code, not by a test: the obvious probe runs main() on the primary and therefore only exercises the inline path Verified on the merged tree: wovm-test 0, woc-test 0, oop-e2e 122/0, residency-accept 8/0, db-bench 132/0, linkcheck clean. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> |
||
|---|---|---|
| .. | ||
| 00-wob-format.md | ||
| 01-error-catalog.md | ||
| 02-corpus.md | ||
| 03-concurrency-coroutines.md | ||
| 04-db-binding.md | ||
| 08-builtin-surface.md | ||
| README.md | ||
docs/plan/oop-vm/ — OOP + systems track contracts
The normative contract documents both stacks cite. Landed by their named plan tasks:
| doc | contract | plan |
|---|---|---|
00-wob-format.md |
.wob bytecode format (compiler↔VM) |
1 |
01-error-catalog.md |
every WO-E### code |
2, grows 3/8 |
02-corpus.md |
how to add conformance fixtures | 3 |
03-concurrency-coroutines.md |
stackless fibers, park/resume protocols, reduction budget, the no-async rule |
arc (was plan 4's slot; that plan ✖ discarded 2026-08-21) |
04-db-binding.md |
row format, WAL records, query subset | 5 |
05-http-service.md |
route section, trap→HTTP table, JSON subset | 6 |
06-ui-live.md |
delta frames, subscribe protocol, wo:live | 7 |
07-systems-stdlib.md |
per-function nil-vs-trap contracts | 9 |
08-builtin-surface.md |
builtin source names, container/call/entry rules the emitter enforces | 3 |
Specs and plans: docs/superpowers/{specs,plans}/. Repo map: docs/08-project-structure.md.