This document tracks the design governance, decision records, and architectural principles of the Llux project.
| # | Directive | Core Idea |
|---|---|---|
| 1 | Golden Path, Not Cage | Escape hatches always exist. |
| 2 | Embed Governance | Automate security & compliance. |
| 3 | Design for Flow | 5-minute first successful call. |
| 4 | Prioritize Evolvability | Additive-only changes. |
| 5 | Make Failure Legible | “Scalpel” errors with suggested fixes. |
| 6 | Offline-First | <40MB download, 2G-compatible. |
| 7 | Democratise Access | Free, open, and broadly reachable. |
| 8 | Break the Language Barrier | Top-10 languages. |
| 9 | Fair Outsourcing | Transparent credit model. |
| 10 | Remote-Friendly Collaboration | Participation should not depend on travel. |
| 11 | The Open Invitation | Extensible at every stage. |
| 12 | Decentralized Registry | Git-based extension sharing. |
| Principle | Question | Implication |
|---|---|---|
| Amplify, Don’t Replace | Does this augment human capability or replace judgment? | AI is a suggestion engine, not a decision-maker. |
| Reduce Friction | Does this lower mental or physical effort? | Progressive disclosure; kind errors. |
| Respect Diversity | Does this work across skills, languages, contexts? | Multiple abstraction layers; multilingual source and diagnostics. |
| Enable Collaboration | Does this help different roles work together? | Shared formats (.llux, .intent). |
| Sovereignty | Does this give users control over their work? | Offline-first; open formats; no vendor lock-in. |
| Value-Additive | Is this feature essential or just “nice to have”? | Resist feature creep; core focus. |
Significant architectural decisions should be recorded here so contributors can understand why the project works the way it does.
(Placeholder for future DDRs)
../philosophy.why/index.md../philosophy.why/index.md