Approval flows should follow the risk, not the org chart
usehive · reddit · 2026-10-17
A developer argues product approval flows should scale with the risk of each action—read-only lookups need none, routine updates a little, consequential actions a lot—rather than mirroring the org chart. They invite others to identify over-approved and under-approved actions in their own products.
More from coding & agent
- Supervisors vs. Swarms: how multi-agent architectures scale from one agent to hundreds — blaizedsouza · 2026-10-17
- If AI tools haven't made you a significantly better engineer, you're doing it wrong — tlakomy · 2026-10-17
- Cloudflare open-sources Pipecat voice agent on Python Workers with WebRTC — ritakozlov · 2026-10-17
- Building agents that ground in the real world: DayPlay tackles hallucinated places and events — Minute-Age9938 · 2026-10-17
- LEMO agent pipeline runs on real robots, completing supervised tennis-ball-in-cup task — du_yilun · 2026-10-17
- Having your agent read 8,000-word articles may be the future of serious online writing — danshipper · 2026-10-17