KylloToolchain
Kyllo is a standalone language. Its first execution target is Python — but Python is a target, not the authority. The language's rules are enforced before code generation, in Kyllo's own terms.
Python is the target, not the authority
- Python syntax must not define Kyllo's syntax.
- Python behaviour must not define Kyllo's semantics.
- All language rules must be enforced before code generation.
That distinction matters most for the unresolved parts of the language. Decimal semantics, for example, are undecided in Kyllo (OQ-002) — so they cannot be settled by whatever Python's decimal module happens to do. The specification decides; the target implements.
Status: no compiler yet
There is no working compiler, release, download, install command, package, executable, or benchmark. Nothing on this page is a capability you can use today. The installation page in the documentation exists so the gap is visible — and it invents no installation steps.
MVP prototype scope
The documentation defines a minimum viable prototype — a prototype objective, not a built system. Its components are:
- Lexer
- Parser
- Abstract syntax tree (AST)
- Type checker
- Semantic analyser
- Contract checker
- Structured diagnostics
- Python code generation
First demo objective
The first demo the prototype must be able to do is small and specific: the Bank Account example compiles and executes. And the negative half matters just as much — deliberately incorrect implementations must be rejected, with useful diagnostics. A compiler that accepts everything is not a compiler; it is a printer.
See the Language page for the Bank Account example, and the Verification page for what a rejection must look like.
Deferred
Native code generation, advanced formal verification, and a package registry are deferred — they are not part of the MVP scope. They are not promised for any date.
Compiler architecture, as specified, is documented at kyllo-docs.pages.dev/compiler/architecture/.