Documentation

The authoritative Kyllo technical reference is the documentation site at kyllo-docs.pages.dev. This page is a curated set of entry points into it — it does not duplicate the specification, and it does not compete with it. Where this website and the documentation disagree, the documentation wins.

Documentation version v0.2.8. Specification v0.1 Initial Draft: 102 pages from 81 source files, 56 TECHSPEC sections. Note: TECHSPEC-22's file and Section 27 are missing in the source material, and file and section numbers diverge from TECHSPEC-23 onward.

Every link below was checked and returned HTTP 200 when this site was built. The changelog has no page on the documentation site, so no changelog link is listed here — the changelog is summarised on the Project page instead.

Start here

• Documentation home — the landing page: what Kyllo is for, why it exists, and where to start.
• Getting started — first steps, including a first program.
• First program — the shortest path to a working Kyllo program (as documented).
• Introduction — the language's purpose and philosophy.
• Philosophy — the principles behind the design.
• Glossary — terms, including the name: kyllopodion, “crook-footed”, the epithet of Hephaestus.

Language reference

• Language Guide — how to write Kyllo, topic by topic.
• Types — the type system as proposed.
• Syntax — statement termination and block structure, including the accepted OQ-001 rules.
• Examples — worked examples from the documentation.

Technical specification

• Technical Specification — the normative specification, 56 TECHSPEC sections, v0.1 Initial Draft.
• TECHSPEC-01 — the first specification section; the rest are linked from the specification index.
• Cross-reference — how the specification sections, guide pages, and decisions link together.

Design decisions

• Decision Records — permanent records of accepted decisions and rule changes.
• OQ-001 — Statement Termination — the only accepted decision: explicit semicolons and typed block endings.
• MVP scope — what the first implementation is meant to cover, and what is deferred.

Compiler architecture

• Compiler — the compiler and its architecture, as specified.
• Compiler architecture — the nine-stage workflow and its components.
• Installation — the documentation's installation page. It exists so the gap is visible: there is no compiler to install yet, and it invents no installation steps.

Verification

• Verification — the verification approach in the documentation: levels, statuses, and evidence.

Unresolved questions

• Unresolved Questions — the register of open design questions, OQ-002–OQ-029. This is where the language is still being decided, and it is essential reading before treating any proposed feature as settled.