I'm going a bit broader with my system but it's similar. Instead of trying to predict future behavior, I'm focusing on capturing new, meaningful information, preparing it for human review (no fully automatic writes) and pairing with an ongoing review process, deduplication and treating it like a resource I manually curate (with help to make that easier of course).
I think context needs to be treated primarily globally with the addition of some project specific data. For example, my coding preferences don't change between projects, nor does my name. Other data like the company I work for can change, but infrequently and some values change frequently and are expected to.
I also use Claude Code a lot more for thinking or writing these days so there's less separation between topics than there are in separate repos.
I have one of these - it's awesome, I love it and I think it's an incredible success for a first hardware product. My takeaway from reading this is that caring about building a great product made a huge difference in how your first 500 units landed. Now the next batch gets to come with all those learnings.
I'm sure there will be more challenges as well but as long as you keep focusing on the experience you're delivering, I'm sure you'll continue to get past them
I think context needs to be treated primarily globally with the addition of some project specific data. For example, my coding preferences don't change between projects, nor does my name. Other data like the company I work for can change, but infrequently and some values change frequently and are expected to.
I also use Claude Code a lot more for thinking or writing these days so there's less separation between topics than there are in separate repos.