Identity. Policy. Lifecycle. Approval. Versioning. Rollback. Audit. The control plane is the layer that turns agentic AI from an experiment into an enterprise system.
- Agents
- Definition, version, scope, policy assignment, lifecycle state, and deprecation.
- Prompts
- Central repository, versioning, promotion flow, rollback, and approval history.
- Tools
- Registration, scoping, role-based execution permissions, abstraction, and validation.
- Datasets and knowledge sources
- Document classification, document-level access control, refresh status, retention, and retrieval policy.
- Plugins
- Role-based execution and modification controls; isolation between workspaces.
- Models
- Provider routing, model pinning, fallback chains, and cost-aware selection.
- Workspaces
- Departmental and tenant isolation with quotas, cost views, and access controls.
- Identities and roles
- Fine-grained RBAC for agent authors, prompt editors, deployers, approvers, auditors, and viewers.
Every agent, prompt, tool, and dataset moves through formal lifecycle states. Promotion is gated by approvals, policy checks, and Haluvance enforcement checks where configured.
- 1
Draft
Authoring stage. No production traffic. Editable by author and contributors.
- 2
In Review
Submitted for review. Reviewers receive notifications based on role and workspace policy.
- 3
Approved
Reviewer-approved but not yet receiving production traffic. Available for staging.
- 4
Production
Receiving live traffic. Modifications require a new version and a new review cycle.
- 5
Deprecated
Marked for removal but still serving for a defined transition window. Triggers stakeholder notifications.
- 6
Retired
Removed from active service. Definition retained for audit purposes per retention policy.
- Single approver
- One designated approver signs off changes within a workspace or capability area.
- Two-key approval
- Two approvers are required for production prompts, sensitive tools, or model changes.
- Conditional approval
- Approval requirements change based on the scope and risk of the change.
- Quorum approval
- N-of-M review is available for cross-departmental workflows.
