Orcher · Architecture
Component Schematic v1
One directive, traced from the moment a professional states intent to the moment the record becomes permanent — and the intelligence stays with the firm.
Layer 0
Entry: a professional states intent.
Layer 0 is the entry point — a human in a role, issuing a directive in plain language. Nothing enters the execution path without one.
Layer 1 · sequential, gating, none optional
Four checks, in order, before anything commits.
L1.1
Directive Interface
Plain language becomes the permanent record of what was asked — before interpretation, before execution.
L1.2
Role Identity Fabric
The directive is bound to a named human and their role, cryptographically and revocably.
L1.3
Logic Scrubber
The proposed action is verified against systems of record in a separate process boundary. 'Will not' becomes 'cannot'.
L1.4
Immutable Audit Ledger
The verified action is hashed permanently. Evidence, not logs.
Layer 2 · continuous, non-blocking
Three controls that run alongside every cycle.
L2.1
Data Control Gateway
Training exclusion and residency are verified before routing; egress is controlled, not asserted.
L2.2
Cost Governance
Routing by stakes, with runaway loops halted rather than invoiced. 40–85% spend reduction in deployment.
L2.3
Observability
Real-time cross-provider trace: which model, which role, what cost, what outcome.
Halt semantics
Nothing partial is ever written.
If any Layer 1 step fails — an ambiguous directive, a revoked role, a reconciliation mismatch against the system of record — the directive halts. There is no partial commit, no compensating transaction to unwind, and no orphaned write for an investigation to discover weeks later. The halt itself is recorded.
This is the difference between a model that will not misbehave and a system in which it cannot. Guardrails persuade; a gating boundary refuses.
Two outputs
Every cycle produces evidence and intelligence.
OUT.A is the verified action and its hashed record. OUT.B is Dipp Intelligence — the verified execution path, retained by the enterprise rather than absorbed by a model provider.
Cycle metrics
Verified Execution Cycles
OUT.A
Verified action, permanently hashed
OUT.B
Dipp Intelligence, retained by the firm
7
components engaged per cycle
1
named human accountable, always
The schematic is the product.
Nothing in Orcher is optional decoration; each component exists because a documented failure mode required it.