[RESILIENCE] Per-agent fallback portfolios and task-class routing #155
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Parent: #154
What
Import the strongest resilience pattern from POI Command: every agent gets an explicit fallback portfolio, but not the same one. Critical agents must degrade without converging onto the same stupid chain.
Tasks
Acceptance Criteria
config.yamlor an adjacent sidecar file documents fallback portfolios by role