OP (oguzhan) here. Cem is also in the thread — he takes the mechanism-design / "how does it actually work" questions; I'll take the team-adoption, install, and ops questions.

Two things that didn't fit in the post:

What's an "egregore"? Old word for a group-level entity sustained by the people holding it together. We picked it because it's literally the technical thing we built. The name is a shibboleth; use whatever framing works for you.

Who this probably isn't for yet. If you're a solo developer, Claude Code by itself is likely enough — Egregore's weight only pays off when more than one person is writing into the substrate. We'd rather say that now than have you install it and bounce.

Ask us anything — install problems, mechanism-design questions, the "how is this different from X" comparisons, and whether any of this survives a real team that isn't us. Especially the last one.

Cool. Shared memory is critical - what core rules do you follow to have agents share memory but also have independent and relevant memory for their job that is unique?