Skip to content
YewForge Digital / Engineering

System page · Governance

Human-Governed Agent Orchestration

A control model built on a simple distinction: capability is not authority. Agents and local models may contribute bounded work and evidence; final direction and promotion remain human decisions.

Partially implementedLast reviewed: 15 July 2026Evidence classes: DESIGNED · IMPLEMENTED · VALIDATED

Objective, constraints and components

The model constrains work through a stated objective, scope, acceptance criteria, evidence-return contract and review-required state. A workforce can prepare plans, execute authorised tasks, report failure and request clarification. It cannot create authority, change protected scope or promote its own output.

Final authority

Human approval determines objectives, acceptance, rejection, return and promotion.

Bounded workers

Tools, services and models are treated as task-specific contributors, not governing actors.

Evidence return

Results, limitations and failure information must accompany a decision request.

Promotion gate

No result becomes canonical merely because it completed, scored well or retried.

Control flow

Human-governed orchestration

The diagram describes a governance rule, not an autonomous execution loop.

Implementation history and validation

The authority model is an explicit doctrine. Workshop interface work has implemented review-facing surfaces and disabled or removed unsupported execution controls. Recorded live-wiring work also kept ordinary conversational sending grounded and read-only where operational authority was not available.

KEJ-EV-002DESIGNED · IMPLEMENTED
Claim
Koda has an explicit human-governance model for bounded agent work.
Method
Authority doctrine review and implementation records for review-required interface controls.
Result
The public record supports the distinction between worker capability and human authority.
Limitation
The model does not prove that every future integration is complete, nor does it grant autonomous external action.
Source period
2026 doctrine and implementation records.

Failure, recovery and current state

Failure, retry, cancellation and recovery must remain bounded and visible. A retry is not a promotion; an incomplete result remains review-required. Provider and model relationships are intentionally described only as distinct contributors in a governed workflow, without private operational detail.

Future development includes stronger evidence contracts and additional bounded integrations. It excludes autonomous external action and self-authorised promotion.

Related systems and provenance

Forge Workshop supplies a review-facing workspace; Evidence and External Memory preserves the decision record; Nano Factory applies the same no-promotion boundary to model research.

Sources: canonical Workshop authority and governed-workshop doctrine, plus public implementation evidence. Provider-specific and private implementation detail is excluded.