A practical sequence for adopting AI Fabrix — from first pilot to governed Role Assistants at scale.
Why a roadmap matters
AI Fabrix is not a single feature switch. Adoption spans Operational Trust, Enterprise Knowledge, Role Assistants, and Evidence Fabrix. Teams that skip certification or metadata modeling often stall when operators ask for proof or when AI access outruns governance.
This roadmap aligns business, architecture, integration, and operations without prescribing a single vendor or industry template.
Role Assistant candidates
Prioritize assistants that reuse certified integrations and produce measurable evidence early.
| Priority | Role Assistant examples | Typical complexity |
|---|---|---|
| Day 1 / highest ROI | Meeting Assistant, Sales Assistant, Customer Success Assistant, Data Quality Assistant | Low — one CRM or calendar integration, clear tasks |
| Medium | Project Assistant, Finance Assistant, Procurement Assistant | Medium — cross-system links, approvals |
| Advanced | Proposal Assistant, Risk Assistant, Manager Assistant | High — multiple datasources, governance depth |
Start with one assistant in the Day 1 row before expanding scope. Each candidate still requires certification gates in Phases 3–4 below.
See Role Assistants operating model and Role Assistants.
Phase 1 — Align (weeks 1–2)
Outcomes: Shared vocabulary, sponsor, and success criteria.
| Activity | Who | Artifact |
|---|---|---|
| Read four pillar READMEs | Executive + architect | Shared outcome statement |
| Pick one pilot system | Architect + integrator | systemKey candidate with test tenant |
| Define “AI-ready” for pilot | Security + business | Certification gates accepted |
Start: Executive overview, What is AI Fabrix?
Phase 2 — Connect (weeks 2–6)
Outcomes: One external system modeled with business metadata and governed capabilities.
| Activity | Who | Artifact |
|---|---|---|
| Wizard + model datasources | Integrator | Integration manifests under the system key (Create integration) |
| Dimensions and protection | Security + integrator | ABAC scopes documented |
| Validate, E2E, upload | Integrator | Green test ladder |
Start: Create an enterprise external system
Phase 3 — Certify (weeks 4–8)
Outcomes: Three-pillar certification for the pilot integration.
Run in order: verify-operations → verify-trust → verify-governance → lifecycle. Treat certification as readiness proof for a defined scope — not unlimited production guarantee.
Architect review: Architect overview. Operator visibility: Operator overview.
Phase 4 — Role Assistant pilot (weeks 6–12)
Outcomes: One Role Assistant using certified capabilities on in-scope data.
| Activity | Who | Artifact |
|---|---|---|
| Map role → capabilities | Business + architect | Capability allow list |
| Pilot tasks with evidence | Operator + Role Assistant owner | Completed tasks in Evidence Fabrix |
| Promotion criteria | Governance | Skill level / scope rules |
See Role Assistants operating model and Operating model.
Phase 5 — Scale (ongoing)
Outcomes: More systems, relationships, and Role Assistants — same gates.
- Add datasources and cross-system relationships before expanding Role Assistant scope
- Re-certify after vendor API or policy changes
- Use lifecycle commands for drift control
Anti-patterns
| Skip | Risk |
|---|---|
| Business metadata | Prompt-heavy, inconsistent AI answers |
| verify-governance | Over-broad data exposure |
| Evidence capture | No audit trail for Role Assistant actions |
| Local/cloud drift | “Works on my laptop” integrations |