Data Quality & Audit Governance
How ConservaNode guarantees data integrity, prevents hallucinations, enforces legal compliance, and maintains a cryptographic chain of custody.
1. Pre-Release Quality Gates (7/7 Verified)
Before any dataset or site export is released, it must pass 7 automated gates without exception:
| Gate Check | Requirement | Status |
|---|---|---|
| 1. Live Database Auditor | 0 HIGH findings across 9 adversarial automated checks. | PASS |
| 2. Stand-alone Release Verifier | Independent verification script confirms file hashes and ledger integrity. | PASS |
| 3. Person Scrubber Audit | Zero personal names detected across every CSV cell, JSON-LD, and HTML text node. | PASS |
| 4. No-Quote Leakage Check | Zero quote columns and zero verbatim evidence quote text leaked into exported data. | PASS |
| 5. Clean Source & Split Scope | Zero heldout or test-fixture documents included in release output. | PASS |
| 6. Quarantine Consistency | Zero quarantined entities or edges present in exported graph. | PASS |
| 7. Deterministic Re-Export | Rebuilding the export produces 100% byte-for-byte identical SHA-256 hashes. | PASS |
2. The Append-Only Audit Ledger
Every ingested document and extraction status is recorded in a PostgreSQL append-only ledger protected by database triggers that forbid UPDATE, DELETE, or TRUNCATE operations. Each ledger entry is linked to its predecessor by an unbroken SHA-256 hash chain:
record_hash = SHA-256(prev_hash || source_url || timestamp || file_hash || status || model_id || prompt_version)Any retroactive modification to an ingested record or timestamp breaks the cryptographic hash chain, immediately alerting the auditor agent.
3. Offline Site Quality Gates
The static site generator is subjected to its own dedicated suite of quality checks:
- Link Integrity: 100% of internal links, images, stylesheets, and anchor fragments resolve to valid targets.
- Zero External Resource Requests: No third-party scripts, stylesheets, web fonts, tracking pixels, or remote CDNs.
- Strict Content Security Policy: All styles and scripts are isolated in standalone files; zero inline scripts, styles, or event handlers.
- Full Offline Compatibility: All navigation paths and resources use relative paths, functioning seamlessly when loaded directly via
file://URLs.