03 / System
Own the boundaries. Replace the machinery.
RFC-0003 remains the accepted Yukh reference architecture. Current qualification work is testing how much implementation machinery can be external without changing the authority, coordination, evidence and accepted-state semantics that must survive replacement.
The architecture and the repositories are not the same thing. The accepted reference decomposition still separates capability authority, accepted delivery state and live coordination. Those boundaries remain authoritative until an RFC supersedes them; the current repositories are implementations of those responsibilities, not protected product pillars.
The working architectural principle is now explicit: Yukh should own semantics only where they must survive replacement of the model, host, runtime, workspace or vendor. Hosts, sandboxes, workflow engines, memory systems and human interfaces are machinery to reuse when they preserve those boundaries.
Current Yukh implementations
- 03.1 / MCPCurrent capability-policy and execution-boundary implementation
- 03.2 / ProjectsCurrent GitHub Projects adapter for accepted work state
- 03.3 / CoordinationCurrent coordination-kernel implementation
Replaceable machinery under qualification
| Concern | Current qualification posture |
|---|---|
| Agent host | goose and Hermes are qualification candidates; both passed only the runtime-substrate gate. |
| Durable execution | Apache Maka is the first AgentRun / execution-evidence candidate. |
| Execution isolation | OpenHands is being evaluated as an external sandbox/execution provider. |
| Orchestration | OpenHuman is a workflow/orchestration challenger, not an accepted Yukh control plane. |
| Shared memory | TencentDB Agent Memory is the Track C2 candidate; Hermes and OpenHuman memory are benchmarks. |
| Workspace | Buzz and other human-agent surfaces may carry interaction without owning Yukh authority. |
No external candidate is adopted by this page. goose and Hermes have passed the first executable runtime-substrate gate, while the stricter Yukh host-composition Gate A2 is defined but not yet executed against candidate adapters. No reference host has been selected.
See the active qualification landscape Inspect implementation and qualification work