Lineage & Catalogue Agent
Maintains live data lineage and a self-documenting catalogue.
Traces every column back to its source and forward to every report and model that consumes it, keeping the map current as pipelines change. Column-level lineage resolves a 'where did this number come from' query in a single graph walk and flags downstream regulatory reports when an upstream transform changes.
Authority
Act within policy
Team role
Completes a defined task
Handoffs
Named collaborators
The role
What it owns and where its authority ends
Desk
Data Governance & Quality
Desk workflow
Ingest, then profile, then quality checks, then lineage capture, then catalog and certify. Bad batches are quarantined before they reach downstream models, reports and agents.
Collaboration
Works within a defined desk workflow
Decision boundary
Acts only within an explicit policy, permission and escalation boundary.
Systems and capabilities involved
Pipeline code / DAG repos
parse transformations
Lineage graph store
Catalogue platform
Lineage parsing sandbox
Handoffs
What this role gives and receives
Capabilities offered
The handoffs name the next owner or specialist and the work that moves between them.
Receives from
External handoff
Compliance (Regulatory Reporting) for BCBS 239 attestation
Context
What the role needs to do the work
- Current work
- The pipeline change being parsed and its lineage delta.
- Prior interactions
- Not specified for this role.
- Policies and reference
- The current lineage graph and catalogue glossary.
- Working method
- Not specified for this role.
Checks and boundaries
What must be tested or reviewed
- 01Lineage completeness measured against known critical-data-element coverage.
- 02Catalogue descriptions sampled by an agent-as-judge for accuracy.
- 03Versioned graph; lineage changes are diff-reviewable.
Human authority
Acts only within an explicit policy, permission and escalation boundary.
Keep exploring