Day 88 of 92 · Wednesday · Learning

The Send Desk - 55 staged, one sent, and the page that owns the send stepCapability

The Send Desk is a page only this Mac can reach, built 10-1, where an application moves through four gates to Submitted. It is now the one place a send is recorded — the step the pipeline never had.

Catch-up progress
88/92
Why this matters to you

55 staged, 1 sent since 8-31. The pipeline built packages faster than anything recorded a send, and the three Submit tasks from 9-20 passed their date unseen. The desk exists because you named three blockers in one sentence: the prose isn't mine yet, there is no warm path into the org, and too many are staged while deadlines pass. Each got one feature.

A local workbench is a small program (the LaunchAgent app.zorc.jobs) that serves one web page at 127.0.0.1:8780. The address 127.0.0.1 means 'this machine' — no router, no Cloudflare, no login, and no personal data leaves the Mac. The page reads the same lead folders the nightly writes (JobHunt/leads/<slug>/lead.yaml) and appends to an activity log; it never rewrites a lead file in place.

Four gates per application, each a yes/no you can see. Live: the posting re-verified on the employer's own site (GET-only checks, nightly and on demand). Warm path: a contact found, outreach sent, replied, or skipped on purpose — it stops blocking once the deadline is under five days. My words: each outward asset rewritten by you; an own-words meter counts the five-word runs that do not appear in Claude's reference draft, and marking an asset final below 85% asks for a confirm (the resume is exempt). Submitted: records the real date and freezes the exact files sent. 'Active' is the existing priority-1 field, so the paper briefing's table and the desk always agree; the page warns above five.

Three inputs are waiting on you and nothing else: 3–5 writing samples in profile/voice/samples/ (the voice kit), your LinkedIn Connections.csv in profile/network/ (the people panel), and three outreach templates in library/outreach/. Deliberately not in v1: Gmail drafts, a PDB summary page, and gating the nightly package builds on activation — that last one is worth deciding after two weeks of use.

Worked example

Open the desk and see what it is waiting for.

launchctl list | grep app.zorc.jobs                       # the desk's own LaunchAgent
open http://127.0.0.1:8780                                 # the page; this Mac only

ls /Users/tom/Claude/JobHunt/profile/voice/samples/ 2>/dev/null || echo "no voice samples yet"
ls /Users/tom/Claude/JobHunt/profile/network/ 2>/dev/null   || echo "no Connections.csv yet"

# the stage counts the weekly review quotes
awk -F'|' 'NR>3 && NF>5 {print $5}' /Users/tom/Claude/JobHunt/tracker.md \
  | grep -oE '\*\*[a-z-]+\*\*' | sort | uniq -c
▶ Do it now
  1. Open the page. Count the Active cards against the 'aim for 5' line; note which gate is the first blocked one on the top card.
  2. Open one lead's drawer and read the four gates with their next action and time estimate — that is the unit of work the desk proposes.
  3. Put one real writing sample (an email or memo you wrote, 300+ words, as .md or .txt) into profile/voice/samples/. That is the first input the desk needs from you; three more unlock the voice kit.

Gotchas

Go deeper: send-desk-spec.md — what it is, status, decisions made during the build · Anthropic — Claude text watermark (2026-08-14)
One-card takeaway

A gate you can see beats a task you can snooze — the desk makes 'sent' a state with a date and frozen files, not a Things checkbox.