Replace .md specs with a state machine: step through your agent's real reducer to interrogate its design
DavidKPiano · x · 2026-10-13
Instead of .md spec files, ohdearlordylord suggests modeling your system as a state machine (or reducer): have the AI generate an interactive diagram from your real events and real reducer, then step through it asking the agent 'why' for each transition. David Piano endorsed the idea and teased he's building something to make this workflow even better — turning fuzzy specs into inspectable, verifiable state flows.
More from coding & agent
- Daniel Jeffries: only ~2% can actually use AI agents, mass adoption is 10-20 years away — Dan_Jeffries1 · 2026-10-13
- Fully local AI short film mimics Wes Anderson style with a detailed open pipeline — Mist3r-Robot · 2026-10-13
- Controlling his Mac's terminal from a phone via t3 code beta while waiting at speech therapy — NERDDISCO · 2026-10-13
- LLM cache verifier drift: reject-only calibration tripled error rate; 5% audits fix it — Reasonable_Royal_621 · 2026-10-13
- A style guide for making Claude-like models write normally, and its linguistic traps — gleech · 2026-10-13
- Open-source desktop agent dodaios runs local Qwen models via ollama — and shows where 16GB models fail — InternationalGap3698 · 2026-10-13