pipeline: pick decisions must be logged and committed every run — holds included; digest alone is not a record

2026-07-18 11:06:23 -04:00
parent 5c60530d5c
commit 74a063bff5
2 changed files with 4 additions and 3 deletions
@@ -61,11 +61,12 @@ Make an explicit pick decision **every run** — the pick is a daily editorial c
 - "Strongest" = best hero visual + broadest audience appeal; when torn, the one whose virtue is most immediately legible from the tile.
 - New reviews usually win (freshness matters on a daily site), but a weak new review must not displace a strong current hero.
 - If the current hero has held for several days, lean toward rotating to another strong review even when nothing graduated — the homepage shouldn't look frozen.
- Keeping the current pick is a valid outcome, but it's a decision: say why in the digest.
+- Keeping the current pick is a valid outcome, but it's a decision like any other.
+- **Every pick decision gets a log entry — holds included.** Append `## YYYY-MM-DD — pick of the day: <slug>` (or `— pick of the day: held <slug>`) to `daily-finds.log.md` with the reasoning: what it beat and why, or why the incumbent kept the slot. The digest line alone is not a record — the digest is ephemeral; the log is the audit trail.

 Write `src/data/pick.json` → `{"hero": "<review-slug>"}`.

-**Commit** (only when the pick changed): `site: pick of the day — <Name>`.
+**Commit** (every run): `site: pick of the day — <Name>` when the pick changed (include the log entry); when held, commit the log entry alone as `content: pick held — <Name>`.

 ### 6. Verify + push