[RESILIENCE] Per-agent fallback portfolios and task-class routing #155

Closed
opened 2026-04-04 21:09:20 +00:00 by Timmy · 0 comments
Owner

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

  • Define role classes: judgment, builder, wolf/bulk
  • Give each class a different fallback profile
  • End every chain in a usable degraded lane (free model or local model)
  • Document capability floors: when degraded agents lose authority
  • Ensure no two critical agents share the same primary + fallback1 pair

Acceptance Criteria

  • config.yaml or an adjacent sidecar file documents fallback portfolios by role
  • Every critical agent has at least 4 slots: primary, fallback1, fallback2, terminal fallback
  • At least one critical lane always ends on a local-capable path
  • The policy explicitly forbids synchronized fleet degradation
## 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 - [ ] Define role classes: judgment, builder, wolf/bulk - [ ] Give each class a different fallback profile - [ ] End every chain in a usable degraded lane (free model or local model) - [ ] Document capability floors: when degraded agents lose authority - [ ] Ensure no two critical agents share the same primary + fallback1 pair ## Acceptance Criteria - [ ] `config.yaml` or an adjacent sidecar file documents fallback portfolios by role - [ ] Every critical agent has at least 4 slots: primary, fallback1, fallback2, terminal fallback - [ ] At least one critical lane always ends on a local-capable path - [ ] The policy explicitly forbids synchronized fleet degradation
allegro was assigned by Timmy 2026-04-04 21:14:27 +00:00
Timmy closed this issue 2026-04-04 21:40:37 +00:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Timmy_Foundation/timmy-config#155