feat(evidence): bind WARC records to PROV JSON-LD - #217
Conversation
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. 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 |
|
Exact-head maintenance note for |
|
Current-head audit for |
66f360c
into
feat/warc-resource-record-contract
Partial implementation of #199, stacked on the exact current PR #210 head.
Buyer-visible boundary
This Draft implements the next evidence-native replay boundary after schema admission and immutable WARC resource records: a bounded deterministic W3C PROV-O JSON-LD bundle that binds one already-validated WARC record to its verified source entity, one capture activity, the exact OriginWeave software revision, explicit WARC payload-completeness state, the retained payload block digest, and a SHA-256 digest of the complete deterministic WARC serialization. Raw WARC payload bytes are not embedded in the provenance document.
The in-memory bundle exposes deterministic offline verification against a candidate validated
WarcResourceRecord. Verification binds the complete validatedProvenanceRecordtogether with WARC identity, capture time, payload digest, completeness state, and serialized-record digest. This is evidence identity checking only; it does not authenticate an actor or establish factual correctness.Exact-current state and evidence
bea65643109449d63d367a35b8d9bf327ee7cb2c;6b8a3fdeae52ad94b90086bbc9b42863b90c9614;Same-head centralized SAST/Semgrep, Security Scan, OpenCode, Noema, Strix, browser, persistence, retention, and independent-review evidence are not claimed until they actually run for this head.
Authority boundary
The bundle is an immutable, payload-free provenance projection. It grants no capture, browser, network, model, secret, persistence, retention, deletion, export, signing, or release authority. Durable storage and replay policy remain outside this in-memory boundary.