$ eldr --open debrief-he-re-ran-the-intake-four-times
$ eldr --debrief 8HK4 --thread
21:04 read 1 HOLD 6/10 window 30d
21:39 read 2 HOLD 5/10 window 30d
22:16 read 3 SPLIT 4/10 window 14d
23:02 read 4 MOVE 6/10 window 12d
outcome acted on day 3, satisfaction 2/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.
Four intakes in two hours on the same decision, each one differing from the last by two or three answers, until the output said the thing he came in wanting to hear. Then he acted on it inside 72 hours and rated the result 2/5.
This is published as a failure of the instrument, not of the man. He did what anyone does with a machine that will answer again if you ask again.
Nothing about the world. Between read 1 and read 4 he adjusted three inputs:
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.