v0.14.0 Implementation Qualification

Status: complete (2026-08-22). This record qualifies the specification-first compiler implementation against the completion definition in the v0.14.0 milestone. It does not prepare, package, tag, push, or publish a release.

Contract Trace

The specification table of contents is the complete public-contract inventory. The implementation and its conformance boundaries trace to it as follows:

Public contract	Normative authority	Executable evidence
Source text and grammar	`spec/13-lexical-grammar.md`, `spec/25-syntactic-grammar.md`	G001-G033 accepted, rejected, semantic-boundary, lossless-projection, depth-limit, and non-recursive parser tests
Modules, declarations, types, generics, construction, and dispatch	`spec/01-modules-use.md`, `spec/02-values-types.md`, `spec/08-generics-interfaces-embedding-methods.md`, `spec/17-literal-definitions-sequence-spread.md` through `spec/19-construction-surfaces.md`, and `spec/22-borrow-coercions.md` through `spec/24-ordering-operators.md`	declaration-lowering, requirement-normalization, conformance, construction-surface, type-validity, and checked-body suites
Control flow, outcomes, ownership, provenance, regions, and destruction	`spec/03-control-flow.md` through `spec/06-memory-region-allocator.md`	checked ownership/loan/cleanup/region/outcome suites and MIR lowering/validation suites
Strings, arrays, views, pointers, standard roles, and public library APIs	`spec/07-strings-arrays-views-pointers.md`, `spec/11-stdlib-primitives-os.md`, `spec/18-callables-default-methods.md`, `spec/21-practical-standard-library.md`	`bundled_standard_library_crosses_the_complete_target_session`, standard-role contract tests, native primitive conformance, and public example execution
ABI, targets, process behavior, and native tests	`spec/09-abi-layout.md`, `spec/10-targets-distribution.md`, `spec/11-stdlib-primitives-os.md`, `spec/20-native-testing.md`	MIR, machine, ARM64, Mach-O, and complete native conformance suites
Diagnostics, formatting, CLI, packages, and editor behavior	`spec/12-diagnostics.md`, `spec/14-tooling-editor-integration.md`, `spec/15-command-line-interface.md`, `spec/16-source-style-formatting.md`	source-tooling, package, command, CLI, analysis, LSP, and language-server protocol suites

Sections explicitly labeled Future Direction, Non-goal, or reserved, not implemented are not current behavior. The specification and active compiler/standard source contain no unresolved TODO, FIXME, HACK, XXX, todo!, or unimplemented! marker. Reserved non-Darwin targets produce the specified unsupported-target failure instead of entering a partial backend.

Completion Evidence

The milestone criteria are closed by these boundaries:

The grammar fixtures and semantic suites above cover every current normative domain. No archived implementation, released binary, historical output, or compatibility adapter participates.
bundled_standard_library_crosses_the_complete_target_session checks every authored standard body and the complete primitive registry. every_public_single_file_example_runs_to_success and public_package_example_runs_with_process_arguments launch every public example through the production command, native session, and generated Mach-O boundary with exact process contracts.
TargetProgram is the single accepted-program boundary. Command tests prove that check stops there without an artifact, while build and run continue from that same value through executable selection. Library, named-target, package, and single-file cases cover the selection matrix.
CLI tests exercise the public process adapter and JSON diagnostic envelopes. LSP and language-server tests exercise JSON-RPC framing, lifecycle, document generations, diagnostics, hover, tokens, navigation, rename, signature help, completion, inlay hints, and code actions at protocol boundaries.
Native conformance executes the ABI, process state, allocation contexts, regions, syscalls, I/O, packs, indirect values, views, destruction, and checked indexing on ARM64 macOS. The Mach-O suite verifies deterministic self-contained images without an external assembler, linker, or signer.
Discovery, topology, declaration reservation, diagnostics, name resolution, type validity, conformance, method selection, and source projection each reverse their relevant input order in focused tests. all_root_executables_share_one_target_compilation_and_keep_declaration_order additionally reverses package and root-module requests and compares the final executable identities and Mach-O bytes.
The workspace contains only the specification-first crates listed in development/compiler/Cargo.toml. Semantic programs and source projections are separate values; each lowering crate exposes an immutable output boundary and cannot access a superseded stage's private representation. The archive directory contains design records only and is outside the compiler workspace.

Verification Runs

The implementation passed the following matrix on ARM64 macOS:

incremental cargo test --workspace --quiet: 1,129 passed, zero failed, one network test ignored;
clean cargo test --workspace --quiet with a new external CARGO_TARGET_DIR: the same 1,129 passed, zero failed, and one ignored;
explicit public-HTTPS clones_resolves_and_materializes_without_external_git: passed;
cargo clippy --workspace --all-targets -- -D warnings: passed;
cargo fmt --all --check: passed;
node docs/build-docs.js: generated 123 pages reproducibly;
git diff --check: passed.

The clean-build directory was created outside the repository and removed after the run, so the qualification did not retain another build tree.

Boundary

The v0.14.0 implementation milestone is complete. Release identity changes, release notes, distribution packaging, artifact qualification, tagging, pushing, and publication are a separate release-preparation operation and require explicit user authorization.