$ eldr --open debrief-the-circuit-breaker-fired-on-day-three
$ eldr --debrief 2CB7
POSITION MOVE (conditional)
CONFIDENCE 7/10
WINDOW 60d
STOP 30 Apr · 8 paying customers · else close
TRIGGERED yes, 3 days after review date
OUTCOME acted (stopped)
SATISFACTION 4/5
SOURCE constructed file
This is a constructed worked example, not a customer. Nobody has run a read here yet: the product has not launched and the decision log is empty. The situation and the numbers are written to show how the instrument reads a file of this shape. Real debriefs replace it when there are any.
A circuit-breaker is a decision you make in advance about a state of the world you expect not to be in. This file is the only reason I believe they work, and it is also the file that shows what they cost.
A side product, built evenings, launched in February. $16,000 of his own money committed to ads and contract design. In the intake he wrote a stop condition unprompted, which is rare, since most men have never been told to write one, and the read did what it always does with a stated stop: it treated it as the window boundary and made the position conditional on it.
The stop, in his words: "If I do not have 8 paying customers by 30 April, I close it and I do not spend another dollar."
Most of the library is open. The material that names costs and patterns directly sits with the instrument that uses it.
Full refund within 30 days · cancel in two clicks · email 7 days before renewal · no retention call.
No trial. There has never been one.