Only Settled Decisions Carry Forward
When Curator opens a project it can bring in defaults you hold elsewhere. That is the most useful thing it does and the easiest to get wrong. It now offers only positions that have held up, that you made, and that bear on the project in front of you.
When you open a project, Curator’s resume diff does two jobs. It shows what changed in your standards since you were last here, the idea behind resume with what you know now. And it can carry in defaults you hold in your other projects, so a lesson learned in one codebase is waiting the first time it matters in another.
That second job is the most useful thing a memory layer does, and the one that costs the most when it is wrong. A default offered at session start lands before the agent’s first edit, framed as something you decided. If it is stale, the agent has little reason to second-guess it.
Why the bar is high
The risk is concrete. An agent’s mid-task draft, captured before the session changed course, can look newer than the correction that replaced it. Carried into the next project as a default, it would arrive with all the authority of something you decided.
So every carried default now has to pass three tests.
Only settled positions
A default that was later replaced does not carry. Neither does one that its own track record has turned against, or one that lost a disagreement where both sides had real evidence behind them. What Curator will not do is settle a disagreement by which note sounded more sure of itself. Only evidence picks a winner, and until there is some, the question stays open rather than being decided by tone.
Your decisions, not the agent’s narration
Agents say a lot of plausible things on the way to an answer, and capture keeps them because the context is useful. But a turn captured from the agent’s side of the conversation can no longer become a binding decision, and it cannot replace one of yours. It is still stored and still there to recall. When something should bind future sessions, it gets recorded on purpose, not inferred from a passing remark.
About this project
The carried list is chosen for the project you just opened, ordered by what bears on it rather than by date, and a project’s own notes never come back dressed up as advice from somewhere else.
Why a shorter list is the better result
The carried section can now come back shorter, and sometimes empty. That is intended. An empty section costs you nothing. A confident wrong default costs you a regression, plus the time it takes to work out where it came from. It is the same bar Curator holds recall to, where a wall of text is not an answer and an honest blank beats a fluent guess.
None of this puts a model in the path at session start. The resume diff is still computed from what is already stored, so the same store gives the same answer twice.
Where it stands
Curator is a working pre-release product: local, encrypted, and reached over MCP from the agents you already use. Follow release preparation.
Was this useful?