LCED
Lattice Core Explainer Document
LCED is the explanatory and interpretive document within the canonical Lattice Core documentation framework.
It makes Lattice Core and its canonical architecture accessible without replacing the documents that govern, define, standardise, or specify the system.
Document Status
Lattice Core Explainer Document
Document: LCED
Full title: Lattice Core Explainer Document
Document role: Explanation and interpretation
Authority domain: Explanatory
Current state: Alignment with verified architecture
Governance authority: LSN Foundation
Release Deferred Pending Architectural Verification
Publication of LCED has been deferred while the canonical architecture is reconstructed and verified in LCAD.
LCED will be aligned against the verified architecture before public canonical release so that explanation follows the architecture rather than becoming a source from which unfinished architecture is inferred.
Role of LCED
Explanation & Interpretation
LCED provides conceptual and accessible explanation of Lattice Core, its architecture, its relationships, and its place within the wider Lattice Semantic Nexus ecosystem.
It may teach, contextualise, illustrate, and interpret canonical material so that the architecture can be understood without requiring every reader to begin with its authoritative architectural, standards, or specification documents.
Explanation Does Not Create Authority
LCED does not acquire governance, architectural, standards, or specification authority by explaining material from those domains.
Where explanatory material conflicts with an authoritative substantive document, the document that owns the relevant subject matter controls.
Explanatory Responsibility
LCED is a substantive canonical document with an explanatory and interpretive role. Its responsibility is to make canonical Lattice Core material understandable while preserving the authority boundaries of the documents it explains.
Explain
LCED explains canonical concepts, structures, relationships, and purposes in accessible language.
Contextualise
LCED places canonical material within the wider conceptual and ecosystem context required for understanding.
Illustrate
LCED may use examples, conceptual framing, and explanatory structures to make canonical material easier to understand.
Interpret
LCED may interpret the significance and relationship of canonical material without changing its controlling meaning.
Canonical but Non-Controlling
LCED belongs to the substantive canonical corpus, but it does not control governance, architecture, standards, or detailed specification. Its canonical status does not make explanation an alternative source of authority for those domains.
Architecture First. Explanation Second.
LCAD Establishes the Architecture
LCAD is the controlling source for what Lattice Core is architecturally. It establishes the architectural constituents, relationships, responsibilities, boundaries, invariants, primitives, canonical layers, and architecture-level conditions.
LCED Explains the Architecture
LCED takes established canonical architecture and presents it at explanatory altitude. It may clarify what architectural propositions mean and why they matter without becoming the source of those propositions.
This dependency is the reason LCED publication follows architectural verification.
No Architectural Reconstruction from Explanation
Explanatory material must not be used to silently supply missing architecture. Where architectural content requires verification or reconstruction, that work belongs in LCAD before the resulting architecture is propagated into LCED.
Seven-Layer Architecture
LCED explains Lattice Core as a seven-layer substrate architecture. The canonical layer identities remain part of the established architectural structure, while their authoritative architectural definitions belong to LCAD.
Layer 1 — WAL: Web Attestation Layer
Layer 2 — ITL: Identity and Trust Layer
Layer 3 — LSL: Lattice Semantic Layer
Layer 4 — LW: Lattice Web
Layer 5 — LP: Lattice Protocol
Layer 6 — SEL: Safety Evaluation Layer
Layer 7 — LPL: Lattice Personal Ledger
This record identifies the established layer structure without attempting to reproduce explanatory content that remains subject to alignment against the verified architecture.
Relationship to the Canonical Corpus
LCED is one of five substantive canonical documents. It explains and interprets material whose controlling authority remains with the canonical document responsible for the relevant subject matter. LCAAD maps the corpus without substantive authority.
LCGD
Governance
Governs authority, stewardship, lifecycle, change conditions, and maintenance of the canonical corpus.
LCAD
Architecture
Establishes the architecture of Lattice Core and controls questions of architectural definition.
LCStD
Standards & Conformance
Formalises normative standards and conformance requirements derived from LCAD without redefining the architecture.
LCSpD
Detailed Specification
Expresses detailed technical and functional specification derived from LCAD and LCStD without redefining either.
LCED
Explanation
Explains, contextualises, illustrates, and interprets canonical material without acquiring authority over the domains it explains.
Current record
LCAAD
Architecture Atlas & Corpus Map
Maps canonical subjects, document relationships, and traceability without substantive authority over the material it maps.
Authority Boundaries
LCED May Explain
Canonical governance, architecture, standards, specification, ecosystem relationships, and other material where explanation supports understanding.
LCED Does Not Define Governance
Governance authority, stewardship, document lifecycle, and change conditions belong to LCGD.
LCED Does Not Define Architecture
Architectural constituents, relationships, responsibilities, boundaries, invariants, primitives, canonical layers, and architecture-level conditions belong to LCAD.
LCED Does Not Define Standards
Normative standards and conformance requirements derived from architecture belong to LCStD.
LCED Does Not Define Specification
Detailed technical and functional specification derived from architecture and standards belongs to LCSpD.
LCED Does Not Control Conflicts
Where explanatory material differs from an authoritative substantive source, the document that controls the relevant subject matter determines canonical meaning.
Ecosystem Context
LCED provides explanatory context for Lattice Core within the Lattice Semantic Nexus. The Lattice Semantic Nexus is the structured relationship between four distinct functions and is not itself a separate institution.
Lattice Core
Architecture
The canonical architecture and foundational seven-layer substrate.
LSN Foundation
Governance & Stewardship
Governs and stewards the framework through which canonical Lattice Core is maintained and evolved.
Lattice Research Institute
Independent Research & Analysis
Independently researches and analyses Lattice Core, related systems, and the wider environment in which the architecture may operate.
Lattice Community Groups
Participation & Community Engagement
Provide structured participation, practitioner knowledge, community perspective, and stakeholder contribution without acquiring canonical or governance authority.
Alignment & Publication
Alignment Against Verified Architecture
LCED publication follows verification of the architecture it explains. The document is therefore being aligned against the reconstructed LCAD and the current canonical documentation model before public release.
This preserves the direction of dependency between architecture and explanation and prevents historical explanatory material from becoming an unintended source of architectural authority.
What This Record Establishes
This record establishes LCED's identity, explanatory role, authority boundaries, and relationship to the wider canonical corpus.
It does not constitute publication of a current LCED edition. Version, publication, and document-access information will be recorded here when the applicable canonical edition is formally released.
Version & Continuity
Version History
Formal LCED editions are recorded by version so that changes across the document's public history can be identified and traced.
Archive
Superseded public editions may be preserved as part of the documentary record while remaining clearly distinguished from any current canonical edition.