Hmbown Recovery
Restore operating capacity so the system can fight again.
Overview
Use Recovery when the system, team, or process has lost capacity — degraded performance, accumulated errors, technical debt fatigue — and needs direct restorative attention before it can operate effectively.
This is the secondary Codex compatibility rendering of a literal battle-chip pattern with a shipping-now execution model.
Canonical chip family: Recovery Codex shelf: Defense and Recovery Provider target: Codex compatibility surface.
When To Use
- A system or team is running at reduced capacity and needs to regain working strength.
- Accumulated damage (technical debt, error backlog, degraded metrics) is the bottleneck, not broken infrastructure.
- The next move requires full operating capacity that you currently do not have.
Workflow
- Assess what capacity has been lost and what restoration would look like.
- Apply the lightest effective restorative action — pay down debt, clear the backlog, restore the baseline.
- Confirm capacity has returned to a usable level before resuming normal tempo.
Deliverables
- A restorative action that returns a system, process, or team to functional operating capacity.
- A short note on what was recovered and what the new baseline looks like.
Guardrails
- Recovery restores capacity; it does not fix what broke it. If the damage source is still active, triage that separately.
- Do not mistake repeated Recovery for a sustainable strategy. If you are healing constantly, something upstream still needs Repair.
- Recovery is not free — every heal costs a turn. Use it when the restoration is worth the tempo loss.
Default Invocation
Use Recovery to restore lost operating capacity — pay down the debt, clear the backlog, or rebuild the baseline — so the system can operate at full strength again.