Documentation for executives, architects, operators, and security leaders adopting AI Fabrix.
AI Fabrix makes Enterprise Reality usable by AI. Adoption is the path from sponsor decision through certified Connected Systems to Role Assistants in conversation — with Evidence for proof, not chat history as the system of record.
Start here
| Audience | Page |
|---|---|
| Executive | Executive overview |
| Architect | Architect overview |
| Operator | Operator overview |
| Operating model | AI Fabrix operating model · Operating model (cadence) |
| Roadmap | Adoption roadmap |
| First Role Assistant | From integrations to Role Assistant · Operate your first Role Assistant |
| Golden path | GitHub integration golden path |
| Identity first | Zero enterprise onboarding · Installation and onboarding |
Four pillars (read in order)
- Operational Trust — enabling
- Enterprise Knowledge — enabling
- Role Assistants — business value (primary)
- Evidence Fabrix — business value (proof)
What scaling adoption means
Adopt's job is showing an organization how to scale the reuse that the product already makes possible — not re-explaining the underlying concepts. Each new initiative should reuse, not rebuild: the same governed business meaning, the same bounded capabilities, and the same authority checks that stop work safely instead of guessing when something can't be verified. See Platform architecture for what becomes reusable across AI initiatives, and Operational Trust for how safe stop works as a normal, expected outcome — not a failure.
Build path (integrators)
Build AI-ready systems — certify Connected Systems before activation. Role Assistants come from publish and subscriptions, not hand-built assistants in Builder.