Workflows

Workflows explain how a business or technical outcome moves through the architecture. Open Model → Workflows.

Workflow Evidence

Capture:

• Outcome-oriented name and description
• Category, criticality, and trigger
• Ordered steps mapped to architecture elements
• Transitions and decision paths
• Static Relationships implementing supported transitions
• Behavior Model nodes linked to important steps
• Canvas layout for review and publication

Static Relationships express intended structure. Workflow participation supplies the dynamic co-activity evidence used by Coupling and contributes to Blast Radius.

Behavior Links

Link a workflow step to the command, event, policy, state, question, or read model that explains what happens at that point. Add timing and relation notes when sequence alone is insufficient.

This preserves two useful levels: the workflow remains understandable to stakeholders, while the Behavior Model captures lower-level semantics.

Review Workflow

1. Name the outcome, not an implementation call.
2. Add the happy path at the level reviewers need.
3. Add meaningful decisions and failure or compensation paths.
4. Map every step to the responsible architecture element.
5. Link transitions to existing Relationships where they represent the same interaction.
6. Add Behavior links for important commands and events.
7. Revisit Coupling and Blast Radius.

Workflows are versioned, publishable, available to Archie and MCP, and usable by Explorer's simplified traffic-flow simulation.