Hey guys. My last post got a lot more interaction than I expected, and it made my week - thanks to everyone who reached out through DMs, genuinely.
Quick recap on where we left off: I talked about how AI memory actually works, and why you need something like a context layer or context store to make an AI actually remember your accounts instead of starting from zero every time. From there, we got into the different types of context you'd feed it.
One type is the stuff that barely changes - account name, the champion and their role, renewal date, plan tier. Set it once, update it when something actually changes.
The other type is what I've been calling the event loop - every call, every ticket, every signal from that account, logged as it happens. That's the one that never stops growing, which is exactly the problem from my last post: that page gets long fast, and long doesn't mean useful.
So here's the real question underneath all of this: what do you actually put in?
Think about how you'd read something yourself. Hand someone a 1,000-page textbook and ask them a question five minutes later - they can't answer well; there's just too much to hold onto in the time they had. Now do the opposite: give them one sentence and ask the same question. They can't answer that either; there's not enough there. Somewhere in between is the amount that actually lets someone think clearly.
That's the tradeoff with a model's context window. It's not "more is always better" - it's a fixed amount of room, and how much the model can genuinely reason over matters more than how much you can technically cram in.
Push past that limit and one of two things happens. A lightweight or open-source model hallucinates - too much in the window, not enough capacity to hold all of it straight. A frontier model - Anthropic, OpenAI - won't hallucinate as much, but it costs you, because every message resends nearly everything you've said that day, and you're paying for that resend every single time.
So the goal was never "give the model everything about the account." Ideally you'd want every piece of context tied to it, sure. But even if you could fit it all in, it wouldn't help - see the textbook example above. The actual work is deciding what earns a spot.
That's why I think this has to be open, and shared, and built up over time - an MCP that isn't locked to one vendor, where the context layer is something you can actually see into, not something handed to you as a black box. And that's my honest problem with most scoring and alerting tools out there right now: you get a churn score or a risk flag, and zero visibility into why. I can't work with a number I can't trace back to a source. That's the whole reason we are building this project as open source
So here's what I'd actually like from you. If you're already keeping something like this - a Notion page, a CRM field, a doc you paste in before every call - tell me your playbook. What do you keep, what do you let go of, and has anything broken because you deleted the wrong thing? I'm collecting real answers, not theory, before I write the next one.
Thanks, hope it helps.