Atlas view

Decision Support

This domain groups systems that solve Decision Support problems - shared vocabulary, common interfaces, and repeatable operational constraints. Use this page to see which systems already exist, what they ingest and emit, and which patterns we repeatedly rely on in this problem space.

Domains are how we avoid reinventing the same solution in slightly different shapes. When a domain repeats, it’s a signal to standardize schemas, mapping layers, auth patterns, and operator workflows.

Domain guide

How to read this domain

Definition

This domain groups systems focused on decision support workflows, shared data models, and repeatable operational constraints.

What belongs

  • Systems where decision support is the primary problem space.
  • Integrations that move, validate, or enforce data in this domain.
  • Operational tools that reduce risk and manual work for this domain.

What doesn't

  • Generic tools where decision support is incidental metadata.
  • One-off experiments without domain-specific constraints.

Typical integrations and constraints

  • Source-of-truth feeds, vendor APIs, and scheduled extracts.
  • Schema drift, credential scope, and compliance requirements.
  • Role-based access and operational review cycles.

Common interfaces

  • REST/JSON APIs and vendor export endpoints.
  • CSV, SQL views, or Sheets-based boundary objects.
  • Auth boundaries (service accounts, OAuth, SSO).
Results 2 projects
System · Active

Data Warehouse

Centralize canonical datasets in a durable storage layer so dashboards, reports, and data-driven systems can depend on consistent truth.

Reality Ingestion Canonical Storage Operational Adoption
Open project
System · Active

Perpetual Data Reports Portal

Turn recurring district report requests into stable, owned, self-service reporting products with visible refresh and ownership discipline.

Reality Ingestion Canonical Storage Human Interfaces Operational Adoption
Open project