Does the professional have to learn a new syntax?

No. The Directive Interface accepts plain language. Normalization is Orcher's job, and where the statement is ambiguous the interface asks a clarifying question rather than guessing.

What happens if the directive turns out to be wrong?

It stands in the record exactly as issued, and a corrective directive is issued alongside it. Orcher never rewrites history — that is the point of freezing intent before execution.

How is this different from logging the prompt?

Prompt logs record what a model received. They cannot establish who asked, under what authority, or what was actually intended. The directive is authored by a person and signed before a model is ever invoked.

Can directives be issued by another system?

Yes, but only under a human role. A scheduled or system-triggered directive still resolves to the named professional whose authority it exercises, and that binding is what the ledger records.

Orcher · Component 01 of 07

Directive Interface

Plain language becomes the permanent record of what was asked.

Layer 1 — sequential, gating

A plain-language directive resolving into a structured, recorded token lattice — Plain language becomes the permanent record of what was asked.

Every Orcher execution starts with a directive: a professional states, in their own words, what should happen. The Directive Interface captures that statement as structured intent and freezes it. What was asked can never be reconstructed after the fact from a chat transcript or a prompt log, because it was recorded as the first act of execution.

Captures intent in plain language and normalizes it into a structured directive.
Timestamps and versions the directive before any model is called.
Carries the directive unchanged through every downstream component.
Makes the directive, not the prompt, the object of record in the audit trail.

Without it, intent is inferred

Prompt logs record what a model received, not what a person meant. When an action is challenged months later, an inferred intent is not evidence. The directive is.

What it emits

A signed directive record that becomes the root of the execution's audit chain.

Evidence

What the record shows

Figures drawn from the Enterprise Superintelligence Report, Vol. I, August 2026.

38%

of enterprises can name an accountable owner for agent decisions

up from 7% — Vol. I, p.2

54%

of organizations reported an agent-related incident

Vol. I, p.2

Mechanism

How it works

Four stages, in order. Layer 1 components gate execution; Layer 2 components run continuously and never block.

01
Statement of intent
A named professional states the outcome they want in their own words — approve this claim, release this payment, publish this schedule. No prompt engineering, no template, no intermediate translation by an engineer.
02
Normalization
The statement is parsed into a structured directive: the objective, the entities it touches, the systems of record it will reconcile against, and the constraints that are implicit in the professional's role.
03
Freeze and sign
The normalized directive is timestamped, versioned, and signed before any model is called. From that moment the directive is immutable; a revision creates a new directive rather than editing the original.
04
Hand-off
The frozen directive travels unchanged through the Role Identity Fabric, the Logic Scrubber, and into the ledger. Every downstream component reads the same object, so intent cannot drift between stages.

Operational contract

Input: Natural-language statement from an authenticated human
Output: Signed, versioned directive record (IN.A)
Mode: Layer 1 — sequential, gating
Mutability: Immutable after signing; revisions are new directives
Retention: Directive persists for the life of the audit record
Interfaces: Web console, API, and embedded surfaces in existing line-of-business tools

What it is not

It is not a prompt library

A prompt is an instruction to a model. A directive is a record of what a person, holding a role, asked the enterprise to do. The two are stored, versioned, and defended differently.

It is not a chat transcript

Transcripts are conversational and lossy. The directive is a single structured object with one author, one timestamp, and one signature.

Failure behaviour

If intent cannot be normalized into a directive with an unambiguous objective and scope, nothing is executed. The professional is asked to restate; no partial directive enters the chain.

Questions

What enterprises ask first

Does the professional have to learn a new syntax?: No. The Directive Interface accepts plain language. Normalization is Orcher's job, and where the statement is ambiguous the interface asks a clarifying question rather than guessing.
What happens if the directive turns out to be wrong?: It stands in the record exactly as issued, and a corrective directive is issued alongside it. Orcher never rewrites history — that is the point of freezing intent before execution.
How is this different from logging the prompt?: Prompt logs record what a model received. They cannot establish who asked, under what authority, or what was actually intended. The directive is authored by a person and signed before a model is ever invoked.
Can directives be issued by another system?: Yes, but only under a human role. A scheduled or system-triggered directive still resolves to the named professional whose authority it exercises, and that binding is what the ledger records.

Where it shows up