TopoloLearn

What It Is

TopoloLearn is the Topolo application for branded learning businesses. It combines a public site, member portal, tenant studio, assessment workflows, evidence packs, certificates, and enterprise seat management in one multi-tenant product.

Architecture

TopoloLearn is split across:

• a web application for operator, studio, public, and member experiences
• a Worker API for tenant-safe reads, writes, and verification routes
• D1, R2, KV, and queues for learning, submission, certificate, and published-brand state

Runtime Surfaces

• PlatformApplications/TopoloLearn/apps/web
• PlatformApplications/TopoloLearn/apps/api
• Topolo Auth for identity, session validation, and app-switcher metadata

API Reference

The initial curated API surface lives in PlatformApplications/TopoloLearn/apps/api/src/index.ts and currently includes runtime resolution, operator and studio overview, learner overview, submission review, certificate issuance, and public verification routes.

Multi-Tenant Model

TopoloLearn is a platform product rather than a tenant-specific LMS.

• one TopoloLearn deployment serves multiple tenants
• each tenant can own multiple brands
• each brand can publish its own public and member hosts
• all application data is tenant-scoped and brand-aware

Core Feature Areas

• branded public websites
• branded member portals
• tenant studio for theme, programme, cohort, assessment, and certificate management
• artefact submissions with versioning
• rubric-based review flows
• evidence pack assembly
• certificate issuance and public verification
• enterprise seat packs and assignment

Flagship Tenant

The first seed tenant is The B2B Faculty. It proves the platform with a cohort-heavy certification programme without hardcoding TopoloLearn around that one business.

Auth and Permissions

TopoloLearn uses Topolo Auth for identity and session state. Product-specific tenant and brand roles are enforced inside the Learn worker so authenticated users only reach the operator, studio, or member surfaces allowed by their TopoloLearn role assignments.

Data Ownership

TopoloLearn owns tenant, brand, programme, cohort, assessment, submission, evidence-pack, certificate, and enterprise-seat state. Topolo Auth remains authoritative for user identity and organization context.

Deployments

TopoloLearn currently defines a Pages web surface plus a Worker API surface with Cloudflare D1, R2, KV, and queue bindings declared in the CloudControl manifest.

Failure Modes

• hostname resolution can fail when a brand has no published domain mapping
• authenticated studio or member routes can fail when Topolo Auth session validation is unavailable
• certificate issuance should remain blocked until evidence-pack and assessment gating rules are satisfied

Debugging

Start with the internal handbook at /internal/apps/topolo-learn, then inspect apps/api/src/index.ts, the D1 migration set, and the CloudControl manifest for route, schema, and deployment shape.

Change Log / Verification

• Added the initial public overview for TopoloLearn on 2026-04-08.
• Verified the doc against the new application scaffold, shared auth integration points, and TopoloLearn system entry on 2026-04-08.