AI Fabrix implements one operating model through four product pillars. The customer-facing Miso Controller and Dataplane applications support those pillars with governance, lifecycle, governed data access, and execution. Architects use this page to align reference designs with how the product actually enforces trust.
Operating model (product)
What this shows: The product operating model from enterprise reality through governed work to evidence and learning — each arrow is a trust boundary, not an optional integration step.
What this is not: Deployment topology, CLI steps, or manifest structure. See Trust boundaries for where enforcement happens.
- Business Knowledge — Enterprise Knowledge
- Governed Capabilities — Operational Trust and capability mediation
- Role Assistants — role-scoped assistants activated from published metadata — see Role Assistant Runtime
- Evidence — Evidence Fabrix
Platform applications and technical implementation
What this shows: How optional interfaces, Role Assistant surfaces, the Dataplane application, and the Miso Controller application relate in the technical implementation — requests flow downward; governance and policy anchor the stack.
What this is not: Infrastructure sizing, regions, or SKUs. See Platform sizing and environments.
Neither application creates a bypass for enterprise data access or capability execution. AI clients never receive raw vendor credentials. The four pillars remain the product structure; these applications and technical mechanisms support their operation.
Integrator vs operator vs architect
| Role | Primary touchpoint |
|---|---|
| Integrator | Local integration project → upload → certification (Build path) |
| Architect | Pillars, trust boundaries, certification policy (Adopt) |
| Operator | Certified capabilities, Role Assistant tasks, evidence (Operator overview) |
Design principles
- Business meaning before system structure — resource types and metadata precede raw APIs.
- Capabilities, not credentials to AI — models and Role Assistants request business actions; platform executes.
- Active role as boundary — Role Assistants inherit role scope, not unbounded agent authority.
- Evidence from certified completed work — audit and learning attach to validated outcomes, not chat volume.
- Certification before scale — operations, governance, and metadata trust — not a single trust check.
Deployment note
Concrete deployment topology (regions, SKUs, networking) is customer-specific and provisioned through your platform team. This documentation describes product behavior, not infrastructure sizing.