Reference

Consultable, complete, and dry. These pages describe exact behaviour; for learning, start with the tutorials, and for tasks see the how-to guides. For the toolchain itself — the CLIs, the bynk.toml manifest, emission, and the editor tooling — see the Developer Documentation.

Language

• Glossary — terse definitions of Bynk’s load-bearing terms.
• Type system — opaque, sum, record, and refined types.
• Refined-type API — .of, predicates, admission.
• Operators & built-ins — operators, precedence, built-in types.
• Agents — declaration, state, zeroability, lifecycle.
• HTTP — HTTP handlers and HttpResult.
• Static assets — asset declarations: files served beside a Worker.
• Embedded text — embed declarations: a project file’s text as a String.
• Testing — suite/case, expect, property, as <tier>, stub, Val[T].

Project & output

• Diagnostic index — every bynk.* code (generated).
• TypeScript client — the typed client a non-Bynk Worker calls a context through, and bynk.foreign.toml pins.
• Version compatibility & changelog.

The bynk.toml manifest and Emission — the TypeScript each construct compiles to — are documented under Developer Documentation.

Generated reference

These pages are generated directly from the compiler (or the grammar) and guarded by tests so they cannot drift:

• Syntax & grammar — from the tree-sitter-bynk grammar.
• Keywords — from the lexer’s keyword tokens.
• Diagnostic index — from the diagnostic registry.
• Wire format — the cross-context call format non-Bynk code can speak, from the emitter’s own constants and codecs.

The CLI (bynkc) reference is also generated (from the clap command tree); it now lives in Developer Documentation.