feat: evidence source provenance (EvidenceMapping) support - #840
Draft
marcusburghardt wants to merge 1 commit into
Draft
feat: evidence source provenance (EvidenceMapping) support#840marcusburghardt wants to merge 1 commit into
marcusburghardt wants to merge 1 commit into
Conversation
Add OpenSpec change artifacts for plumbing the Gemara EvidenceMapping (source field) through complyctl's evidence pipeline. This enables providers to report evidence provenance -- which artifact, location, and content digest each evidence entry was collected from. Artifacts: - proposal.md: motivation and scope - specs/evidence-source/spec.md: behavioral requirements - design.md: technical decisions and approach - tasks.md: implementation checklist Assisted-by: OpenCode (claude-opus-4-6) Signed-off-by: Marcus Burghardt <maburgha@redhat.com>
jpower432
reviewed
Sep 5, 2026
|
|
||
| **Non-Goals:** | ||
|
|
||
| - OSCAL output evidence support (separate concern, no upstream |
Member
There was a problem hiding this comment.
In OSCAL Assessment Results there is an relevant_evidence field under observations. If we are using the upstream conversion (we should be), I submitted an issue to add support gemaraproj/go-gemara#127
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.
Summary
Plumb the Gemara
#EvidenceMapping(sourcefield) through complyctl'sentire evidence pipeline, enabling providers to report where evidence
was collected from.
Context
The Gemara CUE schema (
evaluationlog.cueline 73,auditlog.cuelines 78-97) defines
#Evidencewith asourcefield of type#EvidenceMappingthat records evidence provenance -- which artifact,which location within it, and a content digest. The go-gemara SDK already
exposes this as
Evidence.Source. complyctl's proto API currently defersthis field with a comment referencing an unwritten "ADR 0023".
This PR starts with the OpenSpec change artifacts only (proposal,
specs, design, tasks). Implementation will follow after review.
OpenSpec Artifacts
openspec/changes/evidence-source/proposal.mdopenspec/changes/evidence-source/specs/evidence-source/spec.mdopenspec/changes/evidence-source/design.mdopenspec/changes/evidence-source/tasks.mdScope
EvidenceMappingproto message +sourcefield onEvidenceEvidenceSourceGo type inpkg/provider/sourceare unaffectedRelated