The YAI native repository now uses a compressed canonical layout:
- source implementation lives under
src/<plane> - headers live under
include/yai/<plane> - protocol contracts live under
protocols/{schemas,fixtures,conformance,refs,registry} - repository meta-agent instructions live under
.agents - historical/audit material remains under
Documentation/archiveandDocumentation/internal
src/agents
src/analytics
src/capabilities
src/case
src/control
src/governance
src/knowledge
src/lineage
src/models
src/orchestrator
src/orchestrator/workflow
src/providers
src/runtime
src/runtime/access
src/statememory is registered as a native plane direction, but physical extraction is
deferred and no src/memory tree is created by this cutover stack.
include/yai/agents
include/yai/analytics
include/yai/capabilities
include/yai/case
include/yai/control
include/yai/governance
include/yai/knowledge
include/yai/lineage
include/yai/models
include/yai/orchestrator
include/yai/orchestrator/workflow
include/yai/providers
include/yai/runtime
include/yai/runtime/access
include/yai/statememory is registered as a native plane direction, but physical header
extraction is deferred and no include/yai/memory tree is created by this
cutover stack.
protocols/schemas
protocols/fixtures
protocols/conformance
protocols/refs
protocols/registryOld root source planes were moved under src/.
Old direct include/<plane> headers were moved under include/yai/<plane>.
Old direct protocol folders were absorbed into canonical protocol children:
protocols/topology -> protocols/registry/topology
protocols/naming -> protocols/refs/naming
protocols/ontology -> protocols/refs/ontology
protocols/system -> protocols/refs/systemlineage is a first-class native plane.
It is not owned by Knowledge.
flow is no longer a native canonical plane.
Operational workflow material lives under:
src/orchestrator/workflow
include/yai/orchestrator/workflowidentity is not a native top-level plane.
Identity/account/auth/authorization/entitlement/machine authorization concepts are consumed locally as runtime access projections under:
src/runtime/access
include/yai/runtime/accessThe local runtime does not own platform identity.
skills was renamed/reframed as governed capabilities.
Capabilities are governed executable/action surfaces usable by agents, operators, runtime/system components, and future external integrations such as MCP and web/search capability adapters.
Capabilities are not permissions, entitlements, provider ownership, or raw tool calls.
.agents is the repository meta-instruction surface for coding agents.
It is not the runtime src/agents plane.
The current layout must not recreate:
agents/
analytics/
case/
control/
flow/
governance/
identity/
knowledge/
lineage/
llm/
models/
orchestration/
providers/
runtime/
skills/
capabilities/
state/
memory/
src/identity
src/skills
src/flow
src/knowledge/lineage
include/identity
include/skills
include/flow
include/yai/identity
include/yai/skills
include/yai/flow
include/yai/knowledge/lineage
protocols/topology
protocols/naming
protocols/ontology
protocols/system
Documentation/operatorThese names are intentionally listed here as forbidden examples. They are not current canonical layout claims.
The ROOT cutover stack has passed:
git diff --check
git diff --cached --check
make info
make yai
make -B yai
make validate-contract
protocol JSON validation
root forbidden dir guard
source/header canonical guards
direct include folder guard
protocol direct-child guard
include stale-prefix scans
live path residue scans
current docs stale-path scans
forbidden documentation primary-section guard
symlink scan
artifact/cache scanThe ROOT cutover does not complete:
- API/SDK/Web vocabulary alignment
yai_skill_*/YAI_SKILL_*lexical/API drain- serialized
"skill"vocabulary migration yai_identity_*/YAI_IDENTITY_*lexical/API drain- serialized
"identity"vocabulary migration yai_flow_*/yai_orchestration_*lexical/API drain- cross-repo API/SDK/Web vocabulary migration
- physical
memoryextraction
memory is registered as a native plane direction, but physical extraction
remains deferred.
Baseline before the current uncommitted stack:
cffb318b9 Refactor root source layout and protocol planesAt the time this record was created, ROOT.4D through ROOT.8 remained in the current uncommitted stack.
Documentation/internal/architecture/runtime/waves/root-source-cutover/root-0-preflight-inventory.md
Documentation/internal/architecture/runtime/waves/root-source-cutover/root-1-source-plane-physical-cutover.md
Documentation/internal/architecture/runtime/waves/root-source-cutover/root-2-header-namespace-and-agents-verticalization.md
Documentation/internal/architecture/runtime/waves/root-source-cutover/root-3-build-test-tool-path-realignment.md
Documentation/internal/architecture/runtime/waves/root-source-cutover/root-4-protocol-surface-normalization.md
Documentation/internal/architecture/runtime/waves/root-source-cutover/root-4b-lineage-orchestrator-workflow-correction.md
Documentation/internal/architecture/runtime/waves/root-source-cutover/root-4c-protocol-finalization-lineage-orchestrator.md
Documentation/internal/architecture/runtime/waves/root-source-cutover/root-4d-identity-demotion-runtime-access-boundary.md
Documentation/internal/architecture/runtime/waves/root-source-cutover/root-4e-skills-to-governed-capabilities-layer.md
Documentation/internal/architecture/runtime/waves/root-source-cutover/root-4f-cutover-stack-consolidation-live-residue-guard.md
Documentation/internal/architecture/runtime/waves/root-source-cutover/root-5-documentation-current-path-realignment.md
Documentation/internal/architecture/runtime/waves/root-source-cutover/root-6-root-cleanup-forbidden-stub-removal.md
Documentation/internal/architecture/runtime/waves/root-source-cutover/root-7-full-validation.md