Redditor Crazy-Mountain6125 reports that a repo-resident 'memory vault' — 174 structured notes in docs/ typed as systems, decisions, and status, maintained over two months — is what let Claude Code build and sustain a solo SaaS past 1,000 users, after monolithic CLAUDE.md dumps failed as project memory. The web search did not retrieve the original post itself, so the specific figures (174 notes, 1,000 users, two months) rest on the case's evidence title and remain unverified. What the surrounding results do independently corroborate is the failure mode and the remedy pattern: multiple practitioners describe Claude Code losing project context between sessions ('brilliant code for 20 minutes, then forgets your database schema') and converging on structured in-repo markdown — layered CLAUDE.md plus MEMORY.md (potapov.dev), 'project truth files' read before every action (Show HN), a template vault with a pinned boot file (github.com/jaredrhod/ai-memory-vault), and a r/ClaudeCode thread explicitly about stopping CLAUDE.md from carrying all project context. Adjacent signals (a 713-commit solo Claude-built SaaS in 55 days; Boris Cherny citing ~4% of GitHub commits authored by Claude Code) confirm the solo-agent-built-SaaS phenomenon is real; whether this manual vault pattern spreads beyond one anecdote is unresolved.
Scott's canon already holds this position outright: Cognitive Git formalizes typed session-commits accumulating as project memory, the markdown-native-workflow and llm-navigated-wiki pages carry structured repo markdown displacing monolithic dumps, and bi-for-soft-data already adjudicates the manual-vs-automated curation axis this vault sits on — so the case is field repetition of a held claim, not a challenge, extension, or new arrival. LOW: a 0.17-ratio anonymous anecdote exemplifying the pattern he believes (and builds beyond) is the world agreeing again, and a non-consequential source offers no dated-receipts publishing play.
ip:framework.cognitive-gitdev:concept.llm-navigated-wikidev:concept.markdown-native-workflowip:framework.bi-for-soft-dataradar:karpathy-llm-wiki-adoptionradar:continuity-claude-code-decision-memoryradar:leo-markdown-coding-processradar:memctl-versioned-agent-memory
queries asked of Scott's wikis
- agent-maintained wiki repo memory markdown
- CLAUDE.md monolithic dump failure context drift
- structured notes taxonomy systems decisions status
- solo builder agent-coded SaaS production users
- manual curation versus automated memory capture
- long-lived project decision log agent harness
now 0 pts/hpeak 4 pts/hcomments 0/hpeers p33momentum: steady1 platformsage 190h
points/hour across evidence · reading as of 2026-10-12 02:59:37.977291+11:00 · deterministic, not a model opinion
2026-10-10T00:27:33Z
Fifth independent Reddit anecdote (urchinzhou) confirms decisions.md pattern for rejected-approach memory; corroboration now spans five failure modes (session-zero, decision-reversion, compaction loss, stale-correction, rejected-alternative amnesia) across solo/team/multi-business contexts with two shareable artifacts, but remains saturated at single-platform anecdote tier with zero velocity — the standard-practice displacement question is stalled.
2026-10-09T19:58:38Z
evidence attached: reddit.post.1x1odhr — Discussion of agents forgetting *why* decisions were made (rejected approaches), with top comment confirming 'decisions.md' pattern — directly corroborates the case's hypothesis that structured repo-resident decision memory displaces CLAUDE.md dumps.
2026-10-07T21:31:43Z
Fourth independent line (KTVSUN) is a released artifact — an MIT-licensed files-own-truth memory system run daily for months across businesses and inbox — so the pattern is now being packaged and shared, not merely described; but with every line still at zero traction the meaning shifts from 'recurs across failure modes' to 'real but niche practitioner practice with corroboration saturated at the anecdote tier,' and the standard-practice displacement question is unlikely to be answered by these dead threads.
2026-10-07T20:34:06Z
evidence attached: reddit.post.1x057wd — Second independent files-own-truth structured memory system for Claude, weakly corroborating that the pattern is spreading beyond one builder.
2026-10-07T06:47:03Z
Third independent line (1wzmhh0): a builder losing context to /compact converges on five plain files + an always-loaded index hook — the pattern now spans three distinct failure modes (session-zero, decision-reversion, compaction loss), broadening corroboration without acceleration since every line stays sub-visibility (0.0 pts/h, 6th percentile, single platform). Displacement-as-standard-practice vs fade-as-anecdotes remains the open question.
2026-10-07T06:29:22Z
evidence attached: reddit.post.1wzmhh0 — Independent builder hits compaction-induced memory loss and converges on structured plain-file memory — direct corroboration that file-based structured memory is displacing built-in compaction/CLAUDE.md dumps.
2026-10-04T07:45:06Z
The team-scale thread (1wx8vcm) is a genuinely independent second line: different author, team context, same monolithic-CLAUDE.md failure (agent reverts settled decisions whose reasons live in old PRs) with community convergence on the same remedy class (ADR-linked structured memory) — the pattern now recurs across solo and team practice, not just one anecdote, moving seed→corroborated. New anchor-post comments sharpen the open question rather than resolve it: the vault risks becoming a distributed dump and derived counts go stale, so displacement-as-standard-practice stays unresolved while heat stays low (0.33 pts/h, single platform, 0.25 anchor ratio; the hot agent-memory neighborhood with 60 open episodes dilutes rather than concentrates attention here).
2026-10-04T07:23:36Z
evidence attached: reddit.post.1wx8vcm — Team-scale report of monolithic CLAUDE.md failing (19 comments) plus the structured ADR-linked alternative is exactly the pattern-displacement evidence that case tests.
2026-10-03T18:35:27Z
grounded: known/low — Scott's canon already holds this position outright: Cognitive Git formalizes typed session-commits accumulating as project memory, the markdown-native-workflow
2026-10-03T18:27:05Z
case created — A concrete first-person practitioner artifact (174-note vault taxonomy, two months, real 1,000-user product, explicit CLAUDE.md failure mode) making a distinct manual-practice claim no existing open case covers — the memory cases on file are all tool/protocol releases, not this vault pattern — though its 0.17 upvote ratio keeps it a low-heat seed.