Day 94 of 98 · Wednesday · Learning

Threads - how your two-line turn stamp becomes the Desk at pdb.zorc.app/deskCapability

Threads turns the two-line stamp at the end of every turn into a nightly ledger of open loops and a page at pdb.zorc.app/desk. Nothing is typed twice: the stamp you asked for on 10-11 is now read by a script.

Catch-up progress

94/98

Why this matters to you

The first scan found 56 threads waiting on you, 14 where Claude owes you, and a 13-day-old weekly review still unmarked. Those were always true; until 10-11 nothing counted them. The Desk is the executive-assistant view your Threads Briefing ink chose first (D4: Scan + Desk).

A session transcript is a log file. threads_mine.py walks every transcript under ~/.claude/projects/, finds the last STATE: and NEXT [YOU|ME|PARKED]: lines (and falls back to the older ---TL;DR--- footer), and records who holds the ball, what the next action is, and when the session last spoke.

threads_scan.py merges that with four other sources - claude-mem observations, the tablet listing (every FOR REVIEW doc not yet tagged done), Things next steps, and the project ledger - into data/threads/ledger.json. threads_apply.py is the only writer of fates (open, parked, dropped, closed); it was seeded from your 10-11 ink and writes last_touched back to the project ledger.

gen_desk.py renders the Desk; gen_attention.py adds a Threads strip to the day page; run_threads.sh (LaunchAgent app.zorc.threads-scan, 05:45) scans, renders, deploys, verifies the page exists, heartbeats, and raises one quiet deduped alert on failure. job_health_check.py watches the heartbeat. The generated ledger stays local because it quotes transcripts; only fates.json is tracked in git.

Worked example

Read the ledger, then watch the miner find a stamp.

head -30 /Users/tom/Claude/PDB/data/threads/ledger.md
cd /Users/tom/Claude/PDB/scripts && python3 -I threads_mine.py --days 2 --skip-live-minutes 30 | head -20
grep -n "STAMP_NEXT_RE\|STAMP_STATE_RE" threads_mine.py
tail -5 /Users/tom/Claude/PDB/logs/threads.log

ledger.md is the human render: 'you N · claude N · parked N · closed N', then Waiting on you, Claude owes you, Parked, Closed.
threads_mine.py on its own prints what it extracted from the last two days of transcripts; --skip-live-minutes keeps a session still open from being reported as dropped.
The two regexes are the contract: a STATE: line and a NEXT [YOU|ME|PARKED]: line, bold or not. Change the stamp wording in CLAUDE.md and the miner stops seeing it.
threads.log is the nightly witness: start, scan exit code, desk rendered, deployed, heartbeat.

▶ Do it now

Open https://pdb.zorc.app/desk and read the first eight cards. Pick one 'waiting on you' item and do it.
Run threads_mine.py --days 2 and find this session's own stamp in the output. That is the loop closing.
Tomorrow morning check the day page's Threads strip: the count should have dropped by the one you did.

Gotchas

The miner reads the last stamp in a session, so a session that ends with a question and no stamp is invisible to it.
Fates come only from threads_apply.py (your ink). Editing ledger.json by hand is overwritten at 05:45.
ledger.json and ledger.md hold transcript excerpts; they are gitignored on purpose. Do not add them to a commit.

Go deeper: PDB/data/threads/ledger.md - tonight's ledger · PDB/scripts/run_threads.sh - the 05:45 job · The Desk

One-card takeaway

A derived view is only as good as the convention it reads; the two-line stamp is now load-bearing.

← Prev Index Next →