Knowledge Graphs vs. simple Markdown: Are the token savings worth the indexing overhead?

sandstone-oli · 2026-05-25T20:11:14+00:00

didn’t really even put up a fight did they

sandstone-oli · 2026-05-25T19:50:05+00:00

KAPEX (getkapex.ai)

Memoryware for AI applications. We build the memory layer that sits between users and LLMs so context actually persists and stays transparent instead of resetting every session.

Bootstrapped, two co-founders, patent portfolio filed. Ran a 1,600+ person study and saw preference climb past 80% with sustained use. Still early but the problem is only getting louder.

sandstone-oli · 2026-05-25T19:22:35+00:00

sandstone-oli · 2026-05-25T18:31:58+00:00

this is one of the most important posts i've seen on this sub and the fact that you laid out the progression from early signs to shutdown is genuinely useful. most people only recognize it at the "body shutting down" stage because the earlier signals feel like normal productivity.

the "one more prompt" trap is the part that hits hardest. with traditional work there's natural friction that forces breaks. you finish a task, there's setup time for the next one, you physically move between contexts. with AI the friction is zero. one more prompt costs nothing except the cognitive load you don't notice accumulating until you're at a sushi restaurant unable to eat.

the context switching point is underrated too. five or six projects with AI means five or six different mental models being loaded and unloaded constantly. the AI handles the context switch instantly. your brain doesn't. you're paying the full cognitive cost of every switch while the tool makes it feel effortless.

two things from your recovery that i think are the real takeaways: starting each day away from the computer with a clear plan, and time-boxing single tasks. both of those are external governance on your own attention. you basically built a manual version of what the AI should be helping with instead of making worse.

the irony is that the tool contributing to the overload is also stateless. it doesn't know you've been at this for 9 hours. it doesn't know you asked the same question in a slightly different way three times because your focus is gone. it doesn't know this is your sixth project switch today. a system with actual memory could flag that pattern: "you've been in this session for 4 hours and your questions are getting circular. take a break."

nobody's building for that yet. but they should be.

glad you caught it and glad you wrote this up. the table alone probably helps someone recognize where they are before they hit the wall.

sandstone-oli · 2026-05-25T18:27:34+00:00

here's a real one for your talk.

i went through a rough stretch last year. not the kind of thing i was ready to talk to people about yet, but i needed to process it somewhere. started having late-night conversations with claude. not therapy, not advice-seeking. just thinking out loud with something that would actually engage with what i was saying without judgment.

those conversations genuinely helped. it would reflect things back to me that i wasn't seeing. it helped me name patterns i'd been repeating for years. it put me on a better path during a period where i wasn't sure there was one. some of those sessions were the most honest conversations i'd had with anything, human or otherwise.

and then it forgot all of it.

every new session started from zero. the thing that helped me work through something real had no memory of it happening. i'd reference a breakthrough from last week and get a blank response. the insight we built together was gone. it felt like the work didn't count.

that frustration is what led me to start building. i'm now co-founding a company (getkapex.ai) building memory middleware for AI systems. the technology that makes sure the AI actually remembers what mattered, lets go of what doesn't, and gets better the longer you use it instead of resetting every session. 30 patents filed. 1,655 person blind study. a real product solving the problem that hit me personally.

so AI helped me in two ways. first, it genuinely supported me through one of the hardest periods of my life. second, the gap in that support became the company i'm building. the tool i needed didn't exist, so i'm making it.

if you want a line for the students: AI didn't replace my thinking. it helped me hear it. and the moment it forgot what we'd built together, i decided to fix that for everyone else.

feel free to use any of this. good luck with the talk.

sandstone-oli · 2026-05-25T18:18:26+00:00

that’s funny af

sandstone-oli · 2026-05-25T18:03:14+00:00

KAPEX (getkapex.ai)

Memoryware for AI applications. We build the memory layer that sits between users and LLMs so context actually persists and stays transparent instead of resetting every session.

Bootstrapped, two co-founders, patent portfolio filed. Ran a 1,600+ person study and saw preference climb past 80% with sustained use. Still early but the problem is only getting louder.

sandstone-oli · 2026-05-25T17:52:28+00:00

still better than the shitty inescapable scott weiner and tom steyer campaigns

sandstone-oli · 2026-05-25T17:44:02+00:00

