Back to Build AI-ready systems overview.
Expose governed capabilities, upload to the dataplane, and run Enterprise AI Certification — the proof that Role Assistants may rely on this Connected System.
Who this is for
| Role | Use this band when… |
|---|---|
| Integration developer | Uploading config and running verify-* pillars |
| Architect | Reviewing capability design and certification outcomes |
| Operator | Confirming online state before widening Role Assistant scope |
Publication makes capabilities available to Enterprise MCP and Role Assistants. Certification proves Connected System readiness (verify-operations wraps that ladder) — it is not Role Assistant YAML prove. Prove the assistant separately: Role Assistant tests.
In this phase
| Page | Outcome |
|---|---|
| Governed capabilities | exposed + RBAC-aligned capability keys |
| CIP execution | Transforms and sync steps in the execution layer |
| OpenAPI and MCP contracts | Contract surfaces for AI clients |
| Deployment and upload | Probe upload, publish, deploy |
| Certification | verify-operations, verify-trust, verify-governance |
| Configure Enterprise MCP | Runtime MCP after publish (reference) |
Certification pillars (quick reference)
| Pillar | Command |
|---|---|
| Operations | aifabrix verify-operations <systemKey> |
| Agent metadata trust | aifabrix verify-trust <systemKey> |
| Governance | aifabrix verify-governance <systemKey> --subject-email <scoped-user> |
Then read the report: aifabrix lifecycle <systemKey>.
Prerequisites: Validate and test green for your scope; Configure business policies and protection upload complete before governance pillar.
Limits
Enterprise MCP runtime configuration varies by deployment. Upload success does not publish protection grants — follow protection upload before verify-governance. See Protection manifests and upload for the detailed YAML workflow.
Next: Operate.