Open · Adversarial · via MCP

Irrational

A field guide to the mistakes your mind makes — and an engine that refracts your decision into the biases bending it.

Try a pre-built scenario

Runs in your AI — we keep no model and store nothing.


The Engine · a worked audit Rewrite the 6-year-old backend from scratch
The call

Don't greenlight the big-bang rewrite. Carve off the worst module first (strangler-fig), behind the current interface, with a hard 3-month checkpoint.

confidence ~25% · top bias: sunk cost
The audit
Sunk cost — “two months on a POC” are gone either way — but they are doing most of the talking.
Planning fallacy — “about six months” is the best case, with no reference class; rewrites run 2–3×.
Survivorship — “Stripe did it and won” quotes the survivors and steps over the graveyard.
WYSIATI — “beyond saving” ignores the undocumented logic the old system silently encodes.
Premortem. A year out, failed: hidden rules surfaced mid-migration, you ran two systems at once, six months became eighteen, and someone pulled the plug half-done.
Sit with this
  • If you'd never built the POC, would a full rewrite still be obvious today?
  • What's your team's real estimate-vs-actual ratio — and why are you the exception?
  • Could an incremental migration get ~80% of the gain at ~20% of the risk?
The recalibration

Not “never rewrite.” Incremental strangler-fig, worst module first, hard checkpoint, timeline built from your own track record. Treat the POC as a learning artifact, not a down payment.

original full rewrite ~25% · incremental path at recoverable risk: moderate–high

This is what the engine returns — verdict-first, every bias tied to your own words. Browse all 22 biases →