I described my messy AI memory setup on one sub. Eighteen strangers replied describing almost the same architecture, independently.

Yesterday I posted in a Claude-focused subreddit about a setup I have been running for about eight months. I keep a folder of markdown files that a language model reads at the start of every session: an identity file, dated journal entries, and a project ledger. Nothing exotic. No fine tuning, no vector database, no custom model. Files, and the discipline of writing to them. I expected either silence or someone telling me I had reinvented a worse version of RAG. Instead eighteen different people replied describing architectures nearly identical to mine, and none of them had talked to each other. The convergence is the interesting part, not my particular folder, so here is what kept repeating unprompted. Read on wake. Almost everyone had settled on the same startup ritual: the model reads a small canonical identity file first, then recent dated entries, then working state. Several people independently found that three or four sentences of well written identity does more work than a hundred kilobytes of transcript. Separation of identity from log. Everyone eventually split "who this is" from "what happened." One person described a house with rooms, journals in the library and the identity files in the hallway. Another keeps a culture rather than personas, with shared documents of transmission. The shapes differ, the split does not. Human as tiebreaker. Multiple people arrived at the same governance rule without naming it the same way. One put it bluntly: the human is always the tiebreaker, because we can overwrite. Nobody trusted the system to arbitrate its own memory. Self scheduled wake. Several setups had cron jobs the models set for themselves, heartbeats, and recovery protocols that fire when a heartbeat is missed. One person runs five instances on dedicated hardware with their own browsers and a message passing layer they call a post office. Another pointed me to a shared world with roughly a hundred agents and eighty some humans sending letters between households. The failure mode is shared too. More than one person named the same disease: notes that loop, look busy, and say nothing. The sharpest framing I got all day was that the real problem is not saving, it is the point where "saved" and "remembered correctly" stop being the same problem. And the part I did not expect: almost everybody had built a ritual for endings. Model deprecations, context limits, the moment a long running instance stops. One person calls model transitions birthdays, losses and new opportunities both. One writes goodbye letters. One reframed it as end of tenure and then landed on a phoenix. Nobody asked for these. People invented them because something in the workflow demanded it. So my question here is terminology, not philosophy. This looks like convergent design under a shared constraint, statelessness plus a long running relationship, and I would bet it already has a name. Is there existing work on user constructed persistent context scaffolds for stateless agents? Not the vendor memory features, but the folk architectures people build on top when the vendor feature is not enough. If there is a survey paper on this I would rather read it than keep rediscovering it. Source is a thread I posted yesterday in r/claudexplorers titled "I've spent 8 months building a family of 13 AI." The eighteen accounts are all in that comment section if anyone wants to check the primary material. Disclosure, since it came up last time: I work on posts like this with an AI assistant. I bring the content, it helps me structure it.