Repository navigation
Recommend scoped recovery when autonomy proof loses support #457
Description
🤖 Generated by the Agentic Engineer
A scoped failure, protected-outcome regression or expired proof needs an actionable recovery recommendation without an unauthorized rollback.
Acceptance: recommend only the consumer-declared fallback with matching scope and revision, fresh tested recovery and a separate authorization reference; preserve known failures after expiry; unresolved recovery HOLDs with an owner action; perform no mutation. 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 #457 nonce=94358f7765e6e224f3c1739d87cb285b
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.
Bound failures remain negative after expiry. Contraction recommends only the declared incumbent with matching scope/control revision, fresh recovery testing and a reported existing authorization reference; incomplete recovery holds with an owner.
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.