Orcher · Component 02 of 07
Binds the directive to a human and a role, cryptographically and revocably.
Layer 1 — sequential, gating
Human-in-the-Role only means something if the role is enforceable. The Role Identity Fabric binds each directive to a named professional and the authority their role carries, then scopes the agent's permissions to that authority — not to a service account, not to a shared application identity, and not to a registry entry that merely records an agent exists.
Without it, agents borrow badges
Agents inherit broad service-account permissions and act with authority nobody granted them for this task. Registry sync tells you an agent exists; it does not stop it from acting outside a role at runtime.
What it emits
A role-bound authorization token attached to the directive for the life of the execution.
Evidence
Figures drawn from the Enterprise Superintelligence Report, Vol. I, August 2026.
144:1
non-human to human identities in the enterprise
up from 92:1 — Vol. I, p.11
92%
of organizations have no visibility into agent identities
Vol. I, p.6
86%
cannot enforce policy against those identities
Vol. I, p.6
14%
median role scope as a share of underlying account permissions
Vol. I, p.22
Mechanism
Four stages, in order. Layer 1 components gate execution; Layer 2 components run continuously and never block.
01
Resolve the human
The directive is matched to an authenticated person in the enterprise identity provider — not to an application, a service principal, or a shared automation account.
02
Resolve the role
The person's role at the moment of the directive determines the authority available: what they may approve, up to what value, over which populations, in which jurisdictions.
03
Mint per-directive credentials
Orcher issues credentials scoped to this directive alone — task-bound, time-bound, and expiring on completion. Median role scope in deployment is about 14% of the underlying account's permissions.
04
Enforce and revoke
Every downstream call presents the role-bound token. A role change, suspension, or revocation invalidates authority instantly, with no agent redeployment and no waiting for a credential to age out.
Operational contract
What it is not
It is not an agent registry
A registry records that an agent exists. It does not stop that agent from acting outside a role at runtime. The fabric binds authority, not inventory.
It is not a service account with better naming
Service accounts are static, shared, and over-permissioned by design. Per-directive credentials are none of those things.
Failure behaviour
If the human cannot be resolved, the role does not carry the required authority, or the entitlement is stale, the directive halts before any model call. There is no fallback identity to borrow.
Questions
Where it shows up
Surfaced automatically from the components each solution engages and each industry relies on.
Solution
Turn agent activity into evidence a regulator will accept.
Solution
Authority belongs to a person and a role — never to a service account.
Use case
Clinical authority cannot be delegated to a process.
Use case
Every adjudication is a decision someone must own.
Use case
Supervised institutions need evidence, not dashboards.
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
Verifies the proposed action against systems of record before commit.
Layer 1
Hashes the verified action permanently. Evidence, not logs.
Layer 2
Training exclusion and data boundaries verified before routing.
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 7, 2026
A person was actively supervising every action an AI coding agent took, in real time, and a production database still got deleted. The failure was not attention. It was architecture.
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
Sep 14, 2026
The industry has spent 2026 trying to bill AI agents for outcomes instead of tokens. Almost none of it has solved the harder problem underneath: proving an outcome actually happened before anyone gets billed for it.
By Odero Otieno
Orcher is deployed with named enterprises under the Human-in-the-Role model. Request a technical briefing with the founding team.
