Failure Map

# Failure Map — the master prompt for planning ONE real project.
# Run it against your strongest model (Fable 5). Fill the {{...}} blocks.
# Draft lands in domains/plans/{{NN-name}}.md. Check it against
# rubrics/FAILURE-MAP-SUCCESS.md (all 8) before a cheaper model runs it.
# ------------------------------------------------------------------------------

I want you to write me a FAILURE MAP for one specific project — a step-by-step plan
detailed enough that a cheaper AI model can follow it start to finish without asking me
anything, with a **tripwire** planted at every point it could fall off.

THE PROJECT:
{{what exists now, what "done" looks like, the hard constraints — compliance, latency,
budget, zero-downtime, data residency — and how serious it is: POC / demo / production}}

Look first, don't touch:
{{the repo / system / inputs it should read before planning}}.

Then write the map so that:
- each step says what the model should SEE if it worked,
- each step plants a **tripwire** — the most likely way it fails and what to do instead,
- where the path can branch, give a clear trigger ("if you see X, do Y") so nothing is
  left to guesswork,
- anything you can't confirm up front is flagged, with the exact check that settles it,
- it ends with how to stop safely if things go wrong, and the checks that prove it's done.

Then poke holes in your own map once — find where it would break in practice, fix it,
and tell me what you changed.

Write it so someone could hand it to a mid-tier model and it just runs. Grade against
rubrics/FAILURE-MAP-SUCCESS.md before returning.