The scrape, rate, and notify loop behind an automated engine, drawn as one legible diagram.
A multi-step automation is only trustworthy when every branch and every stop condition is visible to the person paying for it.
A data-driven renderer emits the full pipeline from a spec: schedule, scrape, dedup against the whole board, LLM rating, score gates, and a single batched notification. Because the diagram is data, the renderer is reused unchanged for the next system.
Making a system legible is part of building it. A client can see exactly what runs, in what order, and where it stops.