The pursuit queue - why four GOs became a red alertConcept

The 'JobHunt pursuit incomplete' alert that fired at 15:40 on 9-6 is the pursuit queue reporting arithmetic: six GOs inked in one sitting, two packages built per run. Reading the queue file tells you what happens next without asking.

There are three files in the loop. ink_apply.py is the only writer of briefing decisions: a GO appends an entry to JobHunt/leads/pursuit-queue.json with slug, org, role, URL and your written comment. pursuit.py runs as leg 5 of the nightly wrapper with --max 2, pops up to two entries, and runs the full package build (research, resume, cover, prep, fit) for each. package_send.py then delivers the five PDFs to Job Applications/<Org>/ on the device.

The alert is the queue's dead-man's switch. When pursuit.py finishes and entries remain, it files '🚨 JobHunt pursuit incomplete' so a stuck queue cannot rot silently. A queue with four entries after a six-GO sitting is the switch working correctly. It clears itself as runs drain the backlog: two Monday, two Tuesday.

Each lead's own folder (JobHunt/leads/<slug>/) carries its state: a lead moves from queued to packaged when the five files exist, and only your hand moves it to sent (sent_on in the lead record). Twenty packages are at 'packaged' today. EDF has been at packaged for thirteen mornings. The queue explains what Claude builds; sent_on records what you did.

Worked example

Read the queue and the drain rate from the terminal:

python3 -c "import json;q=json.load(open('/Users/tom/Claude/JobHunt/leads/pursuit-queue.json'))['queue'];[print(e['queued'],e['org'],'-',e['comment'] or '(no comment)') for e in q]"

grep -n "max" /Users/tom/Claude/JobHunt/scripts/nightly_wrapper.sh | head -3

ls /Users/tom/Claude/JobHunt/leads/changeorg-vp-ai-strategy/

• Prints every queued lead in order with your ink comment. Order is drain order: Change.org first because it was queued first from the 9-3 briefing.
• Shows the --max 2 flag the wrapper passes to pursuit.py. That number is the drain rate.
• Once packaged, the lead folder holds the five deliverables plus the lead record. Empty or missing means still queued.

Gotchas

• The alert dedups by signature. If it stays open for days with a rising count, the queue is stuck (a build failing), not merely full. Check JobHunt/logs/nightly.log for 'pursuit leg exit=1' as on 9-3.
• A lead skipped on paper (both boxes blank, like Cresta on 9-4) is not queued and not refused. It can resurface.
• Raising --max speeds the drain but each package is a 10-15 minute LLM build. Six in one night risks the 05:15 watchdog.