Twin (Personal AI Operator)
Twin is your interface to the entire Operations domain. It assembles ticket context, drafts responses, proposes resolution paths, manages approvals, and hands off to other agents when a task requires deeper specialization.Core Agents (Shared)
- Discovery Agent — Maps entities across source systems and surfaces hidden relationships. In Operations, it links a request to the correct asset, vendor, and policy even when the original submission lacks those fields.
- Triage Agent — Classifies and prioritizes incoming requests against SLA rules and capacity. It routes tickets to the correct queue and flags breaches before they expire.
- Schema Agent — Detects schema drift in ServiceNow, Jira, or HR feeds and alerts when mapped fields break. It maintains the integrity of projections into the domain views.
Domain Agents (Operations-Specific)
- Asset Agent — Manages asset lifecycle actions: assignment, refresh alerts, procurement triggers, and disposal records. It reads from and writes to the Asset Inventory.
- Vendor Agent — Monitors vendor portfolios, checks contract coverage, flags risk score changes, and drafts onboarding or offboarding checklists.
- Policy Agent — Interprets active policies against incoming requests and approvals. It validates whether a proposed action complies with current rules.
- Approval Agent — Routes approvals through delegation chains, enforces escalation timeouts, and records signed decisions with receipts.
- KPI Agent — Computes weekly and monthly aggregates, detects threshold breaches, and suggests corrective actions based on ticket and asset trends.
Domain Agents communicate through Spine Fabric events, not direct API calls. This ensures every agent action is auditable and replayable.