Vibe Coding System — How We Stay Organized

The 6 Systems

1. Pre-Session Commit

Before any AI session writes code, it saves what's there first.

git add -A && git commit -m "pre-session save"

If anything breaks, you can undo everything with git checkout .

Where: Rule in CLAUDE.md (both projects)

2. Change Log

Running record of every meaningful change — bug fixes, features, config changes, deploys. Updated automatically after every session where code was changed.

• Only logs real changes, not chat-only sessions
• One-liner per change with the file(s) modified
• Organized by date and project

Where: /home/ubuntu/edgeclaw/docs/changelog.md (on dashboard)

3. Branch Workflow

Small fixes go straight to master (pre-session commit is the safety net). Big or risky changes get a branch first:

• Building a whole new feature or desk
• Rewriting an existing system
• Touching many files at once
• Anything that could break production

git checkout -b descriptive-branch-name    # create branch
# ... do the work ...
git checkout master && git merge descriptive-branch-name   # merge if it worked
git branch -D descriptive-branch-name      # delete if it failed

Where: Rule in CLAUDE.md (both projects)

4. Pre-Flight Checklist

Runs automatically after every EdgeClaw restart. Checks:

• Health endpoint responds
• No fatal errors in startup logs
• Critical cron jobs registered (edge-scanner, sports-stats, player-props, gamesim)
• No data sources in error status (skips ToDo desks)

Sends a Telegram alert: green (all clear), yellow (warnings), or red (failed).

Claude Code also runs manual checks after every restart and reports results.

Where:

• Script: /home/ubuntu/edgeclaw/scripts/post-restart-check.sh
• Service: edgeclaw-preflight.service (runs after edgeclaw.service)
• Rule in CLAUDE.md

5. Session Summary

At the end of every work session, Claude replaces SESSION_STATE.md with a fresh snapshot:

• What we worked on
• What's done
• What's in progress or broken
• What the next step should be

Replaces, doesn't append. Always a snapshot of right now. The change log handles history.

Where: Rule in CLAUDE.md (both projects)

6. Health Monitor (Automated Tests)

Runs every 4 hours (6AM/10AM/2PM/6PM/10PM ET). Watches the system even when nobody's looking. Checks:

• Health endpoint responds
• No data sources in error status
• No sources overdue by 2x their expected frequency
• Edge scanner producing edges (after noon ET)
• Kalshi collector flowing (data in last 2 hours)

Skips all desks in the ToDo group. Sends Telegram alert only when issues are found.

Where:

• Script: /home/ubuntu/edgeclaw/scripts/health-monitor.sh
• Cron: every 4 hours
• Log: /home/ubuntu/edgeclaw/logs/health-monitor.log

How It All Fits Together

Before coding:    Pre-Session Commit (save point)
During coding:    Branch if risky, master if small
After coding:     Quality Gate (6-step verification)
End of session:   Session Summary + Change Log
After restart:    Pre-Flight Checklist (automated)
All day long:     Health Monitor every 4 hours

Post-Build Quality Gate (separate doc)

After any code change — 6 steps, no exceptions:

1. Simplify (2 passes)
2. Math check (2 passes)
3. Function test (2 passes)
4. Import & dependency check
5. Type check
6. Integration check

Every issue gets fixed. If fixes create new code, loop back through all 6 steps.