Expand description
Data-quality contracts for repairing uncertain source records before automation uses them. Data-quality findings that guard the source-fact → domain → workflow chain.
These contracts keep messy provider facts visible instead of silently normalizing them: blocking issues stop unsafe automation, reviewable issues remain attached to analytics facts and manager briefs, and BI-visible status lets labor-cost reports explain when data hygiene—not actual demand or staffing—is driving an apparent exception.
Structs§
- Issue
- Evidence-backed data-quality issue attached to source records and derived facts.
Enums§
- Field
Path - Semantic path to the source field that produced a data-quality issue.
- Field
Segment - Path segment vocabulary for source fields that can fail validation.
- Kind
- Kind of hygiene defect found while validating source facts.
- Reservation
Field - Reservation fields whose absence or ambiguity can block workflow projections.
- Resolution
Status - Lifecycle state for a data-quality issue as staff acknowledge or repair it.
- Severity
- Severity of a hygiene defect and its effect on read-model or workflow safety.
- Source
Field - Source-ingestion metadata fields needed to preserve provenance and auditability.
- Stay
Field - Stay/read-model fields checked before analytics and labor views trust a record.