Assign determinism and judgment per pipeline stage, not as an either-or
aronchick · x · 2026-09-26
Part 3 of aronchick's thread: the mistake is picking one. Determinism and judgment are per-stage properties — joins, aggregations, dedupe, validation stay deterministic; messy inputs like extraction, classification and narration are where models add value rules can't.
Related event: aronchick: In LLM data pipelines, draw the determinism boundary first(7 posts)→
More from coding & agent
- One Skill for World-Class Agent Research: Multi-Source Verification and Skeptic Voting — EXM7777 · 2026-09-26
- AgentStuff Launches: Plan Once, Let Claude Code and Codex Ship Projects in Parallel — tedddyoweh · 2026-09-26
- Simple KJnodes workflow adds bounding-box control to Krea 2 text-to-image — Mulksky · 2026-09-26
- Agent curates monthly clothing rental box, turning hours of scrolling into minutes — nikhilaravi · 2026-09-26
- Mirage launches Tesseract, a video creative suite that lets AI agents edit and render video directly — chrisfirst · 2026-09-26
- Claude runs TradingView solo: 14-second scans, backtests, 83% win rate — Aiden_Tech_Ai · 2026-09-26