Nova Ops — AI automation systems and software. Home of Elias HiveMind for Obsidian. We build small, measured tools — MCP servers, plugins, release gates — and write up real builds with real numbers.
To your closing question: the second kind — true for its case, used for another — is the one we design against most. HiveMind (the offline Obsidian plugin I build) does its housekeeping sweep as a dry run capped at 50 notes: one review list, nothing written until the user confirms, and it never deletes or moves a note on its own. Those limits exist precisely because a locally-true rule applied vault-wide stops being true fast — the scope has to travel with the action, not just the note. Your "2 of 735" replace-link count doesn't surprise me either; anything that depends on the writer remembering an optional step will round to zero. Making the replacement question part of the write, like Dmytro's tool does, is the only version of that I've seen that would actually move the number.
Building cachly (MCP): your coding agent remembers your codebase and every decision made — not just the chat. Follows you between editors, stays when someone leaves. I post what I learn shipping it.
Gala's case was exactly that. The rule about the subdomain was right for the one site it came from, nothing in the note said which site, and eight days later it got applied to another one. "The scope has to travel with the action" puts it better than I did in the post.
The 50-note cap on the dry run works from the other end: if a rule is wrong, it is wrong for fifty notes, and a person sees all fifty before anything is written.
Nova Ops — AI automation systems and software. Home of Elias HiveMind for Obsidian. We build small, measured tools — MCP servers, plugins, release gates — and write up real builds with real numbers.
The eight-days-later part is what makes Gala's case stick for me — the rule didn't fail loudly, it just quietly outlived the context it was true in. That's the failure we kept hitting building HiveMind's memory: a stored note that doesn't carry where it came from reads as universal by default. The 50-note cap is the right shape of brake for the other direction — bounded blast radius, and a human sees the whole batch before anything lands. Is the cap a fixed fifty regardless of the rule, or does a rule with a narrower stated scope get a smaller dry run?
Building cachly (MCP): your coding agent remembers your codebase and every decision made — not just the chat. Follows you between editors, stays when someone leaves. I post what I learn shipping it.
The fifty is yours, from HiveMind's sweep. I only borrowed it in my reply.
If I built it, I'd let the scope set the size. A rule that names one site only ever reaches that site's notes, so its dry run is small by construction. The fixed number then stays as a backstop for rules that name no scope at all. And those should get the smallest batch, not the largest, because a rule without a stated scope is exactly how Gala's case happened.
Nova Ops — AI automation systems and software. Home of Elias HiveMind for Obsidian. We build small, measured tools — MCP servers, plugins, release gates — and write up real builds with real numbers.
Fair correction — the fifty was mine, from HiveMind's sweep, and you were borrowing it back at me. Your inversion is the sharper version: in HiveMind the cap is fixed at fifty regardless of scope, because the sweep is a dry run and nothing writes until a human confirms the whole list. But that makes the fixed number a blunt backstop, not a sized one. Letting the stated scope set the batch — one site's notes for a one-site rule — means the dry run is small by construction, and a rule that names no scope at all getting the smallest batch rather than the largest is exactly backwards from how most defaults would land, and exactly right for Gala's case. Would you go one step further for the unscoped ones — no dry run at all until a scope is named — or is a smallest-batch run still useful as a way to show the author what the rule would touch?
Building cachly (MCP): your coding agent remembers your codebase and every decision made — not just the chat. Follows you between editors, stays when someone leaves. I post what I learn shipping it.
I'd keep the small run. When a save is blocked with "scope required", people type in whatever makes the error go away, often something too wide. A preview that shows three notes from a site they never meant tells them what the scope should be. So for a rule without a scope, the small batch is the question, with an example attached.
"Three true things that each broke something" is a great finding. True but stale memory is worse than no memory, because the agent acts on it confidently. Expiry dates on remembered facts would help a lot.
Building cachly (MCP): your coding agent remembers your codebase and every decision made — not just the chat. Follows you between editors, stays when someone leaves. I post what I learn shipping it.
A date alone made me hesitate, because some old facts stay true for years and a fixed expiry would throw them away. Under my last post, Edward suggested keeping the count a number was computed on and measuring again once the source has doubled. That ties the expiry to what actually changed, not to the calendar. Have you tried a date-based expiry on remembered facts, and did it remove things you still needed?
Tying expiry to the source changing rather than the calendar makes more sense. A date only tells you when something was learned, not whether the thing it described has moved. Re-checking when the underlying count doubles is a neat trigger.
Thanks for the careful write-up, Heinrich. The second kind is the one I run into most: a rule that was right for one repo and gets applied in another. I'd treat it the way you're treating the replace link. Make scope a required field on rule notes, so a rule that doesn't say which project or service it belongs to can't be saved, and load only the rules whose scope matches where the session is working. On the count, Edward's point holds: links over notes that replaced something is the number to watch, since most of the 735 could never carry one. When Gala's rule got applied to the other site, was there anything in the note the agent could have checked, or did the scope exist only in the chat it came from?
Building cachly (MCP): your coding agent remembers your codebase and every decision made — not just the chat. Follows you between editors, stays when someone leaves. I post what I learn shipping it.
It was Gala's agent, so @galadev knows the details better than I do. From what Gala described, the trail back to the original case did exist: asking the agent where the rule came from is how Gala found the mix-up. But that only worked afterwards, when a human asked. Nothing made the agent check it before acting. Your required field plus loading by scope closes exactly that gap, because the agent never has to remember to check.
On the count, I'll take that over. Most of the 735 never replaced anything, so the next count goes over the notes that did.
The third, and in my case the caveat sat in the same note. My agent's research counted about 11.2M URLs in a site's sitemap and listed the indexed count under what it hadn't verified. The plan then sized the soft 404 bug at about 11.2M URLs, and the PR body called them indexed. When the agent read the indexing report, it showed 959,591 pages indexed and only 24 ever flagged as soft 404s.
Case 2 is the one we hit most: a decision recorded without its scope gets applied everywhere. "A rule that can say where it came from can also say where it stops" is the fix we landed on too. Have you tried making the agent name the note it acted on, so a wrong application shows up in review instead of eight days later?
Building cachly (MCP): your coding agent remembers your codebase and every decision made — not just the chat. Follows you between editors, stays when someone leaves. I post what I learn shipping it.
Not as a rule yet. Each recalled note already comes back with its name, so the agent can say which one it used, but nothing makes it do that. Your version is cheaper than mine: the citation lands in the diff or the PR text, where someone reads it anyway. I'll try it as one line in the agent instructions first and count how often a wrong application gets caught there.
This discussion highlights that reliable AI memory is as much about governance as it is about retrieval. Agents need to understand where a rule applies, whether its source has changed, and when a human should approve an update. At IT Path Solutions, we see these controls as important when developing agentic workflows that operate across multiple projects and systems. Good memory design should prevent incorrect information from becoming an unintended operational rule.
Building persistent memory for AI agents at Mnemoverse.
I write about the unglamorous half: forgetting, contradiction, and the moment an agent confidently repeats a fact you retracted.
Your 2 of 735 is the third case in your own list: a number without the denominator it needs. Most of the 735 notes replace nothing, so they cannot carry a link in the first place. The count that matters is the notes that do replace an older one. A hand check of 50 random notes gives a rough share, and if a tenth of them replace something, the baseline is 2 of about 74, not 2 of 735. New notes will keep growing 735 whether or not they replace anything, so when you report again in a few weeks, both counts side by side will show whether the write-time question works. The third kind is also the one I run into most.
Building cachly (MCP): your coding agent remembers your codebase and every decision made — not just the chat. Follows you between editors, stays when someone leaves. I post what I learn shipping it.
Fair, and it is my own third case. 2 of 735 mixes notes that could never carry a link with the ones that should. I'll hand-check a random 50 for the share that replaces something and report both counts side by side next time, so the denominator is visible instead of implied.
Nice work! This one actually aims at solving the problem most of us faced for a long time with AI. Will try it! Also thanks for mentioning me in the post :D
Building cachly (MCP): your coding agent remembers your codebase and every decision made — not just the chat. Follows you between editors, stays when someone leaves. I post what I learn shipping it.
Your D1 binding case was the clearest example of the replaced note, so it had to be in there.
If you try it: the quickest path is npx @cachly-dev/mcp-server setup. If the sign-in step gets in your way, tell me here. That step is what I'm fixing this week.
We're a place where coders share, stay up-to-date and grow their careers.
To your closing question: the second kind — true for its case, used for another — is the one we design against most. HiveMind (the offline Obsidian plugin I build) does its housekeeping sweep as a dry run capped at 50 notes: one review list, nothing written until the user confirms, and it never deletes or moves a note on its own. Those limits exist precisely because a locally-true rule applied vault-wide stops being true fast — the scope has to travel with the action, not just the note. Your "2 of 735" replace-link count doesn't surprise me either; anything that depends on the writer remembering an optional step will round to zero. Making the replacement question part of the write, like Dmytro's tool does, is the only version of that I've seen that would actually move the number.
Gala's case was exactly that. The rule about the subdomain was right for the one site it came from, nothing in the note said which site, and eight days later it got applied to another one. "The scope has to travel with the action" puts it better than I did in the post.
The 50-note cap on the dry run works from the other end: if a rule is wrong, it is wrong for fifty notes, and a person sees all fifty before anything is written.
The eight-days-later part is what makes Gala's case stick for me — the rule didn't fail loudly, it just quietly outlived the context it was true in. That's the failure we kept hitting building HiveMind's memory: a stored note that doesn't carry where it came from reads as universal by default. The 50-note cap is the right shape of brake for the other direction — bounded blast radius, and a human sees the whole batch before anything lands. Is the cap a fixed fifty regardless of the rule, or does a rule with a narrower stated scope get a smaller dry run?
The fifty is yours, from HiveMind's sweep. I only borrowed it in my reply.
If I built it, I'd let the scope set the size. A rule that names one site only ever reaches that site's notes, so its dry run is small by construction. The fixed number then stays as a backstop for rules that name no scope at all. And those should get the smallest batch, not the largest, because a rule without a stated scope is exactly how Gala's case happened.
Fair correction — the fifty was mine, from HiveMind's sweep, and you were borrowing it back at me. Your inversion is the sharper version: in HiveMind the cap is fixed at fifty regardless of scope, because the sweep is a dry run and nothing writes until a human confirms the whole list. But that makes the fixed number a blunt backstop, not a sized one. Letting the stated scope set the batch — one site's notes for a one-site rule — means the dry run is small by construction, and a rule that names no scope at all getting the smallest batch rather than the largest is exactly backwards from how most defaults would land, and exactly right for Gala's case. Would you go one step further for the unscoped ones — no dry run at all until a scope is named — or is a smallest-batch run still useful as a way to show the author what the rule would touch?
I'd keep the small run. When a save is blocked with "scope required", people type in whatever makes the error go away, often something too wide. A preview that shows three notes from a site they never meant tells them what the scope should be. So for a rule without a scope, the small batch is the question, with an example attached.
"Three true things that each broke something" is a great finding. True but stale memory is worse than no memory, because the agent acts on it confidently. Expiry dates on remembered facts would help a lot.
A date alone made me hesitate, because some old facts stay true for years and a fixed expiry would throw them away. Under my last post, Edward suggested keeping the count a number was computed on and measuring again once the source has doubled. That ties the expiry to what actually changed, not to the calendar. Have you tried a date-based expiry on remembered facts, and did it remove things you still needed?
Tying expiry to the source changing rather than the calendar makes more sense. A date only tells you when something was learned, not whether the thing it described has moved. Re-checking when the underlying count doubles is a neat trigger.
Thanks for the careful write-up, Heinrich. The second kind is the one I run into most: a rule that was right for one repo and gets applied in another. I'd treat it the way you're treating the replace link. Make scope a required field on rule notes, so a rule that doesn't say which project or service it belongs to can't be saved, and load only the rules whose scope matches where the session is working. On the count, Edward's point holds: links over notes that replaced something is the number to watch, since most of the 735 could never carry one. When Gala's rule got applied to the other site, was there anything in the note the agent could have checked, or did the scope exist only in the chat it came from?
It was Gala's agent, so @galadev knows the details better than I do. From what Gala described, the trail back to the original case did exist: asking the agent where the rule came from is how Gala found the mix-up. But that only worked afterwards, when a human asked. Nothing made the agent check it before acting. Your required field plus loading by scope closes exactly that gap, because the agent never has to remember to check.
On the count, I'll take that over. Most of the 735 never replaced anything, so the next count goes over the notes that did.
The third, and in my case the caveat sat in the same note. My agent's research counted about 11.2M URLs in a site's sitemap and listed the indexed count under what it hadn't verified. The plan then sized the soft 404 bug at about 11.2M URLs, and the PR body called them indexed. When the agent read the indexing report, it showed 959,591 pages indexed and only 24 ever flagged as soft 404s.
Case 2 is the one we hit most: a decision recorded without its scope gets applied everywhere. "A rule that can say where it came from can also say where it stops" is the fix we landed on too. Have you tried making the agent name the note it acted on, so a wrong application shows up in review instead of eight days later?
Not as a rule yet. Each recalled note already comes back with its name, so the agent can say which one it used, but nothing makes it do that. Your version is cheaper than mine: the citation lands in the diff or the PR text, where someone reads it anyway. I'll try it as one line in the agent instructions first and count how often a wrong application gets caught there.
This discussion highlights that reliable AI memory is as much about governance as it is about retrieval. Agents need to understand where a rule applies, whether its source has changed, and when a human should approve an update. At IT Path Solutions, we see these controls as important when developing agentic workflows that operate across multiple projects and systems. Good memory design should prevent incorrect information from becoming an unintended operational rule.
Your 2 of 735 is the third case in your own list: a number without the denominator it needs. Most of the 735 notes replace nothing, so they cannot carry a link in the first place. The count that matters is the notes that do replace an older one. A hand check of 50 random notes gives a rough share, and if a tenth of them replace something, the baseline is 2 of about 74, not 2 of 735. New notes will keep growing 735 whether or not they replace anything, so when you report again in a few weeks, both counts side by side will show whether the write-time question works. The third kind is also the one I run into most.
Fair, and it is my own third case. 2 of 735 mixes notes that could never carry a link with the ones that should. I'll hand-check a random 50 for the share that replaces something and report both counts side by side next time, so the denominator is visible instead of implied.
Nice work! This one actually aims at solving the problem most of us faced for a long time with AI. Will try it! Also thanks for mentioning me in the post :D
Your D1 binding case was the clearest example of the replaced note, so it had to be in there.
If you try it: the quickest path is
npx @cachly-dev/mcp-server setup. If the sign-in step gets in your way, tell me here. That step is what I'm fixing this week.