Methasit-Pun Data Reliability, Contracts & Governance (Router)
This is a router skill. It groups the three skills that make data trustworthy: correctness checks, cross-team schema guarantees, and regulatory/access governance. Diagnose which sub-area(s) the task touches, then invoke the matching sub-skill(s) with the Skill tool.
How to route
| If the task is about… | Invoke sub-skill |
|---|---|
| Validation rules, Great Expectations suites, dbt tests, anomaly detection, null/type/range/referential assertions, monitoring bad data in a pipeline | data-quality |
| Formalizing what a dataset promises across team boundaries: field types, nullability, allowed values, versioning, breaking vs. non-breaking changes, schema registries, downstream-impact assessment | data-contracts |
| PII tagging/classification, column-level access control, data catalog metadata, lineage, retention, right-to-erasure, audit logging, PDPA/GDPR/HIPAA compliance | data-governance |
Routing rules
- Quality vs. contracts overlap (both validate schema). Same-owner pipeline correctness →
data-quality. Two teams/services sharing a dataset where upstream keeps breaking downstream →data-contracts. When both apply (a contract enforced by quality tests), invoke both. - Any mention of PII, compliance, audit, or regulation →
data-governanceimmediately, often alongsidedata-quality. - "Small" upstream schema change about to ship →
data-contractsto assess downstream impact before it lands. - Invoke via the Skill tool by name, e.g.
Skill(skill="data-quality"). Combine outputs; don't paraphrase from memory.
Related groups
- Where these checks run in the pipeline → [[data-pipelines]]
- The models being validated → [[data-modeling]]