recover

Context Recovery

RUN THIS AT SESSION START. The decision graph is your persistent memory.

Step 1: Query the Graph

# See all decisions (look for recent ones and pending status)
deciduous nodes

# Filter by current branch (useful for feature work)
deciduous nodes --branch $(git rev-parse --abbrev-ref HEAD)

# See how decisions connect
deciduous edges

# What commands were recently run?
deciduous commands

# Check for attached documents
deciduous doc list

Branch-scoped context: If working on a feature branch, filter nodes to see only decisions relevant to this branch. Main branch nodes are tagged with [branch: main].

Step 1.5: Audit Graph Integrity

CRITICAL: Check that all nodes are logically connected.

# Find nodes with no incoming edges (potential missing connections)
deciduous edges | cut -d'>' -f2 | cut -d' ' -f2 | sort -u > /tmp/has_parent.txt
deciduous nodes | tail -n+3 | awk '{print $1}' | while read id; do
  grep -q "^$id$" /tmp/has_parent.txt || echo "CHECK: $id"
done

Review each flagged node (flow: goal -> options -> decision -> actions -> outcomes):

• Root goal nodes are VALID without parents
• option nodes MUST link to their parent goal
• decision nodes MUST link from the option(s) being chosen
• action nodes MUST link to their parent decision
• outcome nodes MUST link back to their action

Fix missing connections:

deciduous link <parent_id> <child_id> -r "Retroactive connection - <reason>"

Step 2: Check Git State

git status
git log --oneline -10
git diff --stat

Step 3: Check Session Log

cat git.log | tail -30

After Gathering Context, Report:

1. Current branch and pending changes
2. Branch-specific decisions (filter by branch if on feature branch)
3. Recent decisions (especially pending/active ones)
4. Last actions from git log and command log
5. Open questions or unresolved observations
6. Attached documents - diagrams, specs, or screenshots on key nodes
7. Suggested next steps