Features explained
Keep decisions and merges in your knowledge
Switch keeping on for a project and the work you finish becomes something GPTree can cite later: a merge you applied, a decision you recorded, a board you committed. It lands in your own space, readable by nobody else until you share it.
Most of what you decide in a chat evaporates. You compare three approaches, merge the best parts, and a month later the reasoning lives in a conversation nobody will scroll back through. Keeping turns those finished pieces of work into knowledge GPTree can find and cite, without turning your whole chat history into a filing cabinet.
What gets kept
Three kinds of finished work, and only when you finish them:
- A merge you applied. Which branches went in, and the result that came out.
- A decision you recorded. The subject, the outcome, the alternatives considered, and which one was chosen.
- A board you committed. The passages you picked and the style they were polished in.
A whole conversation is never kept. Nor is a draft, a temporary chat, or anything GPTree was still thinking about. Keeping stores the verdict, not the deliberation.
Where it goes, and who can read it
Into your personal knowledge space. Not the project's shared space, not your team's: yours. A collaborator on the same project cannot read it, and answers for anyone else cannot cite it.
When a kept record is settled enough for other people to rely on, you share it yourself from the Knowledge page. Sharing moves it into your organisation's space, where answers can cite it and your team can read it. There is no bulk share and nothing shares itself.
It is labelled as ours, not as a source
A kept record is text this product wrote. GPTree labels it that way, and the label does real work: a claim whose only support is a kept record is never reported as verified. It needs a real source behind it.
That is the difference between a flywheel and an echo. Your own summaries are useful context, and they are not evidence of themselves.
Turning it on
Open a project's settings, go to the Review tab, and switch on "Keep decisions and merges in your knowledge". Only the project's owner can change it, because what is kept lands in the owner's space.
Keeping costs no credits. It stores what you already produced and reads nothing with a model.
Turning it off
Switch it off and nothing new is kept. What was already kept stays exactly where it is, labelled and citable, until you delete the record it came from.