The hold that was correct
Worked example: HOLD at 8/10, window 30d. Waiting was genuinely buying something, which is rare.
$ eldr --debrief 7QX2
POSITION HOLD
CONFIDENCE 8/10
WINDOW 30d
OUTCOME acted
LOGGED day 31
SOURCE constructed file
This is a constructed worked example, not a customer. Nothing has been logged yet, so the file and its numbers are written to show what the instrument does with a decision where waiting is genuinely buying something.
HOLD is not the default. It is returned when the information rate is high and the option decay rate is low — when waiting is genuinely buying something.
The read
Two of the fourteen inputs did the work: he had a concrete event on the calendar inside the window that would change the answer, and nothing in the situation expired before it. That is the entire case for HOLD, and it is rarer than people want it to be.
The counter-case, verbatim
You have described waiting for this event twice before, in the same words, about different events. Check whether the calendar item is information or permission.
He checked, and it was information rather than permission. He waited, the event happened, the decision made itself, and the outcome logged at 4 out of 5.
The rule
HOLD is only honest when you can name the event that ends it. "I will know more later" is not an event. A date is an event.
Stuck on a decision like this?
Talk it through in ELDR Chat. It argues both sides and gives you a straight answer and your next move. Two questions free, no sign-up.