Products Get a Memory Layer. Decisions Don’t.
Decisions do not compound unless something remembers them.
In one of my early case studies, “My AI Kept Suggesting Features I’d Already Built,” I made a narrow, demonstrated claim: without a product’s schema, constraints, and roadmap, an AI assistant reinvented existing features, re-proposed roadmap items, and suggested work the product had already ruled out. Add the missing context back and the failure modes disappeared — two new suggestions approved, two killed correctly, zero reinventions.
That result held because the before-and-after was controlled: same product, same model, same session type, missing context added back.
The unresolved question is whether the product mattered, or whether the product merely made the leak visible. Products naturally accumulate memory surfaces. Decisions usually don’t.
What the case study actually proved
The mechanism has a name already: Intelligence Leaks — value lost when context, decisions, or instructions don’t persist between sessions. The product experiment showed one flavor of it precisely. A rejected or already-decided option came back, because nothing the model could see distinguished “already ruled out” from “not yet considered.” The model wasn’t malfunctioning. It was reasoning correctly from an incomplete record, which is a harder failure to catch than reasoning incorrectly from a complete one.
Re-explaining a preference costs a sentence. Relitigating a decision costs the decision-making itself, a second time, at full price, with no discount for having already paid it once.
What the case study didn’t test is whether “product” is doing any of the work in that result, or whether any sufficiently repeated decision degrades the same way once it stops living somewhere the next session can see it.
Why the Mechanism Should Generalize
The structural claim is narrower than it first sounds: a decision gets made, the decision isn’t written into a place a future session reads before it acts, and the same topic comes up again.
Products satisfy those conditions because they accumulate memory surfaces — a roadmap, a schema, a constraints document. The same conditions can exist around a pricing model, a market segment, or a hiring criterion — anywhere a decision gets revisited after the reasoning behind it has fallen out of view.
I haven’t measured those domains the way I measured the product case: controlled before-and-after, fixed failure categories, rerun conditions. The case study earns its narrow claim — schema, constraints, and roadmap fix product-level relitigation. The same structure may apply when a decision is made once and revisited later. That’s a claim still waiting on its own evidence.
The Honest Part
The product case had built-in memory surfaces. Most decisions don’t. That means the fix isn’t “write decisions down” in the abstract. It’s domain design: deciding what counts as durable, where it lives, and what the assistant has to read before it acts.
A pricing call doesn’t come with a roadmap. A hiring rubric doesn’t come with a schema. If the generalization holds, it holds because someone builds the equivalent structure for that decision type — not because it appears automatically the way it does for a product under active development. In my own builds, that structure is a decision file the assistant reads before proposing changes.
The narrower prediction is this: when a decision gets revisited without a persistent record of the first decision, the same failure shape is available — an option nobody has ruled out on paper looks, to any reasoner, like an option that’s still open. Whether that availability turns into the same measurable cost the product case showed is the open question, and it stays open until someone runs that test.
The Implication
The instinct is to treat the product case study as proof of a general principle. It’s proof of one narrow case, built well enough to trust on its own terms.
The transferable part isn’t “AI forgets things.” It’s the specific shape of the failure: a decision that isn’t written where the next session reads it is indistinguishable, from the model’s position, from a decision that was never made.
The product case proved the narrow version.
The broader bet is simpler: decisions do not compound unless something remembers them.