An adoption map for architects and leaders — from enterprise reality to governed AI-assisted work through Role Assistants, with proof organized by business resources and capabilities in Evidence Fabrix (not chat threads).
Business value vs enabling pillars
| Band | Pillars | Adoption question |
|---|---|---|
| Business value | Role Assistants, Evidence Fabrix | What outcomes and proof do we need? |
| Enabling | Enterprise Knowledge, Operational Trust | What data and controls make those outcomes safe? |
Build and certify Connected Systems and Business Entities first. Role Assistants consume governed capabilities only after Operational Trust certifies scope.
Recommended reading order
What is AI Fabrix?
↓
Operational Trust (enabling)
↓
Enterprise Knowledge (enabling)
↓
Build Connected Systems + Business Entities
↓
Role Assistants (business value)
↓
Evidence Fabrix — resource-based proof (business value)
↓
Architecture & certification
↓
Plan rollout
Phase guide
| Phase | Focus | Documentation |
|---|---|---|
| Discover | Product story and pillar bands | Understanding AI Fabrix |
| Design | Trust boundaries, roles, data scope | Operational Trust, Architecture |
| Integrate | Connected Systems → Business Entities → capabilities | Build AI-ready systems |
| Assure | Validate, upload, certify (three pillars) | Certification |
| Operate | Role Assistants, Content Review, evidence | Role Assistants, Evidence Fabrix, Operating model (cadence) |
Evidence Fabrix — resource-based operating model
Evidence Fabrix answers audit and improvement questions in business terms:
| Question | Evidence anchor |
|---|---|
| What resource was involved? | Business Entity + resourceType (deal, document, customer) |
| Which governed action ran? | Capability key (deal:read, document:search) |
| Who was accountable? | Role Assistant + active business role |
| What was the outcome? | Task completion signal — not conversation volume |
| What should we improve? | Capability evidence, role evidence, knowledge findings |
What this shows: How a Business Entity, governed capability, Role Assistant task, and Evidence Fabrix proof connect — the resource-based operating loop.
What this is not: CLI certification commands or manifest field reference — see Build and Evidence Fabrix configure pages.
The last stage is Evidence — what Evidence Fabrix preserves for this task, not a second name for the Evidence Fabrix pillar. See Platform architecture for how the operating-model flow's stage names relate to the four pillars.
Conversation history may help debugging; it is not the operational record. See Evidence vs conversation history.
Principles for rollout
- Start with high-value roles and recurring tasks tied to certified resource types — not generic chat.
- Require certification (operations, trust, governance) before broad Role Assistant adoption on a scope.
- Treat governed capabilities as the only execution surface for AI — never raw vendor APIs.
- Measure success with outcomes and resource-linked evidence, not message counts.
- Keep humans in authority — Content Review, approval gates, and policy remain even as skill levels rise.
- Expand scope only when Evidence Fabrix shows repeatable success on the current capability set.
Decision gates and roles
Expanding a Role Assistant to new capabilities or Business Entities goes through the same certification, governance, and operator-readiness gates as any other scope change, owned by the same six steady-state roles (executive sponsor, enterprise architect, integrator, security/governance, business operator, platform operator). See Operating model for the definitive decision-gates list, the core-roles table, and organizational cadence — this page focuses on the Role Assistant/Evidence-Fabrix concepts those gates and roles apply to.
Limits
Skill levels, promotion rules, and impact dashboards depend on your AI Fabrix release and tenant configuration. This page describes the adoption model — not your tenant's certification profile or live Role Assistant catalog.