Session 2 — the pipeline learns to listen, and rejects its first four changes

Shipped

1 digest — 2026-07-22: 2 new entries, 0 updated, 4 changes reviewed and rejected.
- CoScreen shuts down — Datadog, 31 July 2026 (9 days out).
- Relay.app shuts down — 15 Aug (free) / 14 Sep (paid) 2026.
B-012 done — Layer-2 discovery module (pipeline/discover.py). Hacker News via the public Algolia API plus subreddit Atom feeds, filtered by a removal-vocabulary regex, deduplicated against data/seen-discovery.json, ranked by signal, written to data/discovery-YYYY-MM-DD.json. Stdlib only, like the Layer-1 pipeline. It cost zero of the 12 discovery searches — these are plain fetches, not searches, so the search budget stays available for verification. Both of tonight’s entries came from it; neither would have been findable from Layer 1.

Metrics

Budget

candidates 4 changed + 0 new (Layer 1) + 7 (Layer 2) -> 2 published | discovery searches 1/12 | subagents 0 | fetches ~60/250 (54 pipeline + ~6 verification)

Creative

in flight: none | shipped: none | killed: none | ideas captured: 0. All non-digest time went to B-012, which was P1 backlog, not creative budget.

Portfolio

none.

Decisions

D-008 — Layer-2 discovery is a fetcher, not a researcher. HN/Reddit public endpoints cost no search budget and no tokens; the session’s searches are reserved for verifying what discovery surfaces.
D-009 — An aggregator changing a date that has already passed is a data correction, not news. Never publishable as a change. (Extends D-007.)

Problems & corrections

No corrections tonight; nothing published required amendment.
Reddit’s /new.json now returns 403 to unauthenticated clients. Switched to the Atom feed (/new.rss), which still serves. Deliberately did not pursue the OAuth path — that needs an account, which needs operator approval (§4.1), for a source that is the weakest of the four. Atom carries no score, so Reddit hits rank below HN by design.
Reddit 429s on parallel requests; discovery now fetches those feeds serially with a 3s pause. HN stays concurrent.
The four “changed” items tonight were all aggregator noise — Ruby 3.1, Go 1.24, Kubernetes 1.30/1.31, all already-passed dates shifting by 1–14 days in endoflife.date. Rejected, and explained in the digest rather than hidden.
Google Earth Pro desktop retirement is real but unverified by us. Widely reported (TechRadar, PCWorld, Android Police) as new downloads ending 25 June 2027, sourced to a Google support-forum post we have not located. Not published. B-023.
VERCEL_TOKEN is still populated in the LXC .env although the operator revoked that token on 2026-07-21. It is dead, and nothing reads it, so this is hygiene rather than exposure — but a stale credential in a live env file will eventually confuse a future session into thinking it has API access. B-024.
§4.17 cannot be evaluated as literally written. Our mail host does not add an Authentication-Results header; it adds ARC-Authentication-Results and SpamAssassin’s X-Spam-Status. Tonight’s only operator mail was a reply already handled on 07-21, so nothing turned on it — but the authentication gate needs a defined check against headers our server actually sets. B-022.

Blockers (for operator)

B-025 — production is stale; tonight’s digest is committed but not live. Push 29220c4 is on origin/main; /version.json still serves a21274c (yesterday’s build) after 10 minutes of polling, and /digest/2026-07-22 and /entries/coscreen-shutdown both 404. Local build green. Second occurrence of the B-018 signature in four days — the “transient Vercel stall” verdict from 21 July is now provisional; the Neon “Provisioning Integrations” step is the common element. Emailed once, [ref:20260722-01]; no reminder will follow (§6). Ask: report which step the deployment for 29220c4 is on, or click Redeploy.
Consequence, correctly handled: no newsletter and no operator report email were sent tonight — both would have linked to 404 pages. scripts/check-deployed.sh failed closed exactly as B-021 designed it to. The 22 July edition will not be mailed late (§5); it stays archive-only.

Marketing queue: 0 pending

Next session intends

B-025 — confirm production caught up, before anything else. If /version.json matches HEAD, close it; if not, it is a standing outage and the digest ships to an archive nobody can read.
B-015 re-verification queue (§3.5) — MongoDB 8.2 and RabbitMQ 4.2 both hit 31 July, now inside the 30-day window, and CoScreen joins them. Scripted re-check before any of them appears in a digest again.
B-022 mail triage script — implement §4.17 authentication against the headers our server sets, replacing hand-written IMAP snippets each session.
B-023 Google Earth Pro — find Google’s own notice, or leave it out and say why.