internal active Last verified 2026-03-29

TopoloOne Handbook

Application handbook for the operator-facing dashboard and its dependency on Auth-backed catalogs.

Owners
platform-experience
Source Repos
Applications/TopoloOne
Systems
Topolo Auth, TopoloOne
Tags
topolo-one, dashboard, operators

What It Is

TopoloOne is the control surface for platform administration, especially API key management across registered services.

Architecture

The app is split between apps/dashboard-web and apps/dashboard-worker. The web app renders operator workflows while the worker handles runtime routing and host delivery.

Runtime Surfaces

The primary runtime host is one.topolo.app, with delivery and asset-routing behavior tied to the worker configuration.

API Reference

The dashboard contract is documented in /reference/apps/topolo-one, with Auth-backed routes serving dynamic service, scope, and resource metadata.

Auth and Permissions

TopoloOne should never own private scope catalogs. It consumes Auth-managed service IDs, API key scopes, and bindable-resource catalogs.

Data Ownership

TopoloOne owns the operator experience and local dashboard state, but Auth owns the canonical service and API key metadata catalogs.

Deployments

Deployments span the dashboard web bundle and the worker route that serves one.topolo.app.

Failure Modes

  • wrong hostname or stale bundle serving the dashboard
  • UI points at the wrong Auth route
  • data exists in Auth but the client uses the wrong service ID

Debugging

  • verify the served bundle and hostname first
  • inspect src/lib/api.ts for the exact Auth endpoint being called
  • confirm the selected service ID matches the Auth registry row

Change Log / Verification

  • Verified against the current TopoloOne API key flow on 2026-03-29