Asteria Fleet Data Quality Hub
Certify data-quality records served by a shared REST API. Tasks always supply
a runtime base URL in environment_access.md. Every certification follows the
same pipeline:
- Discover the target collection and schema via
GET /api/catalog/collectionsandGET /api/catalog/schema. - Reconcile sources via
GET /api/source-snapshots. The-certifiedsnapshot is always the authoritative source;-provisionalsnapshots are supplementary. - Load records via the domain endpoint and via
POST /api/queryfor filtered or aggregated data. - Classify every logical record. Quarantined records are excluded from normalized totals; mismatches remain in totals but are flagged.
- Assign opaque control codes (IC-, FP-, OR-, RB-, SB-, LD-, MS-, HR-) from the code families documented in code_families.md.
- Apply certification gates from the case scope. Common outcomes:
PASS/RELEASE,PASS_WITH_EXCEPTIONS/REVIEW_EXCEPTIONS,HOLD/BLOCK_AND_REMEDIATE. - Produce JSON matching the supplied answer template. Follow every ordering rule. Use only stable IDs present in the API responses.
Snapshot reconciliation
- The
-certifiedsnapshot is always authoritative; retain its copy when a record appears in both snapshots. - Raw row count = sum across all snapshots. Logical count = after deduplication. Duplicate count = raw minus logical.
- Report the certified snapshot ID in every
authoritative_snapshot_idfield.
Numeric precision
- Currency (USD), volume (L), weight (KG), distance (KM): 2 decimal places.
- Rates (quarantine_rate): 4 decimal places.
- Counts: exact integers. Phone: digits-only. Email: Unicode NFKC lowercase.
References
- api.md — Endpoint reference, response shapes, query syntax.
- code_families.md — All opaque control codes.
- workflow.md — Domain-specific rules and gates.