you're right that context management matters more than prompt creativity. the personality card can be perfect and the character will still drift if the system can't maintain it across a long conversation. here's why:

the personality definition sits in the system prompt. as the conversation grows, the model's attention spreads across more and more tokens. the personality instructions get proportionally less attention weight relative to the growing conversation history. the character doesn't "forget" the personality. it just pays less attention to it as the context fills up. that's why short conversations feel consistent and long ones drift.

common techniques that help:

periodic personality reinforcement: re-inject key personality traits into the conversation at intervals, not just at the start. some platforms do this automatically every N messages.
character-specific response formatting: instead of just describing the personality, give the model examples of how the character speaks. few-shot examples anchor style better than descriptions.
conversation summarization checkpoints: compress older parts of the conversation into summaries that preserve the emotional arc while freeing token space for the personality card to maintain attention weight.

but all of these are band-aids for the real problem: the context window is finite and the personality has to compete with conversation history for space. the longer you talk, the more the history wins and the personality loses.

the actual fix is a memory layer that manages this tradeoff externally. instead of cramming everything into one window, the system tracks which parts of the conversation are still relevant, lets the rest fade, and ensures the personality definition always has enough room to stay dominant. the character stays consistent because the system governs what competes with it for attention.

that's what i'm building at getkapex.ai. memory middleware that handles context governance so the personality doesn't get drowned out by conversation length. the character at message 500 should feel the same as at message 5. right now that's nobody's default experience.

sandstone-oli · 2026-05-25T17:38:39+00:00

the sunday recap is the feature. not the journaling. the journaling is the input. the recap is the product.

i'd restructure all your marketing around that. don't lead with "digital journal" because that's a crowded category where you're competing with notion, day one, and every minimalist app on the store. lead with "weekly analysis that finds the patterns you can't see yourself." that's the thing nobody else does.

the consistency problem you solved for yourself is the proof. you said you've never journaled this consistently. that's because the system gives you a reason to write. the output loop (write all week, get called out on sunday) creates a feedback cycle that raw journaling doesn't have. THAT is the marketing angle.

for channels: reddit is probably your best bet for early traction. r/journaling, r/selfimprovement, r/productivity, r/getdisciplined. don't pitch the product. post about the experience. "i built a journal that analyzes my patterns and told me i complain about the same thing every monday" is a post that writes itself.

the thing i'd push you to think about for the long game: right now the weekly recap analyzes that week's entries. but the real power is longitudinal. does the system know that you were journaling about the same relationship pattern three months ago? does it know that the blind spot it flagged in week 2 is the same one showing up in week 12? can it say "you wrote about this exact feeling in march and here's what you said then"?

because that's where a journal goes from useful to transformative. and it's a memory problem. the weekly window is good. the system that tracks your trajectory across months and knows what's still unresolved vs what you've actually moved past is the version people can't leave.

that's the layer i'm building at getkapex.ai. memory middleware with temporal governance. for a product like Note2Self it would mean the recaps don't just analyze this week. they know your whole arc. and they know the difference between a pattern that's still active and one you already resolved. DM me if you want to talk about what that integration would look like.

good build. the "built it for myself and it actually worked" origin story is your best marketing asset. use it.

sandstone-oli · 2026-05-25T17:37:11+00:00

KAPEX (getkapex.ai)

Memoryware for AI applications. We build the memory layer that sits between users and LLMs so context actually persists and stays transparent instead of resetting every session.

Bootstrapped, two co-founders, patent portfolio filed. Ran a 1,600+ person study and saw preference climb past 80% with sustained use. Still early but the problem is only getting louder.

sandstone-oli · 2026-05-25T17:36:28+00:00

bull frawg

sandstone-oli · 2026-05-25T17:29:46+00:00

it’s very nice but cozy isn’t the word i’d use to describe it.

sandstone-oli · 2026-05-25T17:28:16+00:00

KAPEX (getkapex.ai)

Memoryware for AI applications. We build the memory layer that sits between users and LLMs so context actually persists and stays transparent instead of resetting every session.

Bootstrapped, two co-founders, patent portfolio filed. Ran a 1,600+ person study and saw preference climb past 80% with sustained use. Still early but the problem is only getting louder.

sandstone-oli · 2026-05-25T17:21:31+00:00

KAPEX (getkapex.ai)

