On this page
In short#
How MSO Cloud is built and why, for engineers who review, extend or integrate with it. Each page ends with its decisions and the gate enforcing each.
System#
System contextPeople, sources, called services and what crosses the boundarySystem architectureApplications, packages, stores, the request path and the AI layerTenancy and securityOrganization and brand isolation in the database, secrets, masking and sign-inApp family and sign-inOne sign-in, a launcher and entitlements across the appsApp family and identity hubThe arc42 write-up: tokens, claims, logout, deploymentPlatform API and eventsScopes, endpoints, signed webhooks, retries, idempotency
Data#
Decisions and measurement#
Extension and technology#
Configured, not codedEvery seam that carries a customer-specific answer as dataTechnology and deploymentThe stack, why each layer was chosen, runtime topology, self-hosted postureQuality gatesThe stages every change passes and what each one provesArchitecture decisionsEvery decision on one table, by areaFuture directionWhere the architecture is heading, with the source of each direction
Where it stops#
These pages describe what is built. Readiness and dated evidence per capability are on Project status; directions are on Future direction.
In this section
The learning loopThe learning loop carries a source event to a ranked proposal, a person's decision, a measured outcome and a label, and feeds the label back into the…Plugin developmentAn optional feature or connector is a plugin: a declarative manifest plus the code it describes, gating a page, a menu item and a data route.Design system and themingOne shared component kit, one set of design tokens: a screen asks for a role and the active theme decides what it looks like, so the same screen is…Security disclosure policyHow to report a suspected vulnerability in MSO Cloud and what happens after you do.Limits and budgetsEvery numeric limit the product enforces, the file that holds it, the external standard it traces to, and whether it meets that standard.Event contractEvery event and record shape that crosses a process or system boundary, with where it is written and read, what identifies it, and what lineage it…Dataset pack fieldsOptional fields a dataset pack can declare to shape a page, a card or the navigation.
API reference
OverviewThe internal application API behind the MSO Cloud web app: tRPC v11 (superjson and Zod) at /api/trpc/[trpc] , plus a few plain HTTP routes.Sign-in and workspaceSession context, members, organizations and brands, passkeys and organization sign-in.Dashboards and explorationDashboards, templates, versions and delivery, Explore, brand comparison and AI insight cards.Commerce dataOrders, products, inventory, creators, reports and customer operations over the organization's own data.Marketing performanceAd spend, web analytics, owned channels, leads and plan bindings from the organization's own sources.Content IntelligenceA conversation corpus: taxonomy, insights and presentation decks.Data sources and datasetsConnections, shared credentials, uploads, mapping templates, backfill, validation and organization datasets.Market and social intelligenceThe third-party estimate plane, kept apart from first-party validation and from chat.Signals and decisionsSignals, alerts, the morning brief, actions, playbooks, memos and the decision ledger.AI and chatThe data assistant, per-organization AI configuration and the prompt registry.NotificationsThe in-app inbox, channel configuration and per-organization notification policy.AdministrationPlatform administration, organization data and backup, menus, blueprints, appearance and masking.Sharing and publicDashboard and report share links, and public surfaces that need no sign-in.