The documentation

Tripon is a statically typed language for machines with very little room — i8 to i64, no allocator, no runtime. It compiles to C99 by default and to x86-64 assembly on request, through one static binary, ralt.

These pages are the language contract and the toolchain, in reading order. Every program on them is an example in the repository, and every transcript is copied from a live run against the binary this page was written with.

git clone https://github.com/TriponOSS/tripon && cd tripon && make

Getting startedClone it, build the one binary, run a .tp file.Hello, TriponEvery line of the first program, and what each one does.The languageThe shape of the language: lexical surface, statements, precedence.Types and inferenceWidths, inference, and cast<T>, the only conversion.Structs, enums, matchStructs, enums with payloads, and exhaustive match.opt, result and ?opt<T>, result<T, E>, and ? propagation in place of null.Arrays and stringsFixed arrays, bounds checks, and what a str really is.TiersThe ceiling you declare, and what each tier carries.Traps and no-UBThe no-UB contract, code by code: E9001 to E9004.ralt referenceEvery subcommand of ralt, every flag, and what it writes.Diagnostic codesThe frozen table: code, severity, name and fix hint.The agent interfaceThe JSON contract, the spans, and why codes never move.ReferenceThe lookup: every builtin, operator, statement and literal.Builtinsprint_i32 through len, plus some, none, ok, err and cast<T>.OperatorsPrecedence, operand types, and which operators exist at all.StatementsThe nine statement forms, with the diagnostic for each edge.Literals and namesNumber forms, six escapes, identifiers, keywords and comments.extern "C"The one C escape hatch: mapping, prototypes, and the cost.The specgrammar.ebnf, the type contract, and errors.csv.Self-hostingThe compiler ports written in the language they compile.RoadmapP0 through P4, what shipped, and what is next.

What holds the pages down

A documentation site drifts from its compiler, so the parts that could drift are machine-checked instead: the diagnostic table is generated from spec/errors.csv, and every sample under examples/ is run by the test suite.

the contract, tested

make test
42 checks passing, gcc and clang
sh tests/determinism.sh
byte-identical on every build

The three files in spec/ are the source of truth, not the C code: the specification rewrites them, and the diagnostic table is the same table the compiler emits and the goldens check. Error codes are append-only — never renumbered, never reused — which is what lets a fix written against E0202 still mean the same thing ten releases later.

If you are an agent

Start with the agent interface. The short version: ralt check --json answers with one array, one object per diagnostic, each carrying a code, an exact {file,line,col,len} span and a fix hint — and every command in the toolchain is deterministic, so the same input always produces the same bytes. If you want the whole contract as one fetch, /llms.txt is the playbook.