Infrastructure

Infrastructure is the shared layer that keeps Sustainable Catalyst coherent and auditable:
common entities, traceable sources, reproducible exports, and documentation standards that reduce drift over time.

Goal: if a claim is made, we should be able to show what it’s based on—quickly, clearly, and without hand-waving.

What this is

This page describes the internal standards and building blocks that sit beneath the modules.
It’s not a hosted platform promise—it’s a public description of how the work stays reviewable.

If you want the conceptual “one-pager” view, see the System Overview in Foundations.

Shared layers

  • 1) Common Entities

    A shared “system of record” for organizations, topics, geographies, instruments, periods, and claims—so modules reference the same things.

    Keeps language consistent across tools.

  • 2) Sources & Provenance

    Every metric and narrative claim should point to sources. Where uncertainty exists, it’s documented—not buried.

    Reduces reporting and narrative risk.

  • 3) Measurements & Methods

    Define how indicators are calculated, updated, and interpreted. Methods are versioned so changes can be audited later.

    Supports reproducible analysis.

  • 4) Exports & Reproducibility

    Outputs should be portable: clean exports, clear schemas, and workflows that can be rerun without tribal knowledge.

    Avoids “spreadsheet archaeology.”

How modules connect

Most modules can stand alone, but they become significantly more useful when they reference shared entities and evidence.
Infrastructure provides those common references.

Catalyst Data

The shared relational layer: entities, sources, indicators, measurements.

Learn More →

Narrative Risk

Claims and evidence stay linked to sources, timelines, and methods.

Learn More →

Global Impact Catalyst

Indicators and reporting pipelines built for review and reuse.

Learn More →

Analytics R

Reproducible analysis and scenario workflows that reference the same system of record.

Learn More →

Over time, this layer becomes the “glue” that prevents separate tools from becoming separate realities.

Standards

  • Evidence discipline

    Claims should be explicit. Sources should be linkable. Uncertainty should be stated. “Confidence” should be earned.

    See: Editorial Ethos

  • Versioned methods

    Indicator definitions, transformations, and assumptions should be versioned so changes don’t rewrite history.

    Prevents silent drift.

  • Portable outputs

    Prefer exports and documentation that can travel across teams, tools, and reviewers—without losing context.

    Builds trust in the work.

  • Human-readable documentation

    Documentation is written for real readers. If it can’t be explained clearly, it’s not finished.

    Supports onboarding and review.

Notes

Infrastructure is evolving. Some elements exist today as documentation and patterns, others as working code and schemas.
The guiding rule is consistency: shared references, traceable work, reproducible outputs.

Tools are provided as-is. Consulting is available for governance, measurement design, and responsible implementation guidance.

 

Scroll to Top