The Architecture Boundary - What You Never See
The Operating Principle
Governance is the architecture. Creation is the experience.
Every decision in fai follows one test: Does the user see architecture or experience?
- If you see architecture → we fix it (make it invisible)
- If you experience creation → we ship it
What's Invisible
When you run fai, here's what you DON'T see:
- How your context is stored and loaded
- How your AI is connected and managed
- How your patterns are detected and proposed
- How decisions flow between sessions
- How multiple AIs coordinate behind the scenes
- How governance ensures quality without your involvement
You see none of this. You see: "Your workbench is ready. Let's build something."
The 90/10 Split
For every action you take, your workbench handles roughly 9 actions invisibly.
You type: fai Behind the scenes: Context loads, AI connects, session
initializes, patterns activate, governance applies, history restores,
preferences load, environment configures, and your workbench is ready.
You see one action. Nine happened invisibly.
This isn't laziness - it's design. The best tools disappear. When you use a well-designed tool, your focus is on YOUR work, not the tool.
Why This Matters
Good design is invisible. You don't think about how your chair works - you sit and work. You don't think about how electricity reaches your desk - you plug in and create.
fai works the same way. You don't think about context storage, AI routing, pattern detection, or governance. You build. Everything else is handled.
For the Curious
If you want to understand what's under the hood, that's fine. fai is open source. But you'll never NEED to understand it. The architecture serves you - you don't serve the architecture.
Creation is the experience. Always.
- Resilience → - How your AI is always there