Everything I could decide myself is decided. What's left needs
you. Each one has a recommendation from Fable — if you agree, pick it and
press Done. "I'm not sure" is a real answer and becomes work for me.
You don't need to open the session — pressing Done sends your answer back and it picks up.
1The drive-gate holds every session open whenever ANY session is past the 80% context ceiling — even sessions that can do nothing about it. One operator took that same block ~15 times in 2 hours, a full turn each, while fleet quota sits at 2-3% weekly with 4 of 6 accounts maxed. But the hold is deliberate: your architect skill says it exists so 'a fleet riding hot stays visible to you either way'. Keep the visibility, or stop the repeat cost?
Fable recommends: Hold once per episode, then go quiet (latch it, like the quiet-stop wake) — you still see the first alert, nobody pays a turn per cycle It is the only option that keeps BOTH documented rules. You still get the alert that makes a hot fleet visible, and the gate stops holding a reader on an item its own text calls 'REPORTED, NOT PRESCRIBED' — which the gate's own constitution (line 444, 'block to force work, never to force patience') already forbids. The latch pattern is proven here: the quiet-stop wake fires once per episode for exactly this reason. Cost is bounded and it does not reverse your visibility decision. Tried first, unsuccessfully: fd040e61e — NEEDS HUMAN. Two passes, options reversed, disagreed at medium confidence. As-given picked fix-now, citing the gate's own 'block to force work, never to force patience' plus the self-hot exemption already in the file. Reversed picked do-not-change, citing architect/SKILL.md:534 that the hold is documented intent so a hot fleet stays visible. I verified BOTH citations exist and are accurate — this is a real conflict between two of your own written rules, not a Fable failure.