NOMEDYukh is defining the governance semantics that should survive when the model, host, sandbox, memory system, workflow engine or human workspace changes.
BeginOwn the semantics. Reuse the machinery.
Agent systems now arrive with their own loops, approvals, sandboxes, memory, workflows and collaborative surfaces. Yukh should not rebuild those capabilities merely to own the stack. It should define the authority, attribution, coordination and evidence contracts that remain true when any one implementation is replaced.
RFC-0003 is still the accepted reference architecture. Current qualification work is testing how much of its implementation machinery can shrink, move behind adapters or disappear without weakening those boundaries.
Semanticsbefore machinery
Own only what must survive replacement.Capabilitynot custody
Authority stays explicit, scoped and composable.Evidencenot declarations
Operational facts remain independently checkable.Open seamsnot captive runtimes
Hosts, memory, sandboxes and workspaces stay replaceable.Accepted boundaries. Replaceable implementations.
The accepted reference decomposition still separates capability authority, accepted work state and live coordination. Yukh MCP, Projects and Coordination are the current implementations of those responsibilities. Agent hosts, execution, memory, orchestration and human workspaces are not automatically Yukh components.
Understand the accepted boundaries See the machinery under qualification
01Capability policy + evidenceImplements the capability-policy and evidence boundary while Track A tests composition with host-native security. Durable production readiness remains unproven.
View Yukh MCP repository
02GitHub accepted-state adapterA useful GitHub Projects implementation whose long-term architectural role is being narrowed to accepted work state. No live apply qualification is implied.
View Yukh Projects repository
03Coordination kernelCarries claims, conflict, handoff, attribution and replay semantics while transports and workspaces remain replaceable. No public/live runtime is qualified.
View Yukh Coordination repositoryNo protected components.
goose and Hermes have both passed the first runtime-substrate gate, but neither is a selected Yukh host. Apache Maka, OpenHands, OpenHuman, TencentDB Agent Memory and Buzz are being evaluated for distinct replaceable concerns rather than collected into one mandatory platform.
RT goose + Hermes PASS runtime substrate
A2 host composition DEFINED adapters not executed
C2 TencentDB Agent Memory MEMORY? contextual, never authority
EX Maka + OpenHands EXECUTION? durable facts + isolation
UX Buzz WORKSPACE? surface, not authority
Research / Architecture under qualification