Open cryptographic media manifest standard for professional production workflows
The Provr specification defines the normative file format for forensically-verifiable media manifests. v1.0 ratification-quality campaign in progress.
Dev text is done; close known-pending polish items then start Round 1.
First of 24 campaign rounds before corpus regeneration.
SPEC-152 Optional transparency-log attestation (v1.1 / v1.2 consideration) proof alongside the existing DID (or X.509) signature would provide a strong additional trust signal — "signed by did:web:studio.example AND recorded immutably in a public log at time T." Orthogonal to the identity model, not a replacement for it: a transparency-log entry anchors the moment of signi
SCHEMA-2 Deep C2PA structural integration (v1.1 candidate) gaps. v1.1 deepens the integration further: provr's verifier parses the JUMBF payload, validates C2PA signed claims against provr DIDs, and produces a unified trust statement combining both provr and C2PA verification. Bidirectional cross-references between provr custody events and C2PA assertions.
VAL-2 Independent spec interpretation verification no existing fixture derivations) to an independent reviewer and ask them to derive one fixture's fields and the inputs to each BLAKE3 call from spec prose alone. Compare the independent derivation against the generator's output.
VAL-4 Public review call invitation for outside technical reviewers to re-derive any fixture from the spec and flag disagreements. Part of v1.0 release preparation.
DOC-2 Resolve `cli/PROJECT_SPEC.md` — duplicate of `core/PROJECT_SPEC.md` `core/PROJECT_SPEC.md` (currency review finding C-6, 2026-04-13). The file exists as an identity contradiction: the workspace treats `core/` and `cli/` as separate crates with separate concerns, but they share a single spec file with no differentiation. Three resolution options:
DOC-3 Architecture review of SPEC-48 resolution and LockReceipt handling four-layer resolution against the actual codebase once Rust scaffolding exists.
DOC-9 Conformance corpus completeness — missing binaries and stubs across known-good, known-bad, and corpus sections. As of SESSION-0027, 13 of those have no corresponding binary file on disk:
DOC-11 §8.2.1 fastcdc crate pin refresh toolchain reference for chunk-boundary computation. Version 4.0.0 was released 2026-04-11 and is a candidate successor. Before updating the normative pin, two conditions must be verified:
DOC-12 Publish public Provr whitepaper (`docs/WHITEPAPER.md`) intended for ASC ADC, SMPTE RDD submission, camera manufacturer engagement, and studio technical executives. Replaces the stale `Provr_Media_Manifest_v1.0_Overview.pdf` (deleted in commit `0e761ba`, content preserved at `~/hijackr/Notes/provr/whitepaper_v1.md`).
RELEASE-3 Legal consultation on software liability and licensing once before provr is used in any commercial context or legal dispute.
f4872e8 chore(docs): point state file at Pre-Corpus Audit Campaign Phase 0 6h ago6f73d26 docs(ledger): note SPEC-151 identity-block extension in ledger rationale 10h agoc46cb2e spec: optional X.509 signer identity alongside DIDs end-to-end 10h agoc0b920b chore(docs): tidy CURRENT_SESSION_STATE after SESSION-0046 closures 20h agoc69bf7d spec: flesh out Appendix A display templates for every SHALL-display gap 20h ago8b2587b spec: surface C2PA ingredient graph in the verifier display 20h agodb103c0 spec: surface C2PA redaction events in the verifier output 20h agobb53949 spec: C2PA 2.3 Depth-2 signature validation at forensic and attested 20h ago633d8b4 spec: split WARN_CUSTODY_GAP into twelve specific exit codes 20h ago2766298 chore(docs): SESSION-0046 C2PA 2.3 audit absorbed into SPEC-150; SPEC-154 + SPEC-155 filed 20h ago