What problem does it solve? Completed OSINT investigation packages need a verifiable integrity record so reviewers can detect later tampering, but manually tracking hashes of findings, fact-checks, and reports is error-prone and not portable. ## Core Features & Use Cases - Immutable Provenance Manifests: Generates content-addressed manifest revisions covering summary.md, findings.json, fact-check.json, evidence bundles, and review artifacts, with input-set hashes and parent revision links. - Staleness Detection: A --check-current mode verifies that case inputs have not changed since the manifest was built and marks stale pointers. - Optional Noosphere C2PA Signing: Hands the manifest to a local Noosphere signer endpoint and stores immutable, deduplicated signing receipts and failure records. - Use Case: After a Spotlight case passes its readiness gate, run the build script to produce a signed provenance package proving the review.html and verification trail have not been altered since delivery. ## Quick Start Run the provenance manifest build script against the case directory to create an unsigned manifest, then optionally pass a Noosphere signing endpoint and credential ID to sign the review artifact.
