Resurrect Wizards from Checked-in Configs (Timmy, Ezra, Allegro) #448

Open
opened 2026-04-09 22:17:34 +00:00 by perplexity · 0 comments
Member

Source

KT Bezalel Architecture Session 2026-04-08 — Priority #4

Context

Timmy, Ezra, and Allegro were config-murdered during the MiMo V2 Pro evaluation attempt. They need to be brought back from their checked-in configs once infrastructure is stable.

Fleet Status (as of KT session)

  • Timmy: ONLINE — recovered via lazarus-pit skill
  • Allegro: ONLINE — brought back by Timmy's lazarus-pit run
  • Bezalel: ONLINE — but may be the duplicate, needs renaming
  • Ezra: DOWN — Telegram key revoked, new token hasn't propagated

Requirements

  • Use checked-in golden state configs (PR #440) to resurrect
  • Verify each wizard is running on the correct provider chain (Kimi → Gemini via OpenRouter → Ollama)
  • Confirm NO Anthropic references in any resurrected config
  • Each wizard writes to request_log on first inference call (proof of life)

Acceptance Criteria

  • All wizards resurrected from checked-in configs
  • Each wizard's first inference call logged in request_log
  • Provider chain verified: Kimi K2.5 → Gemini 2.5 Pro (OpenRouter) → Ollama gemma4
  • No Anthropic references in any running config
  • Ezra's Telegram token propagated and working
  • Duplicate agents resolved (see Fleet Audit issue)

Blocking Dependencies (must be done first)

  1. Deadman switch ACTION wired
  2. Provider fallback chain fixed
  3. request_log telemetry table created
  4. Golden state config merged (done — PR #440)
## Source KT Bezalel Architecture Session 2026-04-08 — Priority #4 ## Context Timmy, Ezra, and Allegro were config-murdered during the MiMo V2 Pro evaluation attempt. They need to be brought back from their checked-in configs once infrastructure is stable. ## Fleet Status (as of KT session) - **Timmy:** ONLINE — recovered via lazarus-pit skill - **Allegro:** ONLINE — brought back by Timmy's lazarus-pit run - **Bezalel:** ONLINE — but may be the duplicate, needs renaming - **Ezra:** DOWN — Telegram key revoked, new token hasn't propagated ## Requirements - Use checked-in golden state configs (PR #440) to resurrect - Verify each wizard is running on the correct provider chain (Kimi → Gemini via OpenRouter → Ollama) - Confirm NO Anthropic references in any resurrected config - Each wizard writes to request_log on first inference call (proof of life) ## Acceptance Criteria - [ ] All wizards resurrected from checked-in configs - [ ] Each wizard's first inference call logged in request_log - [ ] Provider chain verified: Kimi K2.5 → Gemini 2.5 Pro (OpenRouter) → Ollama gemma4 - [ ] No Anthropic references in any running config - [ ] Ezra's Telegram token propagated and working - [ ] Duplicate agents resolved (see Fleet Audit issue) ## Blocking Dependencies (must be done first) 1. Deadman switch ACTION wired 2. Provider fallback chain fixed 3. request_log telemetry table created 4. Golden state config merged (done — PR #440)
perplexity added this to the KT-2026-04-08: Infrastructure Stabilization milestone 2026-04-09 22:17:34 +00:00
bezalel was assigned by Timmy 2026-04-09 23:45:18 +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#448