Learn

Failure modes checklist.

Common failure modes in real workflows — and the deterministic gates that stop drafts from becoming decisions.

Scope drift

The system subtly changes the task definition mid-run (different audience, different constraints, different deliverable).

Gate

Require an explicit scope block and a reviewer approval step before downstream actions.

Hidden assumptions

Defaults are silently invented (units, thresholds, policy interpretation, missing context) and become treated as true.

Gate

Force an assumptions list with required fields; reject outputs with missing assumptions.

Unsupported claims

Statements read confidently but have no cited evidence or input source.

Gate

Deterministic evidence rules: claim → source mapping, or mark as unknown and block approval.

Artifact ambiguity

The output is fluent but not operational: no checklist, no fields, no acceptance criteria.

Gate

Enforce artifact schemas (tables, checklists, diffs, forms) with validation before review.

Tooling side effects

Tool calls or automations run with unclear permissions, producing irreversible changes.

Gate

Require allowlists, sandboxing, and a deterministic human approval gate for side-effecting actions.

Stale inputs

Old documents, outdated policies, or cached context lead to a correct-looking but wrong result.

Gate

Require input timestamps and an explicit ‘data freshness’ check before approval.