Original Reddit post

I’ve got a few major reconciliation and scoping projects I’ve been driving with Claude from the terminal. Lately, I’ve been spotting a LOT more assumptions and forgotten facts. This must just be where the structure and limits of memory files begin to have problems, especially when softer (not code or mathematical) information. After having Claude brainstorm a solution, it suggested a facts.yaml schema to hold truths with dates and reasons. I’m not on the third project where this has been needed to keep things grounded and consistent. If this helps anyone, great! If anyone with more knowledge than me knows if there’s even better ways to solve for this, please let me know! I suppose this is sort of a middle-ground between memory and a DB? Always looking to increase consistency so please, educate me! submitted by /u/Cultural-Horse-762

Originally posted by u/Cultural-Horse-762 on r/ClaudeCode