Standards Stewardship
Preserving the boundary between architecture, standards and specification
Standards stewardship governs the documentary relationship between Lattice Core architecture, normative standards and conformance requirements, and detailed technical and functional specification.
Its purpose is to preserve clear authority boundaries as architectural requirements become increasingly precise, testable, and suitable for implementation.
The Documentary Relationship
Architecture, standards and conformance, and detailed specification are related, but they are not interchangeable. Each belongs to a distinct canonical document with a defined subject-matter responsibility.
Architecture
LCAD establishes.
LCAD is the controlling source for what Lattice Core is architecturally.
Standards & Conformance
LCStD formalises.
LCStD derives normative standards and conformance requirements from the architecture established by LCAD.
Detailed Specification
LCSpD specifies.
LCSpD provides detailed technical and functional specification derived from LCAD and LCStD.
Implementation
Implementations realise.
Implementations operate downstream from the canonical architecture, standards, and specification from which their requirements are derived.
The Core Principle
Derivation Without Redefinition
Standards and conformance requirements derive from architecture. Detailed specification derives from architecture and standards.
That derivation permits increasing normative and technical precision without giving downstream documents authority to create, redefine, repair, or silently complete architecture.
The same principle prevents detailed specification from redefining the standards and conformance requirements from which it derives.
Missing Architecture Is an Architectural Question
If standards or specification work exposes a missing architecture-level proposition, that gap must be resolved in LCAD through the applicable governance process.
A downstream document cannot repair the gap merely by introducing the missing proposition itself.
Architecture — LCAD
Architectural Authority
LCAD establishes the architecture of Lattice Core: its architecture-level constituents, relationships, responsibilities, boundaries, invariants, primitives, canonical layers, and architectural conditions.
It is therefore the controlling source for architectural questions.
Complete at the Architectural Level
LCAD must be complete at the level required to establish the architecture from which standards and specifications derive.
LCStD and LCSpD may make that architecture increasingly normative and technically detailed, but they cannot supply architecture that LCAD itself does not establish.
Standards & Conformance — LCStD
Normative Formalisation
LCStD is the canonical standards and conformance authority. It derives normative requirements from the architecture established by LCAD.
Its role is to make architectural requirements normatively precise and capable of supporting conformance assessment.
The Standards Boundary
LCStD can formalise what conformance to established architecture requires.
It cannot introduce new architecture, redefine architectural responsibilities, or treat a missing architectural proposition as permission to create one.
Detailed Specification — LCSpD
Technical & Functional Detail
LCSpD provides detailed technical and functional specification derived from LCAD and LCStD.
It supplies the level of specification needed below architecture and standards while remaining subordinate to both.
The Specification Boundary
Detailed specification can elaborate within architecture and standards. It cannot redefine either.
If specification work reveals that an architectural or standards proposition is absent, ambiguous, or requires revision, the issue belongs to the canonical document that owns that subject matter.
Conformance
A Standards Responsibility
Conformance belongs with standards rather than being collapsed into detailed specification.
LCStD establishes the normative standards and conformance requirements derived from LCAD. LCSpD may provide the detailed specification needed to implement those requirements, but it does not independently determine the standards against which conformance is assessed.
Why the Distinction Matters
Separating standards and conformance from detailed specification prevents implementation detail from silently becoming normative authority.
It also keeps architectural questions, conformance questions, and specification questions in their correct authority domains.
Implementation
Operational Realisation
Implementations are operational realisations built against the applicable architecture, standards, conformance requirements, and detailed specification.
Implementation therefore remains downstream from canonical definition rather than becoming another source of canonical authority.
Implementation Cannot Repair the Corpus
An implementation choice does not become canonical architecture, a normative standard, or canonical specification merely because it works in practice.
Where implementation experience reveals a problem or missing requirement, that evidence can inform governed change in the document that owns the relevant subject matter.
The Stewardship Boundary
Foundation Stewardship
The LSN Foundation governs and stewards the framework through which architecture, standards and conformance, and detailed specification are maintained and evolved.
That responsibility includes preserving the authority boundaries between the documents and ensuring that governed change occurs in the document responsible for the subject matter being changed.
Stewardship Does Not Collapse Authority
Foundation stewardship does not make the Foundation the substantive source of architecture, standards, or detailed specification.
LCAD, LCStD, and LCSpD retain their respective authority domains within the governance framework established by LCGD.
Governance of Change
Standards stewardship operates within the governance framework established by LCGD. Change must occur through the authority domain responsible for the proposition being changed.
Governance questions belong to LCGD. LCGD governs the governance framework, authority, change conditions, stewardship, lifecycle, and governance constraints.
Architectural questions belong to LCAD. Standards or specifications cannot silently repair, redefine, or complete architecture.
Standards and conformance questions belong to LCStD. LCStD formalises normative requirements from LCAD without introducing new architecture.
Detailed specification questions belong to LCSpD. LCSpD supplies detail within the architecture and standards established upstream.
Lower-authority material cannot indirectly amend a controlling proposition. A change must be resolved in the canonical source responsible for that subject matter.
Participation
Lattice Community Groups
Lattice Community Groups provide the participation and community engagement function of the Lattice Semantic Nexus.
Practitioner knowledge, community perspective, and stakeholder contribution can inform discussion around standards, specification, implementation, and future governed change.
Participation Is Not Canonical Authority
Participation can contribute evidence, experience, proposals, and perspective without acquiring governance or canonical authority.
A proposal affecting architecture, standards, or specification becomes canonical only through the applicable governance and documentary process.
Research & Analysis
Independent Analysis
The Lattice Research Institute can independently analyse architecture, standards, specification, implementation, and their consequences.
Research findings may expose problems, identify opportunities, or inform future proposals without acquiring canonical authority by their own publication.
Influence Without Authority
Independent research can influence future standards or architectural development through evidence and analysis.
Any resulting canonical change must still occur through the governance process and within the document responsible for the relevant subject matter.
Canonical Documentation Framework
LCGD
Governance.
Governs the framework, authority, change conditions, stewardship, lifecycle, and governance constraints.
LCStD
Standards & Conformance.
Formalises normative standards and conformance requirements derived from LCAD.
LCSpD
Detailed Specification.
Provides detailed technical and functional specification derived from LCAD and LCStD.
LCED
Explanation.
Explains and contextualises canonical material without controlling governance, architecture, standards, or specification.
LCAAD
Architecture Atlas & Corpus Map.
Maps locations, relationships, navigation, and traceability without substantive authority over the material mapped.
Distinct Authority Domains
The documentation framework is not a simplistic universal hierarchy in which one document controls every question.
Authority follows subject matter: governance to LCGD, architecture to LCAD, standards and conformance to LCStD, detailed specification to LCSpD, explanation to LCED, while LCAAD maps the corpus without substantive authority.
Preserving Corpus Integrity
Architecture must be complete at the architectural level. Downstream documents cannot silently supply missing architecture.
Standards must remain derived from architecture. Normative precision does not create architectural authority.
Specification must remain within architecture and standards. Technical detail cannot redefine either source from which it derives.
Implementation does not become canonical by practice. Operational choices may inform future governed change but do not amend the corpus themselves.
Cross-document context is permitted. Material may be repeated or cross-referenced where useful, provided the controlling authority remains explicit and no contradiction is introduced.
Change belongs in the document that owns the subject matter. This preserves both documentary clarity and the integrity of the architecture-to-implementation relationship.
Governance Areas
Constitutional Stewardship
Durable governance of the canonical corpus while preserving explicit subject-matter authority boundaries.
Document Lifecycle
Maintenance, publication, versioning, supersession, archival continuity, and documentary status.
Change Management
Controlled evolution of canonical material through the authority domain responsible for the proposition being changed.
Governance Overview
The Foundation's wider governance, stewardship, authority, and institutional boundaries.