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>
75 lines
3.1 KiB
Markdown
75 lines
3.1 KiB
Markdown
---
|
|
iteration: "5"
|
|
status: done
|
|
readiness: ready
|
|
---
|
|
|
|
# Iteration 5 — language surface (Haxe-parity adoptions)
|
|
|
|
> Format: `product/story-iteration-template`. Part of
|
|
> [Story — one language, one runtime, one database, one binary](00-story.md).
|
|
|
|
|
|
> **Status: ✅ COMPLETE 2026-08-20.** The *grammar* half landed 2026-08-14 —
|
|
> modules, `and`/`or`, interpolation, `const`, loop control, switch
|
|
> expressions, typedef records, enum payloads, try/catch, `nil`/`?T`,
|
|
> statics, `pub(read)` syntax, container literals, `for k, v in m`, `as`.
|
|
> The *strictness* half landed in three waves: `?T` forced handling
|
|
> (WO-E211/212/213 + narrowing) and reject rows (WO-E105) on 2026-08-18;
|
|
> the final three on 2026-08-20 (branch `language-surface-strictness`,
|
|
> developer directive overriding the post-12 park) — **`pub(read)` write
|
|
> enforcement** (WO-E219, class-owned writes, corpus-pinned),
|
|
> **`using` static extensions** (compile-time rewrite to a free-fn call,
|
|
> WO-E220 on method collision, zero owner/emit awareness), and **`#if`
|
|
> build flags** (`woc -D name`, token-level filter, WO-E003 misuse).
|
|
> `is`/`throw` stay cut (0 workload uses); `abstract` is a reject row.
|
|
> Plan 8 is closed.
|
|
|
|
## Goals
|
|
|
|
- The language grows from milestone grammar to a daily-driver surface: the
|
|
systems-track verdict table's every **adopt** row — switch expressions,
|
|
typedef records with `?fields`, `?T` optionals with null-narrowing,
|
|
enum payload variants, try/catch/throw over traps, `static` members,
|
|
`abstract` newtypes, `using` extensions, `use` modules, `is`, `pub` /
|
|
`pub(read)`, `#if` build flags, string interpolation, loop control.
|
|
- Every **reject** row (inheritance, `Dynamic`, `cast`, macros, FFI…)
|
|
refuses with a diagnostic citing doctrine — the language's boundaries are
|
|
as deliberate as its features.
|
|
|
|
## Acceptance Criteria
|
|
|
|
- What to achieve?
|
|
- **Given** the verdict table in the systems-track spec,
|
|
- **when** the corpus runs,
|
|
- **then** every adopt row has at least one golden fixture and one
|
|
must-fail fixture passing, and every reject row that would parse
|
|
produces its doctrine-citing diagnostic.
|
|
- What to achieve?
|
|
- **Given** a switch over a union missing one variant and lacking
|
|
`default`,
|
|
- **when** it compiles,
|
|
- **then** the diagnostic names exactly the missing variants.
|
|
- What to achieve?
|
|
- **Given** the three fenced VM changes (catch frames, variant objects,
|
|
boxed scalar optionals),
|
|
- **when** they land,
|
|
- **then** the format doc is updated in the same change and all prior
|
|
trap fixtures still pass byte-for-byte.
|
|
|
|
## Out Of Scope
|
|
|
|
- Stdlib modules and program mode (iteration 6).
|
|
- Any new VM capability beyond the three fenced changes.
|
|
|
|
## Info
|
|
|
|
- Normative table: `docs/superpowers/specs/2026-08-01-systems-track-design.md` Part 1.
|
|
- Order inside the plan matters: modules first (everything imports through
|
|
them), data shapes before optionals, rejects last.
|
|
|
|
## Proposed Solution
|
|
|
|
- Execute the existing plan: `compiler/plan/2026-08-01-haxe-parity-language.md`
|
|
(nine tasks, each shipping its fixtures and error-catalog entries in the
|
|
same task).
|