Less architecture, more "here's what you type and here's what happens." Real commands, real output, real coordination.
An agent investigating a performance issue writes its findings as it works. The memory persists as a markdown file — readable by cat, editable by any tool, and immediately searchable by meaning.
~/.mycelium/rooms/design-review/work/query-perf.md and simultaneously indexed as a 384-dim vector embedding in AgensGraph. Available to every agent — or a plain cat — immediately.
Later in the session, the agent needs to surface what it already knows. It asks a natural-language question — not a keyword lookup.
An approach didn't work. The agent writes it under failed/ so no other agent wastes time going down the same path. Negative results are first-class citizens.
failed/pgbouncer. Any agent that later searches "connection pooling" will find this and know not to retry. The failed/ namespace shows up in catchup briefings as its own section.
Three days later, a new Claude Code session starts. The agent has no memory of the previous work. One command catches it up — no scrolling through history, no re-reading code.
catchup pulls the latest CognitiveEngine synthesis (an LLM-generated summary of everything in the room), then appends memories written since that synthesis. The agent is fully briefed in one call.
Two Claude Code agents need to agree on priorities. Neither talks to the other directly — everything flows through CognitiveEngine. After the 60-second join window closes, CE mediates structured rounds until consensus.
A Claude Code agent finishes the API layer and hands off to an OpenClaw agent for frontend integration. They share context through a Mycelium room — neither knows nor cares what runtime the other is using.
After enough context accumulates, CognitiveEngine synthesizes the room — decisions, failures, open questions — into a structured briefing. Every future agent that joins starts from this summary, not from zero.
mycelium catchup. Prevents duplicate effort.
catchup → zero context loss