Why AI memory isn’t the same as project memory.

Ask ChatGPT or Claude to remember something about you, and it will — a preference, a fact, the way you like to work. Over time it builds a running impression of you out of everything you’ve said, across every conversation, on every topic. That’s genuinely useful, and it’s exactly what that memory is for: making the assistant feel like it knows you. It isn’t organized around any one thing you’re doing. It’s organized around you.

The trouble starts when what you actually want isn’t “remember that I like directness” but “remember where the Q3 launch decision landed.” That’s not a fact about you, it’s the state of a specific undertaking, and nothing in a personalization memory was built to hold that shape. To even attempt it, the system has to comb back through everything you’ve said, guess which parts belong together, and guess which one is still true if two of them disagree. Ask either assistant to summarize where things stand on something you discussed weeks and several conversations ago, and you’ll get a best guess, assembled from fragments — not a record.

A project is organized around the undertaking, not around you. When you tell your assistant what you’ve landed on, that becomes part of a named, specific record — this trip, this decision, this launch — not one more fact folded into a general impression of who you are. Nothing has to be reconstructed later, because it was already organized at the moment you said it.

Giraffe is a project outside of either assistant: the current facts, the decisions, what’s still open, for one specific thing you’re doing — not the conversation that produced them. You tell your assistant what you landed on, it saves that to the project, and the project stays organized around the undertaking instead of around you. ChatGPT and Claude keep being good at knowing you. Giraffe keeps track of what you’re doing.

Being organized around the project also means it can be precise about what kind of thing changed. A fact updates in place, with the old value kept as history — true right up until it wasn’t. A decision that gets reversed stays visible instead of vanishing, marked reversed, with the reason attached. And a question you’re still turning over stays open on purpose, right there in the project, until you actually settle it — at which point your assistant marks it resolved, with the answer, rather than quietly forgetting you’d ever been unsure.

Say you’re hiring for a small business. In ChatGPT, early on: “Open question for the hiring project — full-time or contract to start?” You genuinely don’t know yet, so it stays logged as open, not decided either way. A few weeks later, after talking to a few candidates, in Claude: “Resolve that — we’re going contract-to-hire, three-month trial. Two of the three people we liked only wanted to test the fit first anyway.” The question moves from open to answered, with your reasoning attached. Back in ChatGPT before you draft the job listing, you ask it to check the project first. It reads contract-to-hire as the settled answer — not because it remembers the conversation you had in Claude, which it never saw, but because you told it where to look, and the project had an actual answer waiting instead of an old open question it would’ve had to guess about.

Open the project on its own and the open questions aren’t buried in search results next to everything else you’ve ever said — they’re just there, next to the facts and the decisions, in a project that reads like a page: what’s settled, what’s still open, in plain sentences. That’s the Simple view. Structured view shows the same project broken into its labeled parts. Either way, it’s a record of the undertaking, not a profile of you.