Resource
Decision history with current consequences
Earlier choices retained only where their rejection explains a current Atlas constraint.
Resource decision-history
The current release followed a first-principles reset. Earlier work mixed semantic modeling, spatial navigation, publication behavior, deployment, and compatibility concerns before the core identity model had settled. The reset removed those surfaces from the current contract instead of preserving them as dormant alternatives.
Three consequences remain active. First, one Point now keeps one Atlas-wide identity through an anchor and same-named Map-local context records; the primary Map establishes provenance without exclusive ownership. Second, publication eligibility is an exact profile allowlist, while compilation and non-disclosure remain portal-build responsibilities. Third, the portal direction starts with direct documents and a stable reader shell rather than making a Map workspace the required entry point.
Checks also remain part of the write system. Removing them would leave project-specific authoring policy outside the portable Atlas boundary, while treating them as mapped context would confuse policy with meaning. Their current contract therefore keeps them separate, bounded, and fail-closed.
The separate dated archive preserves discarded implementations and intermediate choices. The active repository does not carry their runtime behavior, aliases, migration paths, branches, or tags.