feat: add semantic model-evidence projection - #3
Merged
Merged
Conversation
sneakocom
marked this pull request as ready for review
September 7, 2026 00:22
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
1 participant
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.
Problem
The compatible canonical evidence packet includes audit/provenance metadata. A downstream repair consumer needs a supported semantic-only representation rather than silently inventing a second packet shape.
Behavior
Adds
opsle.context-firewall.model-evidence/v1,modelEvidenceForPacket(),serializeModelEvidence(), and the optional--model-evidencesidecar. The projection preserves the packet operation identity and byte-identical decision evidence while excluding the packet receipt. Existing packet stdout, receipt, classification, retention, hashes, and escalation remain compatible.Validation
31159627ef42c748ccafd8dbda5c68ec99b69978.npm run check, 43/43 tests, and all 30 conformance fixtures passed.test: passed at the reviewed head.Limits
The legacy producer measurement still describes canonical packet stdout. Downstream delivery must be measured by the consumer. This PR makes no general model-quality, token, cost, or causal-savings claim.
Dependency order
Merge after Gearbox PR opsle/gearbox#2. The Tasks integration must wait for both dependency PRs.