CatalystVisual

00 Source-backed system map

Catalyst, drawn out

Seven interactive diagrams of how this feature flag platform actually runs.

Each one is generated from a typed JSON source, validated against layout and composition rules, and delivered as a single self-contained HTML file. Nothing on these pages is drawn by hand, and every claim traces back to the repository. Start with the runtime architecture, then follow whichever flow you actually care about.

The diagrams

  1. 01 Architecture

    Runtime Architecture

    The whole system at a glance: who calls the API, what the API trusts, and where the data actually lives.

    validated 9/9 checks · Architecture · source pinned to the repo

  2. 02 Sequence

    SDK Flag Check: the Conditional Read

    One flag check, start to finish — including the cold path where the cache misses and the snapshot is rebuilt.

    validated 9/9 checks · Sequence · source pinned to the repo

  3. 03 Sequence

    Toggle Propagation: Dashboard to Next Read

    How a rollout slider in the dashboard becomes a different flag value in somebody's server, and why it cannot be missed.

    validated 9/9 checks · Sequence · source pinned to the repo

  4. 04 Workflow

    Tenant Onboarding: Register to First Flag

    What the platform creates on your behalf, and in which order, when a new tenant gets its first flag.

    validated 9/9 checks · Workflow · source pinned to the repo

  5. 05 Lifecycle

    SDK Client Read-Path Lifecycle

    The states a long-lived SDK client moves through, and why a failed flag check degrades instead of raising.

    validated 9/9 checks · Lifecycle · source pinned to the repo

  6. 06 Data Flow

    Evaluation Data Flow and the PII Boundary

    Where the caller's attributes cross the wire, and the narrow window after which they are never handled again.

    validated 9/9 checks · Data Flow · source pinned to the repo

  7. 07 Workflow

    SDK Release Pipeline to PyPI

    What has to be true before a version of the SDK can reach PyPI, and why the parity suite is the real gate.

    validated 9/9 checks · Workflow · source pinned to the repo

How to read them

  • Every artifact has guided chapters in the header. P plays them as a story.
  • / finds a node by name, R traces an exact route, and L compares two roles.
  • M opens the overview radar, F enters the presentation stage, and Esc leaves it.
  • E exports a PNG, an SVG, a video, or a share card. Exports are always the full diagram.
  • Architecture nodes marked SRC n open the exact file and line range, pinned to one commit.

Regenerating

  • visual/sources/*.json is the editable source of truth for every diagram.
  • zsh visual/check.sh validates all of them at showcase quality.
  • zsh visual/deliver.sh re-renders and commits the artifacts.
  • zsh visual/verify.sh collects bounded desktop browser evidence.
  • node visual/build-site.mjs regenerates this index and the diagram pages.