realitycheck-validate

To validate referential integrity after data additions, run a validation script that verifies all source IDs reference existing records. This enforces schema conformance and detects invalid IDs, missing embeddings, and duplicates before committing changes.

The best way to check schema conformance in a CI workflow is to integrate a validation script that runs before commits. This enforces schema rules, verifies ID formats, and detects missing embeddings and duplicates to maintain database consistency automatically.

Duplicate detection during data consistency validation works by scanning database records to identify redundant entries. Along with checking for missing embeddings and invalid IDs, this process ensures claims, sources, and chains maintain strict referential integrity.

Yes, you can run data integrity checks during local development before committing. By executing a validation script locally, you enforce schema conformance, verify ID formats, and detect duplicates or missing embeddings before changes propagate to the main database.

Database validation fails with missing embeddings because the consistency verification process requires embeddings to be present for all records. This check is enforced alongside schema conformance and referential integrity to ensure complete data quality across claims and sources.