Internals

Implementation documentation for contributors who are changing the code. User-facing behavior is documented in the guide and the reference.

• Architecture — the pipeline, the tiers, the test contracts
• Testing — the test contracts each kind of change must satisfy
• Performance — profiling, and what a large model costs
• Interface records — what a closed document keeps in memory, and why
• An execution-owned IR — a proposal: lowered graphs that own their identity and carry no syntax-tree pointers, with the inventory, the migration and the open decisions
• Design notes — how each subsystem was built, and which normative reference it follows
• Plans — the staged work behind each subsystem, kept for the reasoning it records