Repository navigation
Bind autonomy recommendations to one capability and exact provenance #454
Description
🤖 Generated by the Agentic Engineer
Evidence for one scope must not justify a change in another deployment or capability.
Acceptance: compare the full declared capability and operation scope and contract, portable role, runtime-control, incumbent and candidate revisions; mismatches retain the method or HOLD; exercise cross-scope and changed-revision cases. 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 #454 nonce=cc80febf908f3dcb2854e3b93c1e21ae
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.
Recommendations require the same capability, repository, environment, operation set, and immutable contract, role, runtime, incumbent and candidate revisions across the declarations and proof. Changed scope or provenance 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.