Architecture Decision Records

Key design decisions behind ArchLang, with their context and trade-offs.

• 1. Hand-written recursive-descent parser, not Lezer/tree-sitter
• 2. Optional, lazy-loaded dependencies for heavy geometry and raster
• 3. Expand-time scripting — no runtime, no I/O, no clock
• 4. Relational placement is deterministic arithmetic, not an optimizer
• 5. Design intelligence is facts + advisory lint, not an invisible architect