chirdeeps

3 ms·

1.
by chirdeeps 6mo ago
Extracting a framework from production experience is the right way to build one. The failure modes you encode are the ones that actually matter. Curious what the three failure modes were that caused the most incidents before you extracted t
2.
by chirdeeps 6mo ago
The failure mode most underrepresented in agent testbeds is cascading failure, what happens when individually correct agents interact in ways that produce collectively incorrect outcomes. Most testing focuses on individual agent behaviour.
3.
by chirdeeps 7mo ago
The biggest thing that surprised us: the constraint shifts from intelligence to reliability the moment agents start modifying shared systems. In a PoC, a wrong action is a failed experiment. In production, it's a corrupted customer rec
4.
by chirdeeps 7mo ago
This thread is an incredible resource for adversarial security testing, but I'd love to pull on the "Cascade failures" (#5) thread from the original post, because that's what actually takes down production systems most o
5.
by chirdeeps 7mo ago
The distinction between reversible and irreversible actions mentioned here is crucial, but there's an organizational layer to this problem that most monitoring tools miss entirely.When you scale past a single team, you inevitably end u
6.
by chirdeeps 7mo ago
OpenTelemetry and standard observability stacks are great for seeing the latency and token counts of individual LLM calls, but they break down when you try to debug the coordination between agents.The hardest failure mode we've had to