internal active Last verified 2026-03-29

Platform Inventory

Internal inventory page for the full Topolo application surface beyond the phase-one docs slice.

Owners
platform
Source Repos
Websites/docs, Applications
Systems
Topolo Platform
Tags
inventory, platform, applications

What It Is

This page establishes that the Topolo platform spans a much broader application portfolio than the initial docs migration wave.

How It Works

The canonical inventory is represented in the systems collection and surfaced in the service registry and API coverage pages. Phase-one handbooks remain deeper for Auth, TopoloOne, Socialize, and CRM, but they are not the whole platform.

Interfaces

  • src/content/systems/*.json
  • public service registry
  • public API coverage page

Data Flow

  1. The repo inventory is normalized into the systems collection.
  2. Public and internal builds render that inventory.
  3. Deeper system docs are migrated incrementally without losing visibility of the wider portfolio.

Failure Modes

  • a shipped application exists in the repo but not in the systems collection
  • public docs imply that undocumented applications are out of scope
  • API coverage visibility lags behind the actual repo inventory

Debugging

  • compare top-level Applications/ directories against the systems collection
  • compare route or contract docs against the API coverage page
  • add inventory coverage before attempting deep handbook migration

Change Log / Verification

  • Expanded on 2026-03-29 to make the broader application portfolio visible in the canonical docs platform