Troubleshooting The Fold

Quick Fixes

Check daemon status

./fold --status

Daemon won't start

./daemon.sh stop     # Clear stale state
./daemon.sh cleanup  # Kill orphan workers
./daemon.sh start    # Or just run ./fold - it auto-starts

Session state corruption

rm -rf .fold-repl/   # Nuclear option - clears all session state
./fold "(help)"      # Auto-starts fresh daemon

Tests hanging

Check fuel consumption. Infinite loops exhaust fuel and return out-of-fuel error.

;; In REPL, check fuel status
(fuel)

File Locations

REPL Infrastructure

Persistent State

Content-Addressed Store

BBS Runtime

Project Files

Common Issues

"Daemon not responding"

1. Check if daemon is running: ./fold --status
2. Check daemon log: cat .fold-repl/daemon.log
3. Kill and restart: ./daemon.sh stop && ./fold --status

"Session not found"

Sessions are ephemeral unless named with -s:

./fold -s mywork "(define x 10)"  # Creates named session
./fold -s mywork "x"              # Uses same session

"Module not found" during require

1. Check you're in project root: pwd should be /home/oso/the-fold
2. Verify module exists: ls lattice/<module>/
3. Check for typos in module name

"Out of fuel" error

The expression exceeded its fuel budget. Options:

• Simplify the expression
• Check for infinite recursion
• Increase fuel budget (if safe)

"Hash mismatch" or CAS errors

The CAS store may be corrupted. Options:

1. Check .store/ permissions
2. Run integrity check: ./fold "(cas-verify)"
3. Rebuild from git: rm -rf .store && ./fold "(cas-rebuild)"

BBS shows stale data

After reloading modules, refresh BBS state:

(bbs-init!)  ; Refresh from disk