fjwood69

4 ms·

1.
by fjwood69 4mo ago
Got a bit carried away with the governance aspect.. and after lots of testing, I've published a whitepaper which I think you will find interesting. Link is in my profile.
2.
by fjwood69 4mo ago
Cheers — quite a bit more work going into that presently and extensive testing to back it up. Early finding: auto-extracted memory is no better than a hand-written doc. Human curation is the lever. Numbers at the top of the mori README.
3.
by fjwood69 4mo ago
It isn't the memory store.. that's entirely separate. But it complements the memory store by allowing the agents to pub / sub notifications. Has its uses!
4.
by fjwood69 4mo ago
Yes, the multi-agent governance takes a lot of solving.. thus far I've gotten Hermes writing to the same memory store that Claude code, antigravity, cursor, etc can all contribute, pull from, but it's taken a whole separate layer
5.
by fjwood69 4mo ago
sure they do.. but it's painful how to capture, what to capture, when to capture it.. where to put it.. how to make it 'useful'.. how to reinject it or make it accessible the harness makers may well come up with better means
6.
by fjwood69 4mo ago
about six weeks.. Pushed a v1.0 product with a huge list of v2.x enhancements and features inbound. to your point about asking Codex.. that's my /consult feature. spin out the current context in any number of ways to ask for advi
7.
by fjwood69 4mo ago
So I solved this by using NATS and letting each agent pub / sub to the shared message bus.. simple binary you can run anywhere and it's highly useful! Part of a broader tool I created - https://github.com/fjwood69