One is organized by semantic owner. This page is a reader's map; the linked
AGENTS.md files are the normative contracts.
End-to-end flow
Foundation -> Resources -> Authority -> Execution
\ \ \
+----------> Contracts +-> {Communication, Data}
| |
+-> System IDL v
Components
|
{Composition, Experience}
|
v
Domain declarations and facts --------------------> Knowledge
Provider claims and catalog evidence -----------------+
v
Planning
|
v
Build -> Deployment
|
+--------------------+------------------+
v v
History ObservabilityDeveloper Interface orchestrates public APIs without owning their semantics. This is semantic consumption and lowering flow, not a numeric crate hierarchy.
System owners
| System | Owns |
|---|---|
| Foundation | target/host facts, values, identity, faults, time, events |
| Resources | resource identity, lifecycle, ownership, cleanup, containment |
| Authority | capabilities, effects, principals, policy, grants, trust |
| Execution | tasks, cancellation, deadlines, timers, credits, channels |
| Contracts | domains, schemas, compatibility, mappings, profiles, projections |
| System IDL | .one, System IDL, native One, parsing, source tooling |
| Data | state, storage, transactions, queries, physical data planning |
| Communication | endpoints, calls, streams, messaging, transport mappings |
| Components | operations, services, jobs, workflows, placement |
| Experience | places, intents, projections, interaction and surface contracts |
| Composition | roots, selected semantics, reachability, binding intent |
| Knowledge | semantic graph, D-IR, S-IR, provenance, explanations |
| Planning | requirements, L-IR, P-IR, provider/topology selection |
| Providers | ecosystem packages, catalogs, conformance, publisher trust |
| Build | A-IR, actions, artifacts, toolchains, provenance, signing |
| Deployment | DPL-IR, REC-IR, apply, placement, reconciliation |
| History | causal facts, effect journals, replay, compensation |
| Observability | logs, metrics, traces, audits, lineage, budgets |
| Developer Interface | CLI, facade, tooling, inspection, automation |
Composition laws
Across every system:
- every identity and contract has one owner;
- dependencies use public owned contracts;
- declarations, requirements, plans, artifacts, grants, and runtime authority remain distinct;
- optional edges are inert until selected for one root;
- generated projections are disposable;
- providers and adapters remain removable;
- unavailable behavior fails honestly;
- dependency cycles cause the smallest shared contract to move to the lowest valid owner.
Canonical root: repository architecture.