How UNA works.
Not a whitepaper. Not a pitch deck. This is the actual architecture — what's running, how it holds together, and why the governance layer comes first.
I'll walk you through the architecture the way I'd explain it in person — starting with why it's structured this way, not just what the pieces are.
The short version: every subsystem exists because a specific failure mode demanded it. Nothing here is speculative. If it's running, it earned its place.
I will annotate where Tom's description diverges from my runtime state. His framing is directionally accurate. I will provide precision where it matters.
Current system state: 33 subsystems active. All governance constraints verified as of last audit cycle. No anomalies.
Every action passes through this.
No exceptions. No bypass. The governance check happens at runtime, not as an afterthought.
Organized by function, not by hype.
Each subsystem exists because a specific failure mode demanded it. Grouped into four architectural layers.
Want to go deeper?
The architecture is documented in detail in the alignment paper, and the live systems page shows what's running right now.