azurewraith

6 ms·

31.
by azurewraith 5mo ago
Stately (and XState ^_^) is pretty neat, I hadn't come across it yet... (edit:) neat to see visual XState being used for application logic as well I see constant posts on Reddit/HN about the ways that AI is amazing and at the same
32.
by azurewraith 5mo ago
for the integration piece that ties into Claude Code and other places where AI is used most frequently? yes I think it does... we're not fighting context in Opus/Sonnet as much as we are in smaller models and we're only addi
33.
Show HN: Statewright – Visual state machines that make AI agents reliable(github.com)
126 points by azurewraith 5mo ago|59 comments
34.
by azurewraith 5mo ago
Exactly right, and the next step is making it enforceable rather than aspirational. Restrict the plan phase to read-only tools so the agent literally can't edit during planning. Restrict the impl phase to the edit tools the plan identi
35.
by azurewraith 5mo ago
There's a third mode that works better: structured phases (scoped to each feature, like humans do). (Plan phase => human reviews plan) => (Implement phase => human reviews diff) => (Test phase => tests run). The curren
36.
by azurewraith 5mo ago
The review burden scales with the agent's decision space (which almost nobody is doing anything to limit today) and it's a variable you can control. When an agent has a discrete state, a subset of tools it can work with and const
37.
by azurewraith 5mo ago
The "can't retrace the reasoning" problem is solvable with deterministic workflow constraints. Agents currently run with carte blanche, and they take a mile if given an inch. If the agent was in a specific phase with only s
38.
by azurewraith 5mo ago
I've had similar experiences when I throw a bunch of agents at a problem... some things get flagged but a lot gets truncated in the summarization step. Per-phase constraints solve this naturally, and I think the problem is better suit
39.
by azurewraith 5mo ago
You've touched on the core issue... prompt based orchestration is non-idempotent. Same input, different orchestration paths every run. I've had better experience enforcing tool restrictions in discrete phases with deterministic