The guide

Twelve pages, in reading order. Each one walks the same eight steps — what the problem is, an analogy for it, the mechanics, why it was built this way, what it costs, when you reach for it, and examples you can run — because a decision is only worth reading if you can see what it cost.

What the language refuses is usually the interesting part.

Writing pages? BMX — the markup format Burxt renders — has its own guide at bmx.burxt-lang.org: how to write a document, how to turn it into a page, and how a view gets checked before the page exists.

• 1 Getting started Install, run a file, the editor
• 2 Numbers and money Scales, rounding contracts, why + is strict
• 3 Types Classes, private, constructors, interfaces, enums
• 4 Memory Regions, escapes, and why you never write allocates
• 5 Contracts requires, ensures, pure, decreases
• 6 Effects touches files, network — what a function can reach
• 7 The C boundary external function, as scaled, the pointer wall
• 8 Modules use, one file per module, what is visible
• 9 Generics Type parameters, bounds, why nothing is erased
• 10 Absence and failure Option, Result, ?, and no null
• 11 Maps and strings Insertion order, Equatable keys, bytes
• 12 Tools and agents mcp-schema, review — the contract is the schema
• 13 Practices where a contract belongs and where it does not, and the traps already paid for

Looking for one thing rather than reading? The reference has every keyword, builtin, command and standard-library function, with a search box — and it is generated by reading the compiler, so it cannot fall behind the language.

Running code beats prose: the examples page shows programs beside exactly what the compiler does with them, and every one of those results was recorded by running it.