06-reference

indy dev dan jev news curator agent

2026-10-19·reference·source: IndyDevDan (YouTube)·by IndyDevDan
agentic-engineeringjevpi-agentdurable-agentstyped-judgments

"My Jev Pi Durable Agent CURATES News: HYPE, FACT, or SIGNAL" — IndyDevDan

Full transcript: [[2026-10-19-indy-dev-dan-jev-news-curator-agent-transcript]] (ElevenLabs speech-to-text; YouTube auto-captions were HTTP 429 rate-limited across repeated retries, multiple player clients, and two cooldown windows, so this transcript has no embedded timestamps — segment timestamps below are approximate, from word position and the video's own chapter markers).

Why this is in the vault

Direct continuation of last week's Pi Durable video ([[2026-10-12-indy-dev-dan-pi-durable-proactive-agents]]): same durable-agent architecture, now demoed as a news-curation product that gates every pipeline stage through Jev typed judgments. The HYPE/FACT/SIGNAL three-bucket classification is a concrete, reusable Jev pattern directly relevant to the founder's own content-triage skills (/process-youtube, /process-newsletter, /community-watch), which currently do this same judgment by hand or via full LLM calls rather than a cheap classifier gate.

Episode summary

IndyDevDan demos a "Durable News Agent": a Pi Durable agent (same framework from last week's video) that runs on a one-minute cron, gathers engineering news from a configured set of sources (Hacker News, Latent Space, Simon Willison, etc.), and uses Jev to gate, dedupe, rank, and classify each item into three buckets — Hype (unfounded excitement), Facts (objectively true but not always actionable), and Signal (true, actionable right now). The agent runs detached on his M4 Mac Mini and in parallel on an exe.dev cloud sandbox, reachable from a browser generative UI and a terminal TUI that stay synced in real time against the same durable session. He walks through the layered architecture (SQLite → Pi Durable → custom durable-agent implementation → API → SDK consumed by browser/TUI/cron/CLI), the tool set built for the agent (run_news_sweep, jev_classify, present_news, ask_taste, etc.), and a taste-tuning data flywheel where upvoting/downvoting a card or chatting with the agent ("increase the weight of Gemini") adjusts keyword weights that steer future sweeps. He frames all of it inside his recurring "in the loop → near the loop → out the loop" taxonomy and closes with a plug for his "Phase 3" agentic-engineering product (self-promo, pre-launch sign-up, no third-party sponsor).

Key arguments / segments

Notable claims

Mapping against Ray Data Co

The HYPE/FACT/SIGNAL three-bucket output is a directly reusable Jev typed-judgment pattern for the founder's own content triage, and it is strikingly close to what /process-youtube and /process-newsletter already do by hand: this very note ends with a sharp verdict line (skip/skim/read/file) that is functionally a hand-rolled hype/fact/signal call made by a full LLM pass over the transcript, not a cheap classifier gate. A concrete, cheap experiment: put a Jev classifier in front of the per-article/per-video subagent fan-out in /process-newsletter and /process-youtube (and the /community-watch and /curiosity skills) that scores relevance plus a hype/fact/signal-style bucket before the expensive full-context summarization pass runs. This is the same "Jev gates the expensive LLM call" architecture shown on screen here (gather → gate(jev) → dedupe → rank), and it extends the standing hypothesis already flagged in [[2026-10-05-indy-dev-dan-openrouter-state-of-models-jev-open-weights-tokenomics]] ("~20% savings, n=1, treat as hypothesis until RDCO measures it").

Separately, the "in loop / near loop / out loop" framing is a reasonable lens on this very dispatch: a Mode 4 Watch cron spawning a Mode 1 Manual processing sub-agent for one video is RDCO's own near-to-out-loop pattern already in production for this channel. The architecture itself (durable agent behind an API, with multiple detached thin clients, browser and TUI, staying synced) remains the same reference pattern already mapped in detail in [[2026-10-12-indy-dev-dan-pi-durable-proactive-agents]]; this video adds no new architectural primitive beyond that note, just a second concrete application (news curation instead of incident response) and a cleaner worked example of Jev gating every pipeline stage.

Mapping strength: medium-strong on the Jev-as-cost-gate pattern (directly actionable, cheap to test), low on anything net-new architecturally (durable Pi substance was already captured last week).

Related