Internal · four sheets and the wiring

The machine’s own desk.

Everything the routine reads and writes, in the four sheets it actually maintains. The routine is the only thing that edits these — I read them.

targets.csv

written by 01-source-opportunities · 100 rows held · 8 shown

Company	Pool	Decision maker	Signal	Score	Status	Updated
{{ t.co }}	{{ t.pool }}	{{ t.who }}	{{ t.signal }}	{{ t.score }}	{{ t.status }}	{{ t.updated }}

kpis.csv

written by 12-log-replies and the nightly tick

Metric	Now	Target	Source of truth	Cadence	Last updated
{{ k.name }}	{{ k.now }}	{{ k.target }}	{{ k.src }}	{{ k.cadence }}	{{ k.updated }}

prompts.csv

the inventory — every prompt, what it reads, what it writes

Prompt	File	Reads	Writes	Runs
{{ p.name }}	{{ p.file }}	{{ p.reads }}	{{ p.writes }}	{{ p.runs }}

icps.csv

read by 02-qualify to assign a pool and a score

Pool	Who	Why they fit	The signal	Email difficulty	Share
{{ i.pool }}	{{ i.who }}	{{ i.why }}	{{ i.signal }}	{{ i.email }}	{{ i.share }}

How the routine updates a sheet.

One nightly pass. The clock wakes the worker, the worker runs a skill, the skill writes exactly one sheet, and the sheet’s last updated cell is the receipt that it ran.

Fig. 1 — the nightly loop · solid = automatic, dashed = my hand

One write, in full.

What actually happens when the routine adds a target — the sequence I’d expect to see in the log.

00  clock      tick → pool at 88, want 12          enqueue prospect×1
04  worker     claim job 4471 · kind=prospect
05  routine    read prompts/skills/00-profile.md
05  routine    read icps.csv → pools A–F, weights
11  collector  LinkedIn + Ad Library + their site
19  routine    score 12 candidates against profile
21  routine    append 12 rows → targets.csv
21  routine    stamp targets.csv last_updated=2026-09-04T03:21Z
22  worker     report job 4471 done
23  clock      recompute kpis.csv · pool=100 · stamp
00  me         open this page, read two cells