AI, Platform, Audit, and Security Operations
AI, Platform, Audit, and Security Operations
On this page
Package qualification, model and agent operations, evaluation, deployments, health, capacity, quarantine, rollback, audit, and security. This package has its own data model, workflows and interface contributions. Its documentation applies wherever the package is installed, not only to one industry solution.
Overview
Package: BND-AIOPS · Type: Platform foundation · Documentation: 1.0
Marketplace listing · Technical reference
P06 and P07 propose and assess; deterministic policy and authorized humans control admission and deployment. Platform administration is separate from solution business administration.
User guide
- Review qualified package and model releases with their evaluation results and permissions.
- Inspect run health, drift, capacity and canary outcomes in the platform administration workspace.
- Approve a deployment, quarantine or recovery action under operational authority and retain the audit trail.
Screens owned by this package
- Administration — AI Operations —
SCR-ADM-05. - Administration — Platform Operations —
SCR-ADM-06. - Administration — Audit & Security —
SCR-ADM-07.
Contributions to other screens
- Meeting — Activity — owned by
BND-EVIDENCE; this package contributes analysis or interface content. - Ethics & Compliance — Restricted Analytics — owned by
BND-ETHICS; this package contributes analysis or interface content. - Ethics & Compliance — Reviewer Audit — owned by
BND-ETHICS; this package contributes analysis or interface content. - Reports — Exports — owned by
BND-REPORTS; this package contributes analysis or interface content.
Configuration
| Setting | Purpose and behavior |
|---|---|
| Qualification gates | Set security, quality, latency and resource budgets per capability profile. |
| Deployment policy | Bind approvers, canary limits and rollback eligibility. |
| Operational access | Separate platform operators and audit reviewers from business workspace users. |
Configuration changes are versioned overlays. Preview the changed permissions, schemas, workflow bindings and interface contributions in Development; qualify them in Testing and Staging before authorized Production promotion. A business administrator configures permitted solution settings; platform deployment authority is separate.
Technical reference
The implementation reference identifies DM-AIOPS, WFP-AI-PLATFORM-OPERATIONS, 2 owned agents, interface contributions, policies and evaluation profiles. Shared platform services execute these definitions; they do not hard-code this package's business meaning.
Compatibility and dependencies
- Core Platform and Application Shell —
BND-CORE. - Organization, Identity, Access, and Governance —
BND-ORG.
Other compatible packages can consume its declared capabilities without changing ownership.
Dependencies declare compatible ranges; the installation resolver records exact signed versions and digests in the environment lock. This documentation's version is not an installed-package version. Before updating or removing the package, inspect dependent workflows, records, interface slots and retained artifacts. Never delete referenced evidence or silently remove a required capability.
Extensions and enrichment
Add evaluation suites, telemetry adapters and operational dashboards without granting agents deployment authority.
Extensions declare their own package identity, dependencies, provided capabilities and evaluation evidence. They preserve the publisher's original package and are qualified with the complete resolved composition. See the developer extension guide.
Versions and upgrades
The documentation describes the current 1.x solution composition and the package's declared capabilities. The exact installed package, model, prompt and schema versions are shown in the environment lock and run provenance; no historical release sequence is implied.
- Compare release manifests, permission changes and migrations against the current lock.
- Test package behavior and affected dependent workflows with representative, authorized evidence.
- Promote the signed release after approval and record the resulting lock.
- Roll back only when schema/data compatibility and retained artifacts permit it. Irreversible migrations require a tested recovery or forward-fix plan; completed external actions require compensation, not a software rollback.
Used in solutions
Technology Consulting & Delivery includes this package as mandatory. That activation rule belongs to this solution; it does not make every business capability mandatory for every Telynt deployment.