Product
The agentic control plane that makes frontier autonomy safe to actually deploy. Provider-neutral, role-bound, and evidence-producing by construction — the layer between your professionals' authority and the models that execute on it.
Seven components · Two layers · One verified execution cycle
Orcher — seven components, two layers
Fig. ORC-02
Layer 1 · Accountability
C0
Directive Interface
Where intent enters, attributed.
C1
Role Identity Fabric
Authority bound to a person.
C2
Logic Scrubber
Pre-commit verification.
C3
Immutable Audit Ledger
Hash-chained evidence.
Layer 2 · Operations
C4
Data Control Gateway
Data boundary and redaction.
C5
Cost Governance
Routing and spend ceilings.
C6
Observability
Cross-provider execution telemetry.
Full architecture
Directive in, four sequential gates, three continuous controls, a verified commit to your systems of record, and evidence that outlives the run.
Orcher — full architecture, intent to evidence
Layer 1 — sequential, gating
Layer 2 — continuous
drag · pinch or scroll to zoom · double-tap to reset
Guided walkthrough
What the seven components enforce
Press Start walkthrough, or select any node, to step through the seven components. Each one closes a different gap that keeps enterprises from scaling agents: C1 scopes the work, C2 binds it to accountable identity, C3 makes policy executable before commit, C4 turns activity into defensible evidence, and C5–C7 hold enterprise data boundaries, cost and cross-provider visibility continuously. Together they are Dipp AI's position — Enterprise Superintelligence that is governable by construction.
Source: Vol. I, p. 19 — Component Schematic v1 — the seven components
Interactive · Vol. I sourced
Select any component to reveal the passage from The Enterprise Superintelligence Report, Vol. I that specifies it, with its page citation and a link into the source.
Select a component to reveal its Vol. I excerpt.
Fig. CP-01 · The seven-component control plane
Orcher · seven components
Four sequential gates decide whether an action may commit. Three continuous controls hold data, cost and visibility while it runs. Each is a separate component with its own contract and its own evidence.
The components are specified end to end in The Enterprise Superintelligence Report, Vol. I.
The strategy behind Orcher
Binding a platform to one heavy frontier model wastes tokens and leaks proprietary data. Dipp AI's strategy — and the reason Orcher's seven components exist — is intelligent routing: decouple orchestration from any single provider, match each task to the cheapest model that can carry it, and keep prompts and data inside the enterprise's own tenant boundary.
DIPP AI / ORCHER
Seven components. One enterprise-owned control plane.
01 + 02 / AUTHORITY
Intent, named professional, permitted actions and systems of record.
06 / COST GOVERNANCE
Select the least costly sufficient model within the task’s stakes, latency target and spend ceiling.
Explore Cost Governance05 / DATA CONTROL GATEWAY
Region, redaction, retention and training-exclusion requirements determine which destinations qualify.
Models discussed in Dipp AI Research · September 6, 2026
Model families · exact versions and licences assessed per deployment
Hyperscalers, neoclouds and enterprise infrastructure
03 / Logic Scrubber
Verify proposed actions before commit.
04 / Immutable Audit Ledger
Preserve the decision and refusal evidence.
07 / Observability
Trace cost, latency and outcomes across routes.
Switch providers in a week, not a quarter.
An orchestration layer sits in front of every AI task rather than inside one vendor's SDK. Directives, roles, policy and evidence live in Orcher, so a provider change is a routing-table change — a week of work rather than a quarter of re-platforming — and no model vendor becomes the system of record for how the enterprise operates.
The protocol stackRoughly 90% of workloads never need the frontier.
Cost Governance routes by the stakes of the action rather than the habits of the developer. Standard, routine queries — roughly nine in ten workloads — go to cheaper open-weight or small in-house models; expensive frontier models are reserved for genuinely complex, high-reasoning tasks. Across 400-plus models and 70-plus providers the price spread is 4,500× (Vol. I, p.25), so the routing decision is the economics.
Cost GovernanceProviders never learn from your interaction data.
The Data Control Gateway forces data and prompt histories to stay inside the company's own cloud environment — a private tenant, in-region — and verifies training exclusion and the data boundary on every call before a token leaves. Using frontier capability never means donating enterprise interaction data to the firm that sells it back.
Data Control GatewayInteractive · routing simulator
Each workload type carries a different level of stakes, sensitivity and reasoning depth. Select one to see which Orcher component owns the decision, which model class it routes to, which gates run, and what that does to tokens and cost against a frontier-default baseline.
Workload type
Routing decision
High-volume intake: label the document, extract identifiers, route it to a queue. No irreversible write, no judgement call.
Decided by
Cost GovernanceRouted to
In-house small model
Runs inside the tenant. No egress, lowest unit cost, deterministic latency.
Token reduction
42%
1,800 → 1,044 tokens
Cost per directive
$0.00013
baseline $0.0432 on frontier model
Cost saving
100%
2360ms faster median
Gates that run before commit
Stays inside the tenant entirely — the payload never reaches an external provider.
Indicative class prices per 1M tokens: In-house small model $0.12 · Open-weight mid model $0.60 · Commercial mid-tier $4.50 · Frontier model $24.00. Illustrative only; the 4,500× spread across 400+ models and 70+ providers is from The Enterprise Superintelligence Report, Vol. I, p.25.
Interactive · economics
A frontier-default estate pays the top price band for every workload, including the nine in ten that never needed it. Move the inputs to your own volumes and see the token waste removed and the cost impact of the routine-versus-frontier split.
Your estate
One directive is one verified execution cycle.
Prompt plus completion, before scoping and redaction.
Directive scoping, field redaction and cache reuse before a model is called.
Your blended frontier rate.
In-house or open-weight class hosted in your tenant.
Estimated impact
Monthly cost, frontier default
$30.0K
1.25B tokens at the top band
Monthly cost with routing
$2.5K
$459 routine · $2.0K frontier
Token waste removed
400.0M
32% of 1.25B never reaches a model
Cost reduction
92%
$27.5K per month
Annualised
$330.0K
Retained by routing 90% of directives to a routine class and reserving the frontier for the 10% that genuinely needs it — with every routing decision hashed into the same audit chain as the action it paid for.
Estimates only, for planning conversations rather than contract terms. The 4,500× price spread across 400+ models and 70+ providers, and the 68% of AI programmes running over budget, are from The Enterprise Superintelligence Report, Vol. I (pp. 25, 9).
Proof points
Dynamic model routing is only a strategy if it moves numbers a finance team and an auditor both recognise. These are the outcomes it is accountable to.
Cost
4,500×
price spread across 400+ models and 70+ providers
The spread between the cheapest sufficient model and the frontier default is the entire economic case for routing. A directive sent to the wrong class does not fail — it just costs orders of magnitude more than it had to.
Vol. I, p.25
Token waste
~90%
of workloads never need a frontier model
Routine classification, extraction, summarisation and drafting clear on in-house or open-weight classes. Reserving frontier capacity for genuinely complex work is what turns AI spend from a run-rate into a budget.
Dipp AI routing model · Vol. I, p.25
Budget
68%
of enterprise AI programmes run over budget
Overrun is a control failure, not a forecasting failure. Cost Governance applies a ceiling per role and per directive and halts loops at the step boundary rather than at the invoice.
Vol. I, p.9
Latency
10×
faster on routine classes than a frontier default
Cheaper classes are also materially faster. Routing the routine nine-tenths off the frontier shortens the median directive as a side effect of the economics.
Indicative class latencies, Orcher routing table
Auditability
28%
of enterprises can trace an agent action end to end today
Every routing decision Orcher makes — class chosen, alternatives considered, ceiling applied, boundary attested — is hashed into the same evidence chain as the committed action, so the economics are as auditable as the outcome.
Vol. I, p.6
Portability
1 week
to change providers, not a quarter of re-platforming
Because orchestration is decoupled from any vendor SDK, a provider change is a routing-table change. Directives, roles, policy and evidence stay in Orcher.
Dipp AI protocol stack contract
Layer 1 — sequential, gating
Each runs in order. A failure at any gate halts the directive; nothing partial is written.
01
Plain language becomes the permanent record of what was asked.
02
Binds the directive to a human and a role, cryptographically and revocably.
03
Verifies the proposed action against systems of record before commit.
04
Hashes the verified action permanently. Evidence, not logs.
Layer 2 — continuous, non-blocking
Data control, cost, and observability operate for the life of the directive rather than at a single checkpoint.
Figure · Orcher™
Orcher layers — entry, accountability, control
FIG. P13-01
Layer 0 · Entry
IN
Directive
A professional states intent in plain language, inside a declared role.
Layer 1 · Accountability — sequential, gating, none optional
C1
Directive Interface
Intent becomes the permanent record of what was asked.
C2
Role Identity Fabric
Authority is bound to a human and a role, revocably.
C3
Logic Scrubber
The proposed action is verified against systems of record before commit.
C4
Immutable Audit Ledger
The verified path is hashed into evidence, not logs.
Layer 2 · Control — continuous, non-blocking
C5
Data Control Gateway
Training exclusion and data boundaries verified before routing.
C6
Cost Governance
Routes by stakes and halts runaway loops.
C7
Observability
Real-time trace: which model, which role, what cost, what outcome.
Outputs
OUT.A
Verified action
Executed under authority that can be proven afterwards.
OUT.B
Dipp Intelligence
A firm-owned record of the execution path that compounds.
Why it matters
92%
have no visibility into agent identities
Vol. I, p.6
86%
cannot enforce policy against them
Vol. I, p.6
68%
of AI programs are over budget
Vol. I, p.9
5%
of CISOs could contain a rogue agent
Vol. I, p.8
Dipp AI Research · September 6, 2026
Our September commentary examines GPT-6 Astra, Claude Fable 5.1, Claude Mythos 5.1 and Muse Spark 1.3 through one enterprise question: can advanced reasoning be trusted with real work—verifiable, cost-disciplined, and in control of the enterprise’s own data?
Frontier APIs, open-weight families such as Llama, Qwen, DeepSeek, Mistral and Gemma, and enterprise-tuned models belong behind the same authority and evidence requirements.
AWS, Microsoft Azure and Google Cloud; neoclouds such as CoreWeave, Lambda and Crusoe; private infrastructure. The destination may change. The enterprise’s boundary and budget must not.
Cost Governance chooses the sufficient route. The Data Control Gateway governs egress. Observability traces the run. Human-in-the-Role binds authority, while verified execution compounds into Dipp Intelligence.
Named release examples follow the September commentary. Model families and compute providers are ecosystem examples, not a claim of certified integrations or universal availability.
Read Frontier Autonomy Needs a Control Plane →Execution path
Orcher does not replace the agents, the orchestration framework, or the models already in the estate. It sits in front of them and decides, per directive, whether the work may proceed — and writes down what it decided.
Plain-language intent arrives with the issuer's identity attached. Anonymous directives are refused at the door.
The Role Identity Fabric resolves the professional's current entitlements and binds them cryptographically to this cycle.
The Logic Scrubber checks the plan against systems of record — eligibility, policy, licensure, limits — before anything is written.
The Data Control Gateway redacts, routes, and enforces the enterprise data boundary for every payload leaving the estate.
Cost Governance selects a tier within the ceiling in force; Observability streams the run across whichever providers are involved.
The result and the full decision trace are written to the Immutable Audit Ledger and retained as Dipp Intelligence.
Deployment
No re-platforming, no model migration, no rewrite of the agents already in production.
Scope
Pick one workflow where a named professional already signs off today.
Bind
Map the roles and entitlements that workflow depends on into the identity fabric.
Verify
Point the Logic Scrubber at the systems of record the decision is judged against.
Prove
Run in shadow, compare refusals to human judgment, then move the gate in front of commit.
Output B · Dipp Intelligence
OUT.B of the Verified Execution Cycle is Dipp Intelligence — the verified execution path, retained by the enterprise rather than absorbed by a model provider.
Path
The exact sequence that produced a verified outcome.
Role
The authority under which the action was permitted.
Cost
The model tier that actually proved sufficient.
Proof
The hashed evidence a regulator will accept.
Further reading · September 2026
Two long-form pieces per week through September 2026 — sourced, dated, and attributed. Each one links back to the components it argues about.
Jul 28, 2026
A new artificial intelligence research and product company, founded to close the gap between what enterprises can deploy and what they can prove.
By Odero Otieno
Aug 10, 2026
A 37-page examination of why enterprise agentic adoption has outrun the ability to account for it — and the seven-component architecture that closes the gap.
Aug 12, 2026
A contractual promise not to train on customer data is not a control. Dipp AI publishes the architectural commitment it holds itself to instead.
By Odero Otieno
Aug 14, 2026
Recommending a cheaper model is advice. Refusing to dispatch above a ceiling is governance. Orcher now enforces the second.
The Component Schematic v1 traces a single directive from plain language through to a hashed record and a retained intelligence asset.
