SEMANTIC ATLAS
REFERENCE SYSTEM MAP
One canonical layer. Many target surfaces.
The reference architecture compiles heterogeneous sources into typed commitments, allocates a bounded context budget, renders for a target, and issues a receipt describing what the system can actually prove.
The moat is not routing. It is a canonical contract that makes transformation inspectable before provider-specific rendering begins.
03.1
Source plane
Documents, instructions, policies, retrieved evidence, tool descriptions, and state enter as distinguishable sources.
Ingestion records identity, origin, time, trust, and content fingerprints. Extraction may be deterministic, learned, or hybrid, but the method must be declared.
Contradictions and unresolved ambiguity remain visible. The extractor is not permitted to manufacture consensus.
- 01SOURCE
- 02IDENTITY
- 03FINGERPRINT
- 04EXTRACTION TRACE
03.2
Canonical plane
APIR stores typed commitments separately from the text that originally carried them.
Kinds include facts, goals, constraints, policies, decisions, assumptions, open questions, state, output contracts, and safety boundaries.
Each commitment carries modality, status, criticality, provenance, and relationships. The representation is designed to be target-neutral rather than linguistically neutral.
- Meaning contract: APIR core.
- Target contract: provider profile and codec.
- Evidence contract: receipt and trace.
03.3
Budget and render plane
A budgeter selects the smallest admissible commitment set under explicit criticality and dependency constraints.
The renderer then compiles that selection for a named target profile. A deterministic baseline remains available even when learned ranking or compression is introduced.
If a critical commitment cannot fit, the correct output is a blocked or degraded state with an omission record, not a silent success.
- 01APIR
- 02BUDGET
- 03PROFILE
- 04CODEC
- 05CANDIDATE PACK
03.4
Assurance plane
Verification is a vector, not a single confidence score.
Integrity, representation preservation, target uptake, and outcome compliance require different evidence and can hold different statuses at the same time.
The semantic receipt binds the candidate pack to its sources, selected commitments, omissions, verifier scope, and fingerprints. Execution remains outside this boundary.
- 01VERIFY
- 02DIFF
- 03RECEIPT
- 04TRACE
- 05AUDIT