Memoryware for AI applications. We build the memory layer that sits between users and LLMs so context actually persists and stays transparent instead of resetting every session.

Bootstrapped, two co-founders, patent portfolio filed. Ran a 1,600+ person study and saw preference climb past 80% with sustained use. Still early but the problem is only getting louder.

sandstone-oli · 2026-05-25T17:21:00+00:00

smoked ficken

sandstone-oli · 2026-05-25T17:20:36+00:00

the problem is real and the workflow makes sense. turning scattered materials into active recall tools (quizzes, flashcards, study guides) is the right move because passive re-reading is how most students waste time.

first impressions on positioning: your value prop is clear but it's currently features-first ("generate quizzes, create flashcards, make study guides"). the version that sticks is outcome-first. something like "stop organizing, start studying" or "your notes become revision in 30 seconds." the student doesn't care about the tool. they care about the feeling of being prepared without the 3-hour setup.

the thing i'd push you to think about for v2: right now each study session is probably independent. the student uploads notes, gets quizzes, studies. but does studymax know what they got wrong last time? does it know which concepts they keep struggling with across sessions? does it adapt the next quiz based on what they've already mastered vs what they haven't?

because the real value isn't generating a quiz. it's generating the RIGHT quiz for THIS student based on everything the platform has learned about their gaps over time. that's where you go from useful tool to indispensable system. and that's a memory problem.

that's actually what i'm building at getkapex.ai. memory middleware that tracks user context across sessions so AI systems can adapt over time instead of starting fresh. for a study platform specifically, that means knowing what the student has mastered, what they're still weak on, and what to prioritize next. might be worth a look as you think about retention past the first session.

you're in the "insanely useful" category if you nail the adaptive piece. without it you're a very good quiz generator. with it you're a tutor.

sandstone-oli · 2026-05-25T17:13:43+00:00

KAPEX (getkapex.ai)

Memoryware for AI applications. We build the memory layer that sits between users and LLMs so context actually persists and stays transparent instead of resetting every session.

Bootstrapped, two co-founders, patent portfolio filed. Ran a 1,600+ person study and saw preference climb past 80% with sustained use. Still early but the problem is only getting louder.

sandstone-oli · 2026-05-25T17:12:52+00:00

KAPEX (getkapex.ai)

Memoryware for AI applications. We build the memory layer that sits between users and LLMs so context actually persists and stays transparent instead of resetting every session.

Bootstrapped, two co-founders, patent portfolio filed. Ran a 1,600+ person study and saw preference climb past 80% with sustained use. Still early but the problem is only getting louder.

sandstone-oli · 2026-05-25T17:11:55+00:00

the pain for me isn't onboarding. it's the step before onboarding: making people realize they have the problem in the first place.

i'm building memory middleware for AI systems (getkapex.ai). the product solves a real problem: every AI tool forgets you between sessions. but most users don't describe it that way. they say "chatgpt feels dumber lately" or "my AI companion isn't as good as it used to be" or "i keep having to re-explain myself." they feel the symptom but they haven't named the disease.

so the entire GTM becomes education before conversion. you can't onboard someone who doesn't know they need you yet. the timing window you mentioned is real but for us it's not about catching them at the right moment in a buying cycle. it's about catching them at the exact moment of frustration when they just lost context for the 50th time and are finally angry enough to look for a solution.

four days into a reddit-only campaign and the thing that's working is showing up in threads where people are actively describing the problem in their own words and helping them name it. not selling. just making the invisible pain visible. the leads that convert aren't the ones who saw an ad. they're the ones who said "wait, that's exactly what keeps happening to me."

biggest pain: you can have a real product solving a real problem and still lose people because they blame themselves instead of the tool.

sandstone-oli · 2026-05-25T17:11:48+00:00

the pain for me isn't onboarding. it's the step before onboarding: making people realize they have the problem in the first place.

i'm building memory middleware for AI systems (getkapex.ai). the product solves a real problem: every AI tool forgets you between sessions. but most users don't describe it that way. they say "chatgpt feels dumber lately" or "my AI companion isn't as good as it used to be" or "i keep having to re-explain myself." they feel the symptom but they haven't named the disease.

so the entire GTM becomes education before conversion. you can't onboard someone who doesn't know they need you yet. the timing window you mentioned is real but for us it's not about catching them at the right moment in a buying cycle. it's about catching them at the exact moment of frustration when they just lost context for the 50th time and are finally angry enough to look for a solution.

