[GH-ISSUE #21] Add evidence envelopes, artifact hashes, and reproducible exports #13

Closed
opened 2026-10-15 18:19:56 +00:00 by bsakaguchi · 2 comments
Owner

Originally created by @morluto on GitHub (Jul 12, 2026).
Original GitHub issue: https://github.com/morluto/rea/issues/21

Problem

Results lack a uniform record of artifact identity, provider version, parameters, confidence, limitations, and evidence locations.

Scope

Add artifact SHA-256/format/architecture, provider identity/version, parsed parameters, raw and normalized results, observed/derived/inferred confidence, limitations, source locations, stable evidence IDs, investigation manifests, and JSON evidence export.

Acceptance criteria

  • Every workflow can emit evidence.
  • Unchanged artifacts have stable identity.
  • Reports cite evidence IDs and locations.
  • Secrets and arbitrary environment values never enter evidence.

Roadmap expansion

This remains the evidence/provenance epic.

Child work

Evidence IDs are computed from canonical JSON with recursively sorted object keys and stable array order. Local paths and the ID itself do not affect identity. Records distinguish raw and normalized results, observed/derived/inferred confidence, authority, environment, limitations, and typed locations. Import recomputes IDs and rejects tampering and conflicting duplicates. Evidence v2 is intentionally breaking.

Originally created by @morluto on GitHub (Jul 12, 2026). Original GitHub issue: https://github.com/morluto/rea/issues/21 ## Problem Results lack a uniform record of artifact identity, provider version, parameters, confidence, limitations, and evidence locations. ## Scope Add artifact SHA-256/format/architecture, provider identity/version, parsed parameters, raw and normalized results, observed/derived/inferred confidence, limitations, source locations, stable evidence IDs, investigation manifests, and JSON evidence export. ## Acceptance criteria - Every workflow can emit evidence. - Unchanged artifacts have stable identity. - Reports cite evidence IDs and locations. - Secrets and arbitrary environment values never enter evidence. ## Roadmap expansion This remains the evidence/provenance epic. ### Child work - [x] #49 - [x] #50 - [x] #51 - [x] #72 - [x] #73 Evidence IDs are computed from canonical JSON with recursively sorted object keys and stable array order. Local paths and the ID itself do not affect identity. Records distinguish raw and normalized results, observed/derived/inferred confidence, authority, environment, limitations, and typed locations. Import recomputes IDs and rejects tampering and conflicting duplicates. Evidence v2 is intentionally breaking.
Author
Owner

@morluto commented on GitHub (Jul 17, 2026):

Completed on current . Evidence v2 now has canonical evidence/domain records and IDs, a ledger and bundle file/command application layer, MCP evidence tools/resources, canonical export, and import validation for tamper/conflict cases (, , , and the evidence test suites). Follow-on workflow refinements remain independently tracked.

<!-- gh-comment-id:5001516913 --> @morluto commented on GitHub (Jul 17, 2026): Completed on current . Evidence v2 now has canonical evidence/domain records and IDs, a ledger and bundle file/command application layer, MCP evidence tools/resources, canonical export, and import validation for tamper/conflict cases (, , , and the evidence test suites). Follow-on workflow refinements remain independently tracked.
Author
Owner

@morluto commented on GitHub (Jul 17, 2026):

Correction to the preceding comment: completed on current main. Evidence v2 includes src/domain/evidence.ts and evidenceBundle.ts; the EvidenceLedger, EvidenceBundleFiles, and EvidenceBundleCommands application layer; MCP evidence tools and resources; canonical export; and tamper/conflict import validation in the evidence test suites.

<!-- gh-comment-id:5001526614 --> @morluto commented on GitHub (Jul 17, 2026): Correction to the preceding comment: completed on current main. Evidence v2 includes src/domain/evidence.ts and evidenceBundle.ts; the EvidenceLedger, EvidenceBundleFiles, and EvidenceBundleCommands application layer; MCP evidence tools and resources; canonical export; and tamper/conflict import validation in the evidence test suites.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
morluto/rea#13
No description provided.