Point
A Map-first workspace was rejected
Earlier portal work made spatial or Map navigation the primary experience before direct reading and the semantic core were adequately protected.
- Posture
- asserted
- Lifecycle
- superseded
Earlier portal directions centered the Map workspace, spatial interaction, and implementation architecture before the project had established direct-document parity or a stable Point contribution model. That emphasis risked turning the metaphor and navigation surface into the product instead of testing whether mapped context improved understanding.
The current direction replaces that assumption with immediate reading and stable surrounding navigation. The historical Point remains only because it explains why old components, routes, generated contracts, visual choices, and deployment code are not constraints on the next implementation.
Reader experienceThe rejected Map-first approach shows the navigation ceremony the new reader must not repeat.