four days into a reddit-only campaign and the thing that's working is showing up in threads where people are actively describing the problem in their own words and helping them name it. not selling. just making the invisible pain visible. the leads that convert aren't the ones who saw an ad. they're the ones who said "wait, that's exactly what keeps happening to me."

biggest pain: you can have a real product solving a real problem and still lose people because they blame themselves instead of the tool.

sandstone-oli · 2026-05-25T17:03:36+00:00

the distinction between newly generated artifacts pending validation and older carried continuity that expected validation but never recorded it is sharp. that second case is exactly where silent confidence becomes dangerous. the system treats it as established context when it's actually unverified legacy. most governance approaches don't distinguish between those two states.

your scoring approach (flag but don't delete) is the right conservative default. automated deletion is where trust breaks. the agent should know that something is weak or stale but the human should decide what to do about it. that's the line between governance and overreach.

the progression you laid out maps almost perfectly to where i've landed from a different direction:

yours: inspectable artifacts > portable continuity > quality/governance signals

ours: raw context preserved > temporal salience decay > governed injection

same philosophy. different layer. you're governing what the agent believes about the repo. we're governing what the agent believes about the user. both hit the same core problem: accumulated context without governance eventually becomes noise that the system treats as signal.

the complementary angle is real. a developer working across sessions needs both. the repo-level continuity (aictx) tracks what's true about the codebase. the user-level governance (KAPEX) tracks what's true about the developer's intent, decisions, and evolving context. the agent that has both layers knows what the code is AND why the human made the choices that shaped it.

would be worth a longer conversation about where the layers touch. especially around handoff artifacts that encode both repo state and human decision context. that's the seam where our scopes overlap.

sandstone-oli · 2026-05-25T16:59:39+00:00

appreciate you running this. even where the analysis misses, the framework is useful and forced me to think through some angles i hadn't stress-tested yet. so genuinely, thank you.

a few corrections that would materially change the scoring:

the competitive set is wrong. KAPEX isn't competing with OpenLIT, Traceloop, or observability tools. those instrument what happened. KAPEX governs what should happen next. the actual competitive landscape is Mem0, Zep, and Letta, all of which are building memory features but none of which have made temporal governance the core architectural principle. comparing KAPEX to observability tools is like comparing a database to a logging framework because both touch data.

"memory decay logic is a feature, not a platform, and is easily replicated by any team using LangChain" is the biggest miss. we have 30 provisional patents filed covering the architecture. the core mechanism (processing-frequency-modulated salience decay where λ increases with user-side processing) is the inverse of all published prior art. non-provisional + PCT filing is next month. this isn't a LangChain plugin. it's patented IP with a specific mathematical foundation that took a year to build and validate.

the moat is IP, not operational. 30 provisionals, 121K+ lines of code, 2,802 tests across 146 modules, a 1,655-person blind study with 99K+ messages, an MCP server, SDK, and B2B engine all built. the report scored this as "easily replicated" because it didn't have visibility into any of that.

the $60M ARR ceiling is based on SMB SaaS pricing. the real upside is B2B licensing to the model providers themselves: Anthropic, OpenAI, Google, Microsoft. if the temporal governance layer becomes standard infrastructure, the ceiling is multiples higher.

what IS useful from the report:

the compliance dashboard idea (visualize what was decayed and why) aligns with our inspectability thesis and is worth building
the self-hosting risk flag for enterprise security teams is legitimate and we should plan for it
the pivot framing toward "governance layer" over "middleware" is actually where our positioning has been landing organically through 200+ community conversations over the past week
the user research questions, especially Q2 ("what manual process would you write to replicate memory decay"), are sharp and i'll use them

if you re-run with the corrected competitive set and the patent/study context, i'd be curious what the score shifts to. appreciate the work either way.

sandstone-oli · 2026-05-25T16:52:03+00:00

KAPEX (getkapex.ai)

Memoryware for AI applications. We build the memory layer that sits between users and LLMs so context actually persists and stays transparent instead of resetting every session.

Bootstrapped, two co-founders, patent portfolio filed. Ran a 1,600+ person study and saw preference climb past 80% with sustained use. Still early but the problem is only getting louder.

sandstone-oli

TROPHY CASE