arch-lens-data-lineage

Data lineage maps information flow by tracing data origins, transformations, and storage locations to identify the single source of truth. It produces a clear diagram showing read and write paths across data-centric pipelines.

To visualize data flow with a mermaid diagram, this Skill requires a frontmatter-defined system description to generate a diagram mapping inputs, transformations, and storage destinations. It outputs a visual representation of read and write paths.

Yes, you can document data provenance and read/write paths for compliance by mapping where data elements originate and how they are stored. This lineage diagram supports provenance, compliance, and impact analysis.

The best way to trace data origins through transformation pipelines is to map inputs, transformations, and storage destinations in a data lineage diagram. This approach clearly identifies where data originates and highlights potential bottlenecks.

Yes, you need a frontmatter-defined system description to generate a data lineage diagram. This input is required to map the information flow and produce a mermaid-based diagram showing read/write paths.

You should not use a data lineage diagram when your project lacks a clear system description or when you need detailed schema analysis rather than information flow mapping. This Skill focuses on high-level provenance and storage tracking.