---
name: command-recover
description: Recover lost context from audit session records. Use when you can't remember earlier discussion, aren't sure about task progress, or need to check what the user has corrected before. Also use when your answers feel vague — don't guess, recover. Examples: "recover", "what was I doing", "recap", "what did we discuss", "/recover".
allowed-tools:
  - Read
  - Glob
  - Grep
---

# /recover — Context Recovery

## Trigger

```
/recover              # L0+L1+L2 (current session)
/recover full         # L3 (full audit_trail)
/recover {session_id} # Specific session
```

## When to use

**Do not work from memory — query the audit trail when:**
- You can't recall what was decided earlier
- Unsure what phase the task is in
- About to propose something the user may have already corrected
- Answers feel generic (missing file names, specific numbers)

## Graded loading

### L0 — Index (~200t)
Read `.boo/runs/index.json` → last 5 entries (id, task, status)

### L1 — Task state (~500t)
Read `.current_session` → session.json → last 3 audit_trail entries

### L2 — User corrections + decisions (~1000t) ⚠️ MOST IMPORTANT
Scan ALL audit_trails for `user_correction` records + conclusions
Read daily report §4 (anomalies) + §6 (backlog)

### L3 — Full context (~3000t, /recover full only)
Complete audit_trail.jsonl + audit_pending.jsonl

## Output

```
=== Context Recovery Report ===
Level: L2
Source: .boo/runs/{session_id}/

Current task: {description}
Progress: {last action}

USER CORRECTIONS (must follow):
  1. [{time}] {original claim} → {correction}
     Principle: {principle_extracted}

Key conclusions: ...
Unresolved: ...

Source: audit records (not memory)
```
