Orcher · Component 05 of 07
Training exclusion and data boundaries verified before routing.
Layer 2 — continuous, non-blocking
Before a single token leaves the enterprise, the Data Control Gateway verifies the destination's training policy and data-boundary posture against the classification of the payload. Vendor terms change; defaults flip. The gateway treats every provider's policy as a runtime condition to be checked, not a contract to be trusted.
Without it, exclusion is a checkbox
De-identification is not anonymization, and a default that changed last quarter is not a control. Roughly 300,000 organizations were affected by a single default change in August 2026.
What it emits
A per-call data-control verdict, attached to the execution record.
Evidence
Figures drawn from the Enterprise Superintelligence Report, Vol. I, August 2026.
34.8%
share of enterprise AI traffic carrying sensitive data
from 10.7% — Vol. I, p.24
410M
DLP violations recorded across enterprise AI channels
Vol. I, p.24
7 yrs
maximum retention exposure under the policies surveyed
Vol. I, p.24
Figure · Orcher™
Vendor training-policy comparison
FIG. P24-01
| Provider class | Enterprise default | The caveat that matters |
|---|---|---|
| Frontier API providers | No training on API inputs | Consumer and free tiers differ; retention windows are set by policy and by court order. |
| Hyperscaler AI services | No training on customer data | Scope depends on the specific service and region selected. |
| SaaS applications with embedded AI | Training on by default in several products | Roughly 300,000 organizations affected by a single 2026 policy switch, with retention up to seven years. |
| Open-weight self-hosted | No provider training path | Control moves to the operator, along with the obligation to prove it. |
Mechanism
Four stages, in order. Layer 1 components gate execution; Layer 2 components run continuously and never block.
01
Classify the payload
Every outbound payload is classified before routing: regulated personal data, protected health information, privileged material, trade secrets, or unrestricted content.
02
Check the destination posture
The candidate provider's current training policy, retention window, and processing region are evaluated as runtime conditions — not as a contract signed eighteen months ago.
03
Permit, re-route, or block
If the destination satisfies the classification, the call proceeds. If it does not, the gateway re-routes to a permitted provider or region, or blocks the call outright.
04
Record the verdict
The data-control decision is attached to the execution record, so the question of where a given payload went, and under what policy, is answerable per call.
Operational contract
What it is not
It is not a DLP replacement
DLP inspects content leaving the network. The gateway governs which model, operated by whom, in which jurisdiction, under which training policy, may see that content at all.
It is not de-identification
De-identification is not anonymization, and treating it as such is how sensitive material ends up in a training corpus. Classification plus destination control is the actual control.
Failure behaviour
If a provider's posture cannot be verified at call time, the gateway treats it as non-compliant and blocks or re-routes. A default that changed last quarter is not a control.
Questions
Where it shows up
Surfaced automatically from the components each solution engages and each industry relies on.
Solution
Verify where data goes before it goes there.
Use case
Clinical authority cannot be delegated to a process.
Use case
Physical consequence closes the loop on digital authority.
Use case
Public decisions must be explainable to the public.
The strategy behind the component
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 GatewayProof 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
The other six
Layer 1
Plain language becomes the permanent record of what was asked.
Layer 1
Binds the directive to a human and a role, cryptographically and revocably.
Layer 1
Verifies the proposed action against systems of record before commit.
Layer 1
Hashes the verified action permanently. Evidence, not logs.
Layer 2
Routes by stakes and halts runaway loops.
Layer 2
Real-time cross-provider trace: which model, which role, what cost, what outcome.
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.
Sep 16, 2026
A promise in a contract is not enforced anywhere a machine can check it. The Data Control Gateway redacts, routes, and verifies an enterprise's own data boundary at the point of every call.
By Odero Otieno
Sep 28, 2026
Four of the five classic competitive moats have lost their predictive power. The one thing that cannot be bought, borrowed, or replicated is the verified record of how an organisation's own people actually work.
By Odero Otieno
Sep 2, 2026
Enterprises can trust what a model says. Very few can prove what an agent actually did, under whose authority, once it has already happened.
By Odero Otieno
Sep 9, 2026
Seven components, two layers, one verified execution cycle — built so autonomy can run at machine speed without the enterprise losing the ability to prove, on demand, what happened and under whose authority.
By Odero Otieno
Orcher is deployed with named enterprises under the Human-in-the-Role model. Request a technical briefing with the founding team.
