Position
Why Orcher
Everyone is converging on the control layer, which is exactly why it cannot belong to any of them. Orcher's neutrality is structural: it has no model to defend.
Why the control layer cannot belong to a vendor
Fig. NEU-04
Converging on the control layer
V1
Model vendors
Have a model to defend.
V2
Cloud platforms
Have consumption to defend.
V3
Observability tools
Watch, but cannot refuse.
Structural neutrality
N1
Orcher
No model, no cloud, no routing incentive — able to refuse any provider.
Refusal is only credible from a layer with nothing to sell underneath it.
Not a model provider's console
A provider's control surface cannot credibly block that provider's model, nor trace a directive that left its estate three hops ago.
Not an agent registry
A registry records that an agent exists. It does not decide, at runtime, whether this action is within a role's authority.
Not an observability tool
Telemetry describes what happened. Orcher decides whether it may happen, then produces evidence that it was permitted.
Not a policy document
Written policy is not a control. A control refuses, halts, and leaves a hashed record of the refusal.
Guardrails ≠ governance
Eight vendors, ten platforms, one missing primitive.
Agent identity is not directive identity. Registering that an agent exists is not the same as proving that a named human authorized this action, in this role, against this record.
47%
of CISOs saw unauthorized agent behavior
5%
were confident they could contain it
38%
of organizations with a named agent owner (from 7%)
<1%
with full agent governance maturity
Landscape
Specialists, platforms, and the convergence.
Vol. I maps who is building toward this layer and what each of them structurally cannot do.
Neutrality
Who can refuse whom
Microsoft
Names the problem and sells the gateway — but is invested in both OpenAI and Anthropic. Never provider-neutral.
Google · AWS
Gateways and routing at scale, without runtime verification of the human authority behind an action.
Sierra · Glean
Vertical agents bound to one provider harness. Excellent outcomes, single-vendor evidence.
Frontier labs
Own the model and the application layer at once. Structurally conflicted as an arbiter.
Dipp AI · Orcher
Verified authority per directive, enforced across providers. No model to defend.
Architecture beats models.
Capability is rented quarterly. Accountability is built once and compounds.