Architecture Maps

Architecture maps visualise the complete data flow from external sources through the canonical model, projection layers, APIs, and UI views on an interactive grid.

April 1, 2026

End-to-End Data Flow Visualisation

Architecture maps lay out the complete data pipeline on a grid. Each node represents a data layer: external sources, the canonical model, projection layers, API endpoints, and UI views. Edges show how data flows between them. The grid layout provides a clear visual hierarchy, reading left to right or top to bottom depending on your preference.

Grid-Based Layout

Nodes are positioned on a structured grid for clear visual hierarchy. The grid keeps layouts tidy and readable even for large architectures.

Auto-Derived Edges

Edges between projections are derived automatically from chain references in the model. No need to draw connections manually.

Step Flows

Define processing steps between nodes with decision logic and edge metadata. Describe the transformations that happen at each stage.

Anchor Elements

Decorative elements like icons, labels, and spanning blocks can be anchored to nodes with a relative grid offset for visual context.

Node Types

Several node types represent different stages of the data pipeline. External source nodes represent data that enters from outside the system. Model nodes are derived from the canonical graph. Projection nodes represent each transformation layer where data is reshaped for a specific purpose. Integration nodes cover APIs and UI views that consume projected data. Group hull feeders can import groups of related entities from the model, letting you show domain boundaries on the map.

Step Flows Between Nodes

Step flows define the processing that happens between architecture map nodes. Each step flow is a mini-sequence of operations connecting one node to another. Decision nodes branch based on conditions, letting you represent routing logic. Process nodes describe transformations such as enrichment, validation, or format conversion. Each step carries configurable metadata so readers understand what happens at every stage of the pipeline.

Simulating Change on the Map

Architecture maps are also the canvas on which the architecture simulator runs. From any node, an architect can open the simulator, pick a change (retirement, deprecation, rename, type change, move) and watch the cascade colour every downstream casualty by severity. Mitigations are proposed in place: marks-as-fixed for consumers the team owns, structured shims for adapters, aliases or new artefacts. The result is saved as a hypothesis that can be cited from an ADR or bundled into an options paper.

Architecture Simulator

A what-if engine that runs against the model itself. The architect picks a target, picks a change, and the simulator colours every downstream casualty by severity. Mitigations are structured. The plan is saved as a hypothesis that can be reopened, cloned, cited from an ADR, or bundled with siblings for an options paper.