Introduction
Overview of the Topolo documentation platform, what is considered canonical, and where to start.
What this site is
This Astro site is the canonical documentation source for the Topolo platform. It replaces scattered repo-local notes as the published source of truth for platform behavior, application architecture, API reference, and debugging entrypoints.
What is public versus internal
- Public docs explain how to build on Topolo, integrate with platform services, and understand the high-level behavior of major applications.
- Internal docs add architecture, operational flows, debugging procedures, deployment notes, and agent-oriented implementation detail.
- Both builds come from the same source content model so public and internal material stay aligned.
Where to start
- Read Quick Start for the shortest path into the platform.
- Read Authentication for token and session flow.
- Read API Keys if you are integrating across services.
- Use the Service Registry to locate ownership, repos, and app IDs.
Canonical rules
- Topolo Auth is authoritative for service registration, API key scopes, and API key resource catalogs.
- TopoloOne is the main operator-facing dashboard for platform controls.
- Application teams remain authoritative for their product data models and runtime behavior.
- Repo-local docs are source material unless they are explicitly migrated into this docs site.
Change Log / Verification
- Reconciled docs freshness on 2026-06-28 against topolo-platform through 20653c79; latest commit reviewed was 20653c79 feat(auth): bulk availability + app_id-mapping endpoints (seed subrequest cap), with recent context 20653c79 feat(auth): bulk availability + app_id-mapping endpoints (seed subrequest cap); 61117a0d feat(app-shell): add lazy component factory; d8784cfa feat(app-shell): add canonical lazy route factory.