Comment by jorl17

I'd like to share with HN an almost exact message I got from Fable today, with exactly ONE word changed for privacy reasons.

I love what I can build now, but I sure as hell don't love the headaches this trend has been giving me.

> So the full honest arc on the case we set out to fix: the expiry rules and day note tripled the loose version of the story, the relay fix carried the device’s own guardrail through the pipeline, the fair replay then revealed the last mechanism — ticket-anchoring — which none of the shipped layers reach. Remaining options, in order of my confidence: making the resolved-ticket summaries in the AI’s context carry their day so the expiry rules have something to bite on (small, mechanical, targeted at the observed anchor); and the plan-B second-model check, which structurally catches this class no matter how the model reasons. About $25 of headroom remains. Which way?

Yikes.

(The worst part is that I understand it)