feat(evidence): verify persisted deletion inventory commitments - #155
Draft
seonghobae wants to merge 31 commits into
Draft
Conversation
|
Important Review skippedDraft detected. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
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.
Partial implementation of #10, stacked on exact PR #140 head
959aab2c23e38f33fa355de8d832defc39118364.Buyer/audit gap
PR #140 emits a deterministic credential-free commitment after exact sensitive-data deletion receipt-set verification. A durable evidence owner also needs a bounded versioned representation that can be reconstructed and reverified against the externally expected request scope and exact declared-copy inventory without duplicating OriginWeave's private canonicalization logic.
Live dependency alignment
The previous branch targeted stale #140 head
de243e7ed6e60b57f7ab5b42d6c0b8f3a6a89a99. Content-aware merge headf2dc2bf48ffbcd4b6b887003eee060e5ae7a5699now uses the exact current parent tree and overlays only this lane's seven unique production/test paths. Fresh ancestry is ahead 29 / behind 0 with merge base exactly959aab2c23e38f33fa355de8d832defc39118364; the diff remains those seven paths. No force push or destructive rebase was used.Implemented contract
The current branch provides:
SensitiveDeletionPersistedCommitmentInputfor reconstructing persisted credential-free scope, declared-copy count, digest, and explicit version metadata;u16persisted copy counts and architecture-independent canonical wire representation;1, rejected fail-closed when unsupported;Public boundaries retain useful rustdoc and deterministic credential-safe standard Rust errors, preserving enclosed structural errors as sources only where applicable.
Exact-current proof
On unchanged exact head
f2dc2bf48ffbcd4b6b887003eee060e5ae7a5699against exact live base959aab2c23e38f33fa355de8d832defc39118364:31940835206: success;Rust contracts: repository contracts, canonical formatting, locked workspace/all-target checks, full tests, strict Clippy, and rustdoc success under Rust 1.97.1;Production coverage: exact owned production function/line/region/branch enforcement success;Security/SAST/central/model workflows not returned for this stacked Draft are not represented as passing. No predecessor-head, prerequisite-head, queued, pending, skipped, cancelled, absent, stale, synthetic, status-only, or model-only evidence is promoted to current-head proof.
Truth boundary
This proves deterministic structural consistency between one versioned loaded commitment, the externally expected scope, and one exact caller-supplied declared inventory. The durable envelope authenticates nothing by itself: it does not authenticate the persistence owner, sign or persist evidence, discover undeclared copies, prove inventory exhaustiveness or deletion, enforce retention/legal hold, prevent replacement by an attacker controlling both commitment and declared inventory, or replace storage-layer integrity/access controls.
Keep Draft while #140 and its prerequisites remain active. The scheduled actor does not merge or self-approve.