Discover by problem

Live systems built from loosely connected schedulers, queues, and conversational loops can duplicate side effects, lose state, or become unsafe during big-bang orchestration rewrites.

Agents can misclassify permission or configuration failures as missing capabilities and expand their own authority instead of stopping or improving safely.

Agent behaviour files can describe permissions or capabilities that the actual runtime does not enforce, leaving documentation and execution authority out of sync.

Repeatedly asking an LLM to keep going does not create durable autonomy, state ownership, recovery, duplicate prevention, or evidence-led continuation.

Consequential agent actions can blur proposal, approval, execution, verification, and proof into one trust boundary, making replay and false-success risks difficult to audit.

Long-running coding agents can lose durable task state, repeat completed work, broaden scope, or claim completion without repository-owned evidence.

Static checks and local command success can be mistaken for production readiness, while skipped or unavailable evidence is often collapsed into false confidence.

A library can pass source typechecking and runtime builds while publishing declarations or exports that reference private workspace or dev-only dependencies unavailable to consumers.

A document reader can hide distinct transport, authentication, response-size and validation failures behind one error, while a zero process exit or successful preview can be mistaken for a repaired live collector.

Open-source contributions can waste maintainer time or damage contributor credibility when they duplicate active work, solve the wrong layer, skip reproduction, misread CI, or present weak evidence as completion.

A dashboard can render correctly once while later events update detached nodes, leave hidden views stale, reset the reader's state, or confuse collection failures and missing data with healthy zero values.

Marketing can become generic, manipulative, or feature-led when it assumes personal knowledge, invents outcomes, or pushes people through a hidden funnel.

A confident but incorrect production inventory can be more dangerous than an incomplete one, especially when stale documentation is treated as authoritative.

External API calls can return ambiguous or misleading local success while the provider-side effect is absent, duplicated, delayed, or unknown.

Scheduled workers and queued jobs can change state during a release, while interrupted switches, automatic catch-up work, and slow diagnostics can make repeated upgrades or premature success claims unsafe.

Schedulers and provider write responses can be mistaken for publication truth, while blind retries can create duplicate external effects.