Skip to content
MSO CloudDocumentation

Architecture decisions

On this page

In short#

This table lists the architecture decisions that shape MSO Cloud, one line each, with the area they belong to. The full records are internal; the pages named in the last column explain the mechanism and the gate that enforces it.

Decisions that apply everywhere: the request host picks the organization, every organization runs the same build, and the three data planes never mix.

Reference#

ADR Decision Area Explained on
0001 A headless semantic layer serves analytics Platform System architecture
0002 Features and connectors are plugins in one compiled catalog, enabled per organization Composability Configured, not coded
0003 Connectors call vendor HTTP APIs directly instead of vendor SDKs Connectors Ingest pipeline
0004 The off-take loop learns from confirmed outcomes and proposes; a person approves Decision engine The decision engine
0005 AI runs on ordered connections per organization, each with ordered models and failover AI System architecture
0007 Demo posture masks identities and keeps an explicit validation agenda Security Tenancy and security
0008 Marketing data is a first-party connector family with its own plane Connectors Data planes and the warehouse
0009 Causal computation is a separate batch boundary, not part of the web request path Decision engine The decision engine
0010 Runtime database roles are exact and non-bypass; async work goes through a transactional outbox Tenancy Tenancy and security
0011 Tenant archive and restore never bypass row-level security or integrity checks Tenancy Tenancy and security
0012 Workspaces are shaped per organization by blueprints, dashboard templates and menu self-service Composability Configured, not coded
0013 Connector credentials live in an organization-level store and are shared across connectors Connectors Tenancy and security
0014 Sheet connectors carry several streams under one contract Connectors Ingest pipeline
0015 Every dashboard and report is configuration, edited in one layout editor Composability Configured, not coded
0016 Each organization gets a subdomain, and white-label domains are supported Tenancy System context
0017 One data contract and one mapping layer serve both upload and sheet transports Ingest Ingest pipeline
0020 A tenant is composed from starter packs, declared pillars and organization-created pages Composability Configured, not coded
0021 A planned number is comparable only when a person declared how to measure it Metrics Measurement and honest numbers
0025 Narrative numbers and quotes must carry proof of the facts they cite Metrics Measurement and honest numbers
0026 Metrics have one semantic definition, with KPI classification, shared by every surface Metrics Measurement and honest numbers
0027 Measurement uses the conversion the organization declared, not hard-wired orders Metrics Measurement and honest numbers
0028 Ingest is brand-bound: a shop belongs to one brand and every write resolves its brand Ingest Ingest pipeline
0029 Deck presentation is data, anchored to an oracle Composability Configured, not coded
0033 Organizations own their skins, with a brand override layer Composability Design system and theming
0034 An organization can sign in through LDAP or Active Directory, with a fail-closed bind Security Tenancy and security
0035 The morning brief is shaped per organization type Decision engine From signal to decision
0038 Tenant datasets sit on a semantic layer of declared measures and dimensions Datasets Configured, not coded
0039 Each measure declares its grain, stock or flow behaviour and the filters that apply Datasets Configured, not coded
0040 Measure expressions use a small closed expression language Datasets Configured, not coded
0041 Widgets bind to datasets by field reference through one registry Datasets Configured, not coded
0042 Dashboard packs are data, not code Datasets Configured, not coded
0043 Pages and dashboards form a hierarchy with a filter-scope law and brand-scoped navigation Composability Configured, not coded
0044 A render plan is compiled once per dashboard and cached by binding Datasets System architecture
0045 Each organization can have a branded sign-in page and its own OpenID Connect provider Security Tenancy and security
0046 Notifications pass platform, organization and person gates before leaving Notifications System context
0047 One preference store governs four linkable notification channels Notifications System context
0048 One registry maps each vertical to its plane, ingest family and pillar resolver Composability Data planes and the warehouse
0049 Dataset connectors follow one contract Connectors Ingest pipeline
0050 Notification channels and types are declared in a registry Notifications System context
0051 Masked terms are curated per organization, scoped by role, and resolved in one place Security Tenancy and security
0052 White-label is one per-organization entitlement covering a set of capabilities Tenancy Tenancy and security
0053 A loop console lets platform staff observe and draft rules while tenants answer Decision engine The decision engine
0054 Row-level security context is signed, and sign-in material sits under a separate identity Tenancy Tenancy and security
0055 Record-style datasets read through a panel read model Datasets Data planes and the warehouse
0056 AI providers sit behind adapters with capability profiles and a caching policy AI System architecture
0057 Alerts are a designable decision graph that runs from signals to alerts Decision engine From signal to decision
0058 MSO Cloud is the identity and entitlement hub of an app family Identity App family and sign-in

Decisions are never renumbered. A decision that is replaced gets a new number that names the one it replaces.