Skip to content

Service Catalog ​

Status: navigation and dispatch guide. The authoritative ownership definition is the Service Responsibility Matrix. This catalog does not promote a default gateway route or claim that a service slice is complete.

Entry And Identity ​

Canonical serviceImplementationAuthorityGuide
api-gatewayservices/api-gatewaySingle frontend entrypoint, routing, JWT verification, and edge concerns; no business dataAPI
bff-serviceservices/bff-serviceFrontend-specific aggregation only; owner services remain authoritativeAPI
iam-serviceservices/iam-serviceAccounts, credentials, sessions, JWT/JWKS, roles, permissions, and authoritative organization membership writesAPI
profile-serviceservices/profile-serviceEducation profile and display metadata; never credentials or access-control policyAPI

School And Learning ​

Canonical serviceImplementationAuthorityGuide
organization-serviceservices/school-service aliasOrganization and unit metadata plus IAM-synchronized member read models; IAM remains the membership writerAPI
classroom-serviceservices/classroom-serviceClasses, class members, teacher assignments, and classroom projectionsAPI
course-serviceservices/course-serviceCourses, modules, lessons, materials metadata, enrollments, and progressAPI

Assessment And Content ​

Canonical serviceImplementationAuthorityGuide
question-serviceservices/question-bank-service aliasQuestions, answers, solutions, types, tags, and taxonomyAPI
exam-serviceservices/exam-serviceExams, published snapshots, assignments, and access linksAPI
attempt-serviceservices/attempt-serviceAttempt sessions, answer state, grading, results, and attempt-owned snapshotsAPI
file-serviceservices/document-service aliasObject metadata, signed URLs, uploads, and media assetsAPI
import-serviceservices/docx-import-service aliasImport jobs, parsing orchestration, preview/draft state, and approval sagaAPI
formula-docx-servicesource-controlled runtimes/go-formula-docx runtimeDOCX/formula conversion behind import adapters; it is not a services/ directoryTask pack
ai-serviceservices/ai-classifier-service aliasAI provider adapters, prompts, jobs, and model output; no quota or credit ownershipAPI

Monetization ​

Canonical serviceImplementationAuthorityGuide
billing-serviceservices/billing-servicePlans, prices, subscriptions, invoices, and entitlementsAPI
wallet-serviceservices/wallet-serviceAZ Credits, balances, immutable ledger, grants, debits, and refundsAPI
usage-serviceservices/usage-serviceFeature gates, usage counters, quota periods, and entitlement materializationAPI
payment-serviceservices/payment-servicePayment orders, provider transactions, webhook ingestion, and reconciliationAPI

Operations And Projections ​

Canonical serviceImplementationAuthorityGuide
notification-serviceservices/notification-serviceNotification state, delivery attempts, preferences, and event fanout; recipient resolution stays with ownersAPI
search-serviceservices/search-serviceRebuildable search indexes and sync checkpoints; never canonical business dataAPI
audit-serviceservices/audit-serviceAppend-only compliance and security event history, idempotency, retention, and legal-hold metadataAPI
analytics-serviceservices/analytics-serviceRebuildable dashboard, result, progress, and mastery projectionsAPI
admin-serviceservices/admin-serviceAdmin read models, moderation, feature maintenance, and compatibility read APIs; owner data stays authoritativeAPI

Compatibility Scaffold ​

services/user-service is a deprecated compatibility scaffold. It is not a canonical service, must not receive new identity or profile work, and is tracked only through the retirement task pack.

Dispatch And Proof ​

Before assigning an agent, read the service's task pack and the current next-slice queue. An accepted handoff is bounded evidence, not service completion. Default route promotion always requires the named route, live/browser, and rollback proof for that slice.

Go-platform documentation is generated from repository Markdown.