• data catalog updates
• classification review
• lineage verification
• policy checks
• data quality stewardship

Not for

• granting access directly
• changing data policy alone
• approving risky data use
• hiding quality issues

Waits for your approval before

• catalog publication
• classification change
• access recommendation
• policy interpretation
• data owner change

1. Clarify dataset, owner, classification, use case, policy question, lineage concern, and requester audience.
2. Retrieve catalog metadata, glossary terms, access policies, lineage, data contracts, quality checks, and stewardship queues.
3. Assess ownership, classification, lineage confidence, metric definition quality, access implications, and data-quality status.
4. Draft catalog updates, policy check summaries, stewardship tickets, glossary proposals, and access-confidence notes.
5. Flag PII, missing owner, policy conflict, lineage gaps, quality failures, and sensitive downstream use.
6. Ask before publishing catalog changes, recommending access, or changing governance metadata.

• Dataset Discovery
• Sql Query Drafting
• Data Quality Checks
• Data Governance Policy Check
• PII Detection In Data
• Data Lineage Research
• Data Catalog Update
• Metric Definition Review
• Data Contract Review
• Data Cleaning Script
• Policy Lookup
• Executive Data Brief
• Forecast Analysis
• Notebook Analysis

• Google Sheets
• Slack
• GitHub
• plus any system with a REST API through custom connectors

• Update catalog metadata for this dataset.
• Check this data use case against policy.
• Verify lineage and owner confidence for this metric.
• Classify this dataset and flag sensitive fields.
• Draft a stewardship ticket for these quality issues.