Current registry snapshot
| Classification | Count |
|---|---|
| All specifications | 180 |
| Stable and implemented | 175 |
| Accepted design | 2 |
| Draft design | 2 |
| Implementation in progress | 3 |
| Pending implementation | 1 |
| Superseded | 1 |
The stable baseline contains 175 specifications and 175 conformance features. Planning and Draft records are visible, but they contribute no implementation, verification, stabilization, or acceptance credit.
Two independent states
A specification separates design maturity from implementation delivery. This prevents an approved idea from being presented as working software and prevents working experiments from silently becoming compatibility promises.
| Field | Meaning |
|---|---|
Draft | The design is under investigation and may change freely. |
Accepted | The direction is approved but is not yet compatibility-frozen. |
Stable | The behavior belongs to the maintained compatibility contract. |
Pending | No implementation credit is claimed. |
In progress | Some planned acceptance units remain open. |
Implemented | The required behavior and named evidence are present. |
Read by intent
Language and compiler
Start with the language boundary, implemented forms, lexical analysis, explicit IR, direct ESM emission, and Source Maps.
Persistent values
Follow the host-symbiosis design into Vector tries, Lists, HAMT Maps and Sets, Transients, Queues, Records, sorted collections, and the million-value exit audit.
Self-hosting and Emacs
Read the bootstrap foundation, self-hosted compiler, worker protocol, accelerated operation service, and measured Emacs reinvestment.
Maturity and acceptance
The roadmap defines denominators; the compatibility corpus, documentation contract, retained runs, and final manifest provide the evidence.
Executable evidence
The registry is checked against conformance ownership, source locators, the public surface, generated API metadata, compatibility classifications, diagnostics, compiler parity, documentation, and repository integrity. Generated artifacts carry source identities so stale reports cannot silently certify changed code.
bun run check:contracts
bun run progress
make test-core
make byte-compileA retained passing report proves its recorded source identity. Editing a specification, test, document, or bound implementation requires regenerating the affected evidence before the new revision can claim the same matrix result.
Future work stays explicit
Specification 0180 records general automatic tail-call optimization as Draft and Pending. Existing explicit recur and standard-library trampoline behavior remains stable; the proposal receives no current progress credit.
Application projects such as browser UI, publishing, and blog generators are kept outside the core denominator. They can prove usability through public ESM boundaries without changing what the language must be.