Topolo Nodo

What It Is

Topolo Nodo is a family of retained Nodo-era surfaces for app distribution, feed delivery, feed analytics, Android playback, and Android provisioning.

Architecture

The repo is a cluster rather than a single unified application. It includes multiple worker APIs, a support UI, and Android clients with different lifecycle stages.

Runtime Surfaces

Use /systems/topolo-nodo for the current inventory of workers, UIs, and Android surfaces.

API Reference

The active contracts are curated in the docs platform and include the app-library worker, feed worker, feed analytics worker, and the Android consumers that depend on them.

Auth and Permissions

Auth expectations vary by surface. Some workers are lightweight delivery or analytics endpoints, while admin and provisioning flows should align with broader platform standards.

Data Ownership

Nodo surfaces own app-catalog metadata, feed configuration, feed analytics, playback state, and provisioning-related artifacts depending on the subcomponent.

Deployments

Treat Topolo Nodo as a retained product family with several separately deployable surfaces rather than a single product runtime.

Failure Modes

• the product family is documented as if it were one coherent app
• provisioning, feed delivery, and analytics responsibilities are conflated
• lifecycle maturity is overstated for the provisioning branch

Debugging

Start with /systems/topolo-nodo, then identify the exact sub-surface before debugging or documenting behavior.

Change Log / Verification

• Added canonical Topolo Nodo coverage and retired repo-local cluster docs on 2026-03-30