Step Flow Editor

The step flow editor defines processing steps, decision logic, and data transformations between architecture map nodes.

April 1, 2026

Describing Data Processing Steps

Step flows define what happens between nodes in an architecture map. They are constrained graph editors with process nodes, decision nodes, and configurable edges that describe how data is transformed, validated, and routed as it moves through a pipeline. Rather than leaving processing logic as a black box, step flows make it visible and reviewable.

Process Nodes

Define individual processing steps with configurable metadata and descriptions. Each node represents a discrete operation in the data pipeline.

Decision Nodes

Branch the flow based on conditions with labelled yes/no or custom exit paths. Decision nodes make routing logic explicit and visible in the diagram.

Edge Configuration

Edges carry metadata describing what data moves between nodes and how. Label edges with data descriptions, conditions, or transformation notes.

Auto-Layout

The flow layout is computed automatically to maintain readability as the graph grows. Nodes are positioned to minimise edge crossings and keep the flow direction clear.

Node Configuration

Each node carries a configuration panel where you describe what the step does. Process nodes have free-form descriptions and structured metadata fields. Decision nodes have condition descriptions and branch labels. The configuration is designed to capture intent clearly so that implementation teams know exactly what each step should accomplish.

Publishing Step Flows

Step flows are published as part of architecture maps. In the published site, viewers can see the processing pipeline between any two architecture nodes, making the data transformation logic visible to the entire team. This bridges the gap between high-level architecture diagrams and the implementation detail that developers need.