Public content moved to a static-first architecture
Source-controlled reading surfaces such as the map, Atlas, mathematicians, and concepts now use versioned artifacts and static pages.
What changed
- Public content remains source-controlled and is frozen into validated JSON artifacts at release time.
- Static pages respond from the CDN while manifest hashes and artifact-size limits are checked automatically.
- Only user data whose source of truth is PostgreSQL, such as public notebooks and future contributions, stays on a dynamic path.
Why it matters
It keeps shared explorations fast and resilient by avoiding an application-server and database round trip for each public read.
What remains unproven
Post-release CPU, response-time, and search effects still require an observation window. Shipping the architecture is not proof of impact.