Version History
Public continuity across canonical document editions
This page records the public version history of the canonical Lattice Core documentation corpus.
As canonical editions are formally published, their version, publication state, and relationship to earlier editions are recorded here so that change remains visible and traceable over time.
Current Version History
No Public Canonical Editions Currently Recorded
The current Lattice Core documentation corpus is undergoing architectural verification, document alignment, and publication preparation.
No public canonical document edition is presently recorded in this version history.
Entries will be added when applicable canonical editions are formally released. The existence of a document within the canonical documentation framework does not by itself constitute publication of an edition.
Canonical Documentation Model
The current documentation model contains five substantive canonical documents and one non-substantive architectural atlas. Each has a distinct role within the corpus.
LCGD
Governance
Establishes the governance framework, authority, change conditions, stewardship, lifecycle, and governance constraints under which the canonical corpus is maintained.
LCAD
Architecture
Establishes Lattice Core architecture and controls questions of architectural definition.
LCStD
Standards & Conformance
Formalises normative standards and conformance requirements derived from LCAD.
LCSpD
Detailed Specification
Expresses detailed technical and functional specification derived from LCAD and LCStD.
LCED
Explanation
Explains, contextualises, illustrates, and interprets canonical material without acquiring authority over the governance, architecture, standards, or specification domains it explains.
LCAAD
Architecture Atlas & Corpus Map
Maps canonical subjects, locations, relationships, navigation, and traceability without substantive authority over the material it maps.
Document Identity Is Not Publication
A canonical document may have an established identity, role, and authority boundary before a public canonical edition of that document is released.
Version history begins with formal publication, not with the creation of a document role within the documentation framework.
What Version History Records
Version history provides a chronological public record of formally published canonical editions. It records documentary continuity without becoming an alternative source of substantive document content.
Document
Identifies the canonical document to which a published edition belongs.
Version
Identifies the formal version designation assigned to the published edition.
Publication
Records when an edition entered the public canonical record.
Status
Distinguishes an edition's current documentary state from earlier editions retained for continuity.
Relationship
Records whether an edition establishes, succeeds, supersedes, or otherwise relates to another published edition.
Archive Location
Provides a route to retained historical material where an earlier public edition has been superseded.
Why Version History Matters
Canonical Continuity
Canonical documentation can evolve without erasing the record of what previously governed, defined, standardised, specified, explained, or mapped the system.
A visible version history allows readers to distinguish a current edition from earlier public editions and to understand the documentary sequence through which change occurred.
Change Without Silent Replacement
Governed change requires more than replacing one file with another. Where a published canonical edition is superseded, the transition should remain visible in the documentary record.
Version history provides that continuity while the archive preserves applicable historical material.
Version States
Publication state and canonical document identity are separate. Once editions begin to enter the public record, their status can be distinguished without changing the underlying identity of the canonical document.
Current
The edition presently identified through the applicable governance and publication process as the current public canonical edition of a document.
Superseded
A previously current public edition that has been replaced by a later canonical edition.
Archived
A retained public edition preserved for documentary continuity and historical reference rather than current canonical use.
Pre-Publication Is Not Version History
Drafting, reconstruction, verification, alignment, and other pre-publication states may be described on individual document records where appropriate, but they do not create published canonical version-history entries.
Authority & Versioning
Version History Does Not Create Authority
Recording a document edition here does not determine the subject-matter authority of that document. Authority follows the canonical documentation framework and the responsibility assigned to each document.
Version history records which edition occupied a documentary state at a particular point in the public record.
Historical Access Does Not Mean Current Authority
A superseded or archived edition may remain publicly accessible so that the documentary record is preserved.
Continued accessibility does not make that edition current or give it authority over a later controlling edition.
Subject-Matter Authority Remains Distinct
Governance questions are controlled by LCGD, architectural questions by LCAD within the governance framework, standards and conformance questions by LCStD subject to LCAD and LCGD, and detailed specification questions by LCSpD subject to LCStD, LCAD, and LCGD.
LCED explains without overriding those domains. LCAAD maps the corpus without substantive authority.
Foundation Stewardship
Maintaining the Public Record
The LSN Foundation governs and stewards the framework through which the canonical Lattice Core corpus is maintained and evolved.
Public version history forms part of that stewardship by preserving an explicit record of formally published editions and their documentary continuity.
Stewardship Does Not Replace Subject-Matter Authority
Maintaining the public version record does not make the Foundation's version-history page an alternative source of architecture, standards, specification, explanation, or other substantive canonical content.
The applicable canonical document remains the source for the material within its authority domain.
Document Archive
Version History and Archive
Version history and the document archive perform related but different functions.
This page records the chronological public history of canonical editions. The archive provides the location in which applicable superseded or historical material can be retained.
Current Archive State
No superseded public canonical editions are currently recorded through this version history.
Historical entries and corresponding archive material can be added as the public canonical corpus develops over time.
Documentation Framework
Canonical Document Records
Individual document records identify each canonical document's role, authority boundary, current state, and relationship to the wider corpus.
Governance
Governance of canonical change, stewardship, document lifecycle, and corpus maintenance belongs within the governance framework established by LCGD.