Changelog is the structured record of visible change.
This route is reserved for concise, chronological updates across public routes, applications, and shared platform surfaces.
Help returning users understand what changed and where to go next.
Format
Structured
Entries should be concise, chronological, and useful to repeat visitors.
Coverage
Cross-system
Changes can span routes, applications, doctrine, and support layers.
Primary CTA
01
The page should route the user from change history into one updated surface.
This page matters because it helps the founder reduce ambiguity and move into a clearer next decision.
Apollo treats this as part of one connected operating system, so learning, tools, and support should reinforce each other here.
The founder should use the primary action on this page to move into the next concrete step: open roadmap.
Connected pages
Likely change sources
These routes are likely to generate meaningful public-facing updates early.
The parent-system view of what Apollo is and why the ecosystem exists.
Open OverviewThe stronger articulation of the standards Apollo is trying to uphold.
Open ManifestoThe operating rules that should keep product, content, and software aligned.
Open PrinciplesA shared pricing surface spanning learning, software, and founder-support layers.
Open PricingA single intake route for starting a conversation or qualifying a next step.
Open ContactRelated Applications
Related Applications
Applications aligned to this page that help translate understanding into action.
A visibility layer for sharper synthesis, framing, and decision readiness.
Open Clarity°Command-layer software for operators managing multiple client realities.
Open Signum°Founder advisory, operating visibility, and system-level decision support.
Open Advisors°Related Learning
Related Learning
Learning routes connected to this context so the user can deepen understanding before acting.
Short-form ideas, operating notes, and fast-moving thinking.
Open ArticlesRelated Case Studies
Related Case Studies
Applied examples can clarify when this page should become an execution priority.
Applied examples that connect theory, systems, and operator outcomes.
Open Case StudiesRelated Pages
Related Pages
Pages in the same system context that keep orientation and decision flow intact.
The parent philosophy, doctrine, and system logic behind the whole platform.
Open ApolloCapability-led discovery across Apollo applications, tools, and operating surfaces.
Open BuildPublic founder support pathways covering diagnostics, advisory, and collaboration.
Open GrowA placeholder for product direction and public-facing build sequence.
Open Roadmap