# ADR-0003: Every dataset carries its own proofs — ledger, fingerprints, quality contract

ADR-0003: Every dataset carries its own proofs — ledger, fingerprints, quality contract — documentation from Algorythmos-AI/sggs-data at the pinned commit c36e317.

- Page: <https://docs.gurbanisoul.com/data/adr/0003-integrity-proofs/>
- Updated: 2026-10-27
- Pinned copy of `Algorythmos-AI/sggs-data` `docs/adr/0003-integrity-proofs.md` at `c36e317`; the canonical file is <https://github.com/Algorythmos-AI/sggs-data/blob/c36e3172bdf38a61070849bb604b38da89ca5d8b/docs/adr/0003-integrity-proofs.md>
- From the Sri Guru Granth Sahib Ji — Knowledge Base wiki. Sri Guru Granth Sahib Ji is quoted verbatim, cited by Ang, and never altered.

---

**Status:** accepted (2026-09-24)

**Context.** The corpus is sacred scripture, extracted verbatim from the source edition. A rebuild,
a tool upgrade or an editor must never change a character unnoticed, and "the same data" must be
provable across SQLite versions and machines.

**Decision.** Four independent proofs gate every change (all required CI checks):
- **Reconcile attestation** — the corpus equals the source PDF character for character; the PDF's
  sha256 is recorded and a different edition is refused without explicit review.
- **Editorial ledger** (`audit/editorial-ledger.jsonl`, `pipeline/ledger_check.py`) — the only
  sanctioned text transforms, each itemised and reviewed; any scripture change without a ledger entry
  fails.
- **Fingerprints** (`pipeline/sggs_integrity.py`, `audit/dataset-fingerprint.json`) — content, not
  bytes: scripture and T0 hashes, every table (build stamps blanked), every FTS index; stable across
  SQLite versions.
- **Data-quality contract** (`pipeline/data_quality.py`, `audit/data-quality-baseline.json`) — shape,
  the `comp_id` gap set (ids are never reused), the heading set, script separation, references, and
  the rows under scholarly review tracked by their exact Gurmukhi.

**Consequences.** A rebuild is either provably identical or its differences are named, reviewed and
recorded. Baselines are re-recorded only in reviewed PRs. Consumers (the platform, the app) pin a
commit and a sha256 and never need to re-prove the text.