Dipp AIDipp AI

News · August 18, 2026

Dipp AI opens the Orcher design partner programme

A small cohort of regulated enterprises will run Orcher against real workloads, real audit exposure and real spend — and shape the control plane while they do it.

By Odero Otieno — Founder, CEO & CTO, Dipp AI Technologies, Inc.

The design partner programme places Orcher in production alongside existing agent estates in regulated environments. Partners bring one governed workflow, a named accountable role and an audit requirement; Dipp AI brings the control plane, the routing policy model and direct access to the founding team.

Dipp AI is opening a design partner programme for Orcher. It is intentionally small. The objective is not logo accumulation; it is to run the control plane against workloads where the consequences of an unaccountable action are real — regulated data, external auditors, material spend, and an executive who has to sign.

What a partner brings

  1. One workflow already running agents, or credibly about to. Not a sandbox: a workflow with a business owner.
  2. A named role willing to hold the standing grant for that workflow, with real bounds on value, data class and jurisdiction.
  3. An accountability requirement — internal audit, a regulator, a customer contract — that the current stack cannot satisfy.
  4. Access to the people who own cost, risk and engineering for that workflow, in the same room.

What Dipp AI brings

  • The control plane deployed against the partner's existing estate, without replacing the agent frameworks already in use.
  • A routing policy model calibrated to the partner's directive classes, data classes and spend envelopes.
  • Ledger-backed evidence that can be handed to an auditor, rather than exported from an application log and explained.
  • Direct working access to the founding team, and a published corrections practice when we get something wrong.

Select a component to reveal its Vol. I excerpt.

Layer 1 — sequential gatesLayer 2 — continuous controls01Directive InterfaceIntent captured02Role Identity FabricAuthority bound03Logic ScrubberAction verified04Immutable Audit LedgerEvidence hashed05Data Control GatewayData boundary + no-training06Cost GovernanceCeilings on autonomy07ObservabilityCross-provider traceOrcher™ · Dipp AI Technologies

Fig. CP-01 · The seven-component control plane

Fig. 1 — What a partner deploys: gates ahead of dispatch, continuous controls alongside execution, evidence written per action.

How the engagement runs

PhaseDurationOutcome
Directive mappingWeeks 1–2Directive classes, data classes and roles named and bounded
Grant designWeeks 2–4Standing grants written, refusal and escalation paths agreed
Governed pilotWeeks 4–10Live traffic through the control plane, ceilings enforced
Evidence reviewWeeks 10–12Ledger output tested against the partner's real audit question
Table 1 — The twelve-week shape of a design partnership.
1

workflow to start

Depth over breadth

12

weeks to evidence

From mapping to an auditable record

0

framework replacements required

Orcher governs the estate you already run

Who this suits

The programme is aimed at regulated industries first — healthcare, financial services, insurance, public sector and adjacent sectors — because that is where the accountability question is asked most sharply and where the answer currently costs the most headcount. It is not restricted to them. Any enterprise where an autonomous action can move money, change a record of consequence, or touch data it should not, has the same problem in a quieter form.

FIG. A01-03

What the regimes now require

Select a milestone

EU AI Act enforcement powers

The Commission can demand model evaluations and source-code access, restrict market access, and fine up to €15M or 3% of worldwide annual turnover.

Fig. 2 — The obligations partners are preparing for, and the artefact they all require.

“We would rather have four partners whose auditors test us than forty pilots nobody depends on.”

Odero Otieno, Founder, CEO & CTO, Dipp AI Technologies

Sources

Sources for every figure in this article.

Where a number comes from Dipp AI's own analysis or an observed deployment, it is labelled as such and is not presented as an independently audited third-party finding.

  1. Dipp AI Technologies, Orcher design partner programme brief (August 2026)

Case studies

Organisations that ran this argument in production.

Modelled reference scenarios with the measurement window, the components enforced and the numbers attached. Each one downloads as a PDF.

Written by Odero Otieno.

Writes the Dipp AI record on enforced governance for agentic systems — authority, enterprise data boundary, cost and compute. Every figure in this piece carries a source, and corrections are published on the record rather than made quietly.

More from Odero OtienoAuthors and editorial desk