One is a composition of isolated systems. Every stable identity, schema, fault, effect, operation, requirement, provider claim, plan node, artifact, grant, observation, and historical fact has one semantic owner.
Semantic flow
The arrows show semantic consumption and lowering, not permission to import a sibling's internals. Cross-system code depends only on public owned contracts.
Eight owned representations
| Stage | Owner | Question answered |
|---|---|---|
| D-IR | Knowledge | What accepted declarations were authored? |
| S-IR | Knowledge | What is their normalized owner-validated meaning? |
| R-IR | Planning | What does this exact root require? |
| L-IR | Planning | Which provider-independent realization shapes are valid? |
| P-IR | Planning | Which exact providers, topology, targets, and costs are selected? |
| A-IR | Build | Which exact actions and artifacts materialize that selection? |
| DPL-IR | Deployment | Where are artifacts placed and grants bound? |
| REC-IR | Deployment | Which fenced actions reconcile desired and observed state? |
Runtime state and historical facts are not additional planning stages. No earlier record is accepted as later-stage evidence or authority.
Owner map
| System | Owns |
|---|---|
| Benchmark | controlled workloads, environments, measurements, comparison methodology, and governed performance evidence |
| Foundation | stable values, identities, faults, time, events, target and host facts |
| Resources | resource identity, lifecycle, ownership, containment, and cleanup |
| Authority | capabilities, effects, policy, grants, tokens, trust, identity, and admission |
| Execution | structured concurrency, tasks, cancellation, deadlines, scheduling, and backpressure |
| Contracts | semantic-domain meta-models, schemas, mappings, OCS, projections, and interoperability |
| System IDL | .one envelope, semantic grammar, implementation framing, parser, formatter, and source maps |
| Data | state, transactions, queries, layouts, conversions, and data-provider contracts |
| Communication | invocation, endpoints, streams, RPC, messaging, delivery, and transport semantics |
| Components | operations, services, jobs, workflows, placement, and component runtime contracts |
| Composition | applications, roots, areas, declaration graphs, and per-root semantic closure |
| Experience | explicit product-facing places, intents, projections, interaction state, accessibility, localization, and bounded surface contracts |
| Knowledge | semantic graph, D-IR, S-IR, provenance, explanation, and semantic facts |
| Planning | R-IR, L-IR, P-IR, provider selection, topology, costs, and inclusion proofs |
| Build | A-IR, actions, artifacts, CAS, toolchains, provenance, signing, and Build evidence |
| Deployment | DPL-IR, REC-IR, apply, reconciliation, placement, rollout, and infrastructure lifecycle |
| History | immutable causal facts, replay bounds, compensation, and forward rollback |
| Observability | observations, correlation, budgets, logs, metrics, traces, audits, lineage, and costs |
| Provider Ecosystem | provider, adapter, semantic, and language-tool supply and governed admission |
| Developer Interface | CLI, facade, project tooling, inspection, and automation orchestration |
Global invariants
- One contract has one owner and one current revision line.
- A digest commits an inspectable owner value; it never substitutes for it.
- Requirements are not grants, plans are not artifacts, and artifacts are not runtime authority.
- Closure is independent for every root and deployable.
- Optional contracts remain inert until explicitly selected for one root.
- Generated projections are disposable; source contracts and receipts remain.
- Providers and adapters are removable; contracts never depend on them.
- Unknown external outcomes are reconciled before unsafe repetition.
- A missing realization returns typed unsupported, unsatisfied, or missing-evidence output.
Normative source: repository architecture.