Repository navigation
Check complete reported runtime enforcement coverage #456
Description
🤖 Generated by the Agentic Engineer
A positive-only runtime test does not establish that disallowed execution was intercepted across the declared paths.
Acceptance: require both positive and intercepted-negative reports tied to the same runtime control revision and covering all declared paths; missing/unknown/unsupported reports HOLD; every output labels those reports unauthenticated. Size: M.
Part of #223.
Metadata
Metadata
Assignees
Type
Fields
Priority
None yet
Start date
None yet
Target date
None yet
Effort
None yet
Projects
- Status
Activity
chore: agent-claim #456 nonce=9f59dd8304315c4ce77f5ec8c681f7cb
devantler commentedon Oct 4, 2026
Delivered through PR #462, merged as 89ec0f1. Fresh fetch and an isolated main checkout confirmed HEAD equals origin/main; the Go assessment suite, independently copied installed consumer and manifest validation all pass on that commit.
Both positive and intercepted-negative runtime reports must bind the declared controls and independently cover every declared path. Missing, unknown, foreign or incomplete coverage holds.
All outputs remain assessment-only: executionAdmitted, mutationPerformed and reportedEvidenceAuthenticated are false. These are offline reported-fact assessments, not authenticated native enforcement. Parent #223 remains open for that integration.