Repository navigation
test(p8-a3.1): prototype typed evidence report at internal boundary - #150
Merged
aetherxeg-source merged 7 commits intoOct 4, 2026
Merged
Conversation
This was referenced Oct 4, 2026
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.
Purpose
Execute R0-R3 of #149 as a test-only research prototype.
Design
The prototype is compiled only under
cfg(test)and consumes the internalBackendObservationboundary directly, before the public raw-v2 return path discards typed collection-health information.It emits a deterministic research report containing only already-known metadata:
Non-expansion boundary
No new acquisition is added. The prototype does not collect or claim:
No public CLI, Action, baseline, policy, verdict, or raw-v2 schema is changed.
Tests
R0-R3 cover deterministic output, incomplete/ambiguous health, unsupported capability, laundering attacks, backend-name inflation, missing capability, process binding, repeated effects, profile mismatch, and a live Linux x86_64 native ptrace write path.
R4 remains full CI + P9.3 compatibility before any R5 decision.