Architecture · Narrative
Readable without replacing evidence
Narrative architecture lets Heritage Journeys stay readable while Story and Research point to the same reviewed claims.
Overview
From records to readable journeys
LUX143 organizes lighthouse heritage as a traceable system. Canonical records and relations form the knowledge layer. Sources and review state form the evidence layer. Meaning and narrative architecture connect evidence to human recognition without inventing facts.
Focus
Narrative focus as reading contract
Narrative focus separates the reader's subject from the technical root object. A journey may follow an asset, place, route, or phenomenon while canonical identity stays stable.
Focus is a reading contract — not proof that every interpretive frame is public-ready.
Structure
Story beats and narrative units
Story beats hold presentation and sync metadata. Narrative units link readable claims to evidence, sources, media, relations, and open questions. Narrative plans record archetype, central question, transformation, and resolution — all reviewable before publication.
The architectural rule: Story copy must not drift away from Research evidence.
Layers
Knowledge, evidence, meaning, renderers
Knowledge — identities, relations, assets, places, and focus metadata.
Evidence — sources, field claims, confidence, review state, and attribution.
Meaning — reviewed interpretation of why a continuity matters; authored, not computed.
Renderers — Story, Research, and QA views over the same base. Future compiler-like tools suggest; they do not publish facts.
Knowledge
Structured identities, relationships, places, assets, and continuity threads across time.
Evidence
Sources, claims, confidence, attribution, review state, and open questions that explain why a claim may appear.
Meaning
Reviewed interpretation that helps readers recognize why evidence-backed continuity matters.
Narrative Architecture
Story beats, narrative units, narrative focus, and plans that keep readable copy tied to evidence.
Renderers
Story, Research, QA, and future assessor tools as views over the same reviewed material.
Narrative Focus
The reader's subject may differ from the technical root — asset, place, route, landscape, or phenomenon.
Boundary
What stays editorial
Meaning, narrative framing, climax emphasis, and public copy remain authored and reviewed. Computed suggestions may assist QA, but provenance before narration is the rule.
Internal pilots, personal material, and operational review tools stay out of public discovery until explicit publication gates are met.