Define durable data and future provenance safety gates - #29
Merged
Conversation
Contributor
There was a problem hiding this comment.
Pull request overview
This PR formalizes CalorieApp’s “durable data before public onboarding” foundation and reserves a disabled-by-default, privacy-preserving XRPL transaction-linking/provenance seam via machine-readable contracts and contract tests.
Changes:
- Update public-facing docs to state SQLite is local/test only and public onboarding is blocked until PostgreSQL durability gates pass.
- Add machine-readable data-safety and provenance contract JSON (plus supporting documentation) that defines release gates and XRPL/provenance boundaries.
- Add backend contract tests to prevent identifier/name drift for the new contract IDs and required gate semantics.
Reviewed changes
Copilot reviewed 15 out of 15 changed files in this pull request and generated 4 comments.
Show a summary per file
| File | Description |
|---|---|
| README.md | Updates top-level architecture/docs links to reflect durable-data gating + provenance contract docs. |
| docs/XRPL_TRANSACTION_LINKING.md | Adds detailed, disabled-by-default XRPL transaction-linking architecture boundary doc. |
| docs/public/xrpl-linking.md | Adds public-facing summary of the voluntary XRPL reference direction. |
| docs/public/release-readiness.md | Extends release readiness checklist with durable PostgreSQL / migration / backup / export / deletion gates. |
| docs/public/data-safety.md | Adds public data-safety direction page describing durable storage and privacy boundaries. |
| docs/public/architecture.md | Adds explicit SQLite vs PostgreSQL public onboarding gating note. |
| docs/DURABLE_DATA_FOUNDATION.md | Adds DS-1 durable data & privacy foundation architecture contract and implementation order. |
| contracts/provenance/v1/traceability.json | Introduces provenance contract (architecture-only) describing XRPL anchor pairing and traceability layers. |
| contracts/provenance/v1/README.md | Adds short readme describing provenance contract scope/boundary. |
| contracts/data-safety/v1/release-test-matrix.json | Adds auditable matrix of release-blocking durable-data gates and status/evidence pointers. |
| contracts/data-safety/v1/README.md | Adds readme describing the data-safety contract purpose and status vocabulary. |
| contracts/data-safety/v1/data-safety.json | Adds durable data-safety contract defining architecture, data classes, retention, and XRPL linking boundaries. |
| backend/tests/test_provenance_contract.py | Adds contract tests to enforce provenance contract IDs and safety boundaries. |
| backend/tests/test_data_safety_contract.py | Adds contract tests to enforce durable-data safety gates and XRPL boundary invariants. |
| backend/README.md | Aligns backend readme wording with SQLite-local-only and durable-data gating. |
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Doel
Legt de duurzame-datafundering vast vóór publieke onboarding en bereidt een optionele XRPL/CalorieDB-herkomstlaag voor zonder extra kernplatformen toe te voegen.
Inhoud
(XRPL network + validated transaction hash) ↔ calorie_anchor_hash, met een visibility-filtered provenance-DAG daaronder.contract_id-waarden tegen naamdrift.Niet in deze PR
Actuele gecontroleerde stand
mainop6976822baa6aa53f5483eee74d46c5b8d3ab479b.fd25ee73143dacc1500f789b7a36d877c9171f82.357ef5df441a17d45b8ffc3f841dd53bd3bc8205.main: 15 verklaarde tekstbestanden,+1259/-3; geen runtime-, dependency-, lockfile-, binary- of UI-wijziging.3ec5d63b0e98b5e54b1ebf5055241afa5f3161beheeft geordende parents oude PR-head8b4ea22enmain=6976822.c25a76eheeft parent3ec5d63en treeb02ceed; hij activeerde CI na retargeting zonder bestandswijziging.fd25ee7heeft parentc25a76een wijzigt uitsluitend de vier door Copilot aangewezen bestanden.Controle
Lokale reviewfixkandidaat:
pytest.release-check.ps1is niet in de commit opgenomen.Exact-head GitHub CI:
fd25ee7: volledig geslaagd.Review:
fd25ee7adresseert alle vier; alle vier threads staan opgelost en er zijn geen onopgeloste reviewthreads.Deze PR is Ready for human review. Er is niets gemerged, gedeployed of gepubliceerd.