Data Flow Mapper

Workflow planning requires tracking artifact provenance by listing all produced artefacts alongside their producers, consumers, formats, and purposes. This process creates a structured, auditable catalog detailing why each artifact exists within your workflow.

Identifying orphan or missing artifacts requires consistency enforcement rules that verify every artifact has a producer and a consumer. The mapper actively surfaces orphans and missing requirements, failing the planner if any non-empty gaps remain.

An artifact inventory is a structured catalog listing all artefacts produced during a workflow run, including provenance and purpose. You need it when requiring an auditable record of data flow and consistency enforcement within a selected scope.

Data flow mapping supports MVP scope by applying guardrails that focus planning on the selected scope and blockers. It ensures the artifact map resolves specified blockers without expanding beyond the defined MVP boundaries.

Generate a data flow map by running the mapper on your selected scope to produce the 03_data_flow_map.json output. This file enforces orphan and missing artifact rules while cataloging all producers, consumers, and purposes.

The workflow planner fails during artifact mapping if consistency enforcement detects non-empty orphan or missing artifact lists. This happens because every artifact must have a defined producer and consumer to pass validation rules.