Multiplayer AI: one ICM, a whole team

Using ICM alone makes one person fast. Using it as a shared knowledge base makes a whole team fast and consistent.

I call it an organized organisation 😂

The hard part isn't the AI, it's conflict management. I enforce four steps in code, not prompts:

Resolve conflicts: Git or a shared drive, depending on the case
Permissions and visibility: who edits instructions vs. who edits data
Handle stale files: give new information dates and context
Full auditability: every request is logged

My setup today: 7 people on community-based research. I'm the maintainer (rules). Everyone else is a member (data). They can suggest rules, but I approve them. The AI even flags broken rules to me: "he wants to do this but can't, check it out".

Still unsolved: stale files. Expiry dates or events help, but assigning them when a file is created is the hard part. For now, expired files stay put, the AI traces linked files to infer why, and asks me when unsure. Every failure updates the rules.

If you're building team ICMs, I'd love to compare notes. Technical or not, message me. 🤝

43 comments

Multiplayer AI: one ICM, a whole team