Lore and chronicle map

Wardenseed lore is not a separate marketing microsite. It is the narrative projection of persistent world systems: chronicle events, mythic identity grammar, biome language, and community-owned world-building docs. This hub defines how public story routes connect to the world-building documentation cluster and back to Genesis entities that carry mythic labels.

The lore graph has three public entry surfaces: /lore for primary narrative framing, /story for the combined narrative and technical map, and /world/chronicle for time-ordered world events. Each surface should link into structured docs rather than ending in isolated prose. World-building cluster articles explain persistence, emergent play, governance inside fictional worlds, and how narrative memory relates to simulation boundaries.

Mythic identity on seed entities (Relic, Spirit, Crystal, Void, Biolume) is the bridge between entity layer and lore layer. Mythic category pages group seeds by identity band; world-building articles explain what identity means inside Wardenwood. Collectors traverse mythic bands to compare lore posture; readers traverse docs to understand the rule set that generated those identities deterministically.

Lore must not overclaim chain state. Gameplay and chronicle memory remain in the simulation truth layer unless a wallet action explicitly settles on Base. Documentation states this boundary repeatedly so narrative pages are classified as world design, not financial product description.

Recommended crawl path: lore-map hub → /story or /lore → world-building cluster pillar → mythic seed category → individual seed profile → related documentation on that profile. That loop ties narrative authority to inspectable entities.