07 — AI Twin
The layer that governs the rest.
The control plane for every model and agent in the estate — routing, cost, evaluation, guardrails and audit — so intelligence stays accountable to value.
North Star
Value per model in production
The stream
Automation → Capability → Value driver → Financial value
Automation
Cost-aware model routing
Capability
Right model for the task, priced
Value driver
AI unit economics
Financial value
Lower inference cost per outcome
Automation
Continuous evaluation and drift detection
Capability
Quality proven, not assumed
Value driver
Reliability
Financial value
Fewer failures reaching customers
Automation
Policy and guardrail enforcement
Capability
Safe by default at runtime
Value driver
Regulatory readiness
Financial value
Avoided fines and rework
Value system
Value ≠ North Star ≠ KPI ≠ driver ≠ process metric.
The translation layer that connects a corporate objective to something an operating team can actually move on Monday.
Value
Reliable machine capability
Economic outcome
Value delivered per dollar of AI spend
North Star
Value realized per model dollar
Outcome KPIs
Driver metrics
Process metrics
Causal model
Value leakage
Where the value goes missing today.
Leakage is multiplicative. Every gate that stays leaky discounts everything built upstream of it.
Pilots
Demos that never reach production.
Sunk investment
Routing
Frontier models used for trivial tasks.
Run cost
Grounding
Stale retrieval erodes trust and adoption.
Abandoned tools
Attribution
No baseline, so value is never proven.
Budget withdrawn
Digital twin
Simulate the interventions before anyone funds them.
Instead of implementing ten recommendations and learning the result in six months, the twin stacks them first.
Value realized per model dollar
Guardrails
- No high-risk deployment without registry entry
- Human intervention right preserved
- Zero-retention inference only
Constraints
- EU AI Act timelines
- Data residency
- Vendor and model availability
Automation
What runs without asking.
Model gateway routing
SLM for volume, LLM for reasoning, cached where safe.
Orchestrator Agent
Eval harness
Golden sets, regression runs and drift alerts per agent.
Evaluation Agent
Runtime guardrails
PII, injection, toxicity and policy enforcement inline.
Guardrail Agent
Orchestrator Agent
Plans and routes work across agents and models.
LLM planning + routing policy
Evaluation Agent
Scores output quality against real outcomes.
Eval harness + outcome feedback
Guardrail Agent
Blocks and logs unsafe or non-compliant actions.
Classifier ensemble + policy engine
Integrations
Where it plugs into the domain.
Vendor-agnostic by design. The twin reads and writes through whatever stack the domain already runs on.
Runtime
- Model gateway (hosted + private)
- Vector + graph store
- MCP + enterprise connectors
Governance
- Observability & audit log
- Policy engine
- AI system inventory
Platform
- IAM & secrets management
- Warehouse / lakehouse
- CI/CD for prompts and agents
Domain platforms we connect
Model providers
Cloud AI platforms
Retrieval & vectors
Agent & orchestration
Eval, observability & cost
Governance & security
Plus anything else with an API — connectors are added per engagement, not sold as a platform lock-in.
Value
The levers, and what they move.
Cost
Route to the cheapest model that passes eval.
Cost per successful task
Trust
Every action explainable and reversible.
Audit coverage · Incident rate
Speed
Reusable pattern per new agent.
Days to production per agent
Risk
What could go wrong, and what stops it.
Every risk in this domain has a named containment in the runtime — not a slide.
Prompt injection and tool abuse
Content isolation, allow-listed tools, signed action policies
High
Unclassified high-risk AI use under the EU AI Act
Risk tiering at intake; registry entry before any deployment
High
Runaway inference cost
Model routing with SLM-first policy and per-use-case budgets
Medium
Model drift after vendor update
Continuous eval suites gate every model version
Medium
Compliance · Security
Built into the runtime, not bolted on.
EU AI Act
Compliance control plane — enforces classification, transparency and oversight for all deployed systems.
- Technical documentation and conformity evidence per AI system
- Transparency notices for user-facing generative output
- Post-market monitoring, incident logging and model change records
- GPAI provider obligations tracked for every third-party model used
GDPR
- No customer data used for third-party model training
- Data residency and regional inference routing
- Right to human intervention on any consequential output
- Erasure propagated to embeddings, caches and logs
Security
- Prompt-injection and tool-abuse defenses
- Secrets never exposed to model context
- Zero-retention inference agreements
Controls & oversight
- Risk tiering per agent
- Kill switch and rollback per deployment
- Independent red-teaming before release
Agentic execution
Agents earn authority. They are not given it.
No agent in this twin controls anything it has not first proven in replay, evaluation, simulation and shadow.
01
Historical replay
Re-run the last 12 months. Would the agent have been right?
02
Offline evaluation
Scored against held-out outcomes, not opinion.
03
Digital twin
Simulated against the causal model under stress.
04
Shadow mode
Runs live, decides nothing. Divergence is logged.
05
Human recommendation
Proposes; a person executes and rates it.
06
Bounded pilot
One segment, capped exposure, hard rollback.
07
Human-supervised execution
Acts inside thresholds, humans approve exceptions.
08
Progressive autonomy
Authority widens only where evidence widened.
The unit of value
Don't buy transformation. Buy measurable movement.
This twin is contracted the way it is engineered: a baseline, a target, a guardrail, and an attribution method agreed in advance.
Baseline
1.4× value per model dollar, 4 use cases live
Target
3.5×+ with a governed production portfolio
Guardrail
Zero reportable AI incidents
Proof / attribution
Per-use-case baselines with pre-registered success criteria
Next twin
Marketing Twin →