Lockdown — Daily Accountability CLI

The Premise

I’d tried every accountability tool and bounced off all of them. Habit trackers reward streaks instead of work. Goal apps reward declarations instead of shipping. Coaches reward feeling good about the conversation instead of getting harder over time.

I wanted a system with four immutable laws and no escape hatches:

1. Declare an objective — the one thing this day needed to produce.
2. Ship an artifact — output something the world can see.
3. Hit the health floor — non-negotiable minimum on body.
4. Subtract something — remove something that adds nothing.

A day where any law was skipped didn’t count toward the streak. The system was built to refuse to lie to me.

The Build

A single-file Node.js CLI — lockdown.js, about 860 lines, zero npm dependencies. JSON file storage for daily logs and recurring bills. Three cron jobs handle the morning declare, the evening verify, and the weekly review.

node lockdown.js status   # Today's state, streak, engagement mode
node lockdown.js week     # Day-by-day breakdown
node lockdown.js streak   # Current/longest streak, law valid rate

The interesting part is the engagement mode. The system detects gaming patterns — laws marked complete in suspicious sequences, artifacts that don’t change between days, declarations that drift — and shifts tone accordingly. Honest weeks get terse confirmation. Drift gets called out. Outright gaming gets refused.

What It Taught

That accountability is mostly a measurement problem. Once you can detect the gaming patterns, the willpower part takes care of itself — because most failures aren’t willpower, they’re unmeasured re-definition of what counts. Lockdown’s gaming detector outperformed every human accountability partner I’d ever paid for, and I wrote about why in /writing/ai-accountability-partner.

Still running daily. Source stays internal because the gaming heuristics expose tells I don’t want broadcast.