c5fb98af8d
- agent-parallel-tracking/ — 'How do you keep track of multiple coding agents?' — the multi-agent attention cluster (1xmzp2n, 1xh5cum, 1xdjb2g, 1xipsk0, 1xk0ghj); answered with documented per-session hook events (session_id, typed Notification matchers) and the status line. - agent-run-without-asking/ — 'Should you let your coding agent run without asking permission?' — the autonomy cluster (1xexhwf, 1xk8imc, 1xk277d); answered with the permission-mode ladder, the docs' own container/VM warning, rule precedence, sandboxing pointer, PreToolUse deny. Internal target Mon 2026-11-09; drafted 2026-11-05. All doc claims re-read 2026-11-05 against code.claude.com (permissions, hooks, statusline). Ban compliance: no product of ours, no competitor, no handles, no price, no invented figures.
Marketing tree
One voice, one place. Every later artifact draws on positioning.md — do not
invent framing per-asset.
positioning.md # source of truth: wedge, voice, banned phrasings, approved claims
calendar.json # scheduled pushes: date, channel, status
briefs/<channel>.md # per-channel rules, format, limits, what "good" looks like
drafts/<id>/ # agent output: copy.md, assets/, rationale.md
pending/ approved/ posted/ # human gate by directory move
metrics/weekly.md # funnel snapshot, generated
listening.md # buying-intent threads + drafted replies
Hard rule
approved/ is the only thing a human ever publishes from. Nothing posts itself.
Workflow: agent drafts into drafts/<id>/ → moves to pending/ when complete →
a human reviews and moves it to approved/ → the human publishes from approved/
under their own account → the artifact (or a pointer) lands in posted/.
Nothing in drafts/ or pending/ is ever publishable, by anyone, by any means.
The weekly read
bun --env-file=.env scripts/weekly-metrics.ts (or bun run metrics:weekly)
rewrites metrics/weekly.md from the live databases: the staged funnel, the
campaign breakdown (getAnalyticsSummary.topCampaigns' grouping), and the one
stage that moved. It needs TURSO_DB_URL, TURSO_DB_TOKEN, NOOK_DB_URL and
NOOK_DB_TOKEN — no other production secret. The file is generated; never
hand-edit it. The numbers are engineering's; the interpretation is the CMO's.