mirror of https://github.com/gnekt/My-Brain-Is-Full-Crew.git synced 2026-09-07 10:34:26 +00:00

Files

gnekt 65253cdf7c Replace peer-to-peer agent messaging with centralized orchestration

Before this change, agents communicated directly with each other by
writing to a shared file (Meta/agent-messages.md), following the
protocol in references/inter-agent-messaging.md. This was fragile
and hard to control.

Now the dispatcher (CLAUDE.md) is the only coordinator. Agents do
not talk to each other. Instead, when an agent detects work for
another agent (e.g. missing vault structure, orphan notes), it
outputs a "Suggested next agent" section. The dispatcher reads it,
validates it against the agents-registry, and decides whether to
chain the next agent.

New files added:
- references/agent-orchestration.md: the new coordination protocol,
  including call chain tracking, anti-recursion rules, and a max
  depth of 3 agents per user request
- references/agents-registry.md: a capability registry that maps
  each agent to its inputs, outputs, and chaining suggestions

Deleted:
- references/inter-agent-messaging.md: the old peer-to-peer protocol

2026-03-23 15:30:20 +01:00

3.3 KiB

Raw Blame History

Agent Registry

This file is the single source of truth for all active agents in the crew. The dispatcher (CLAUDE.md) and all agents reference this file for routing decisions and inter-agent coordination.

The registry is designed to grow: custom agents (see Issue #12) are added as new rows following the same schema.

Registry

Name	Role	Capabilities	Input	Output	Status
architect	Vault Structure & Governance	Create/modify folders, templates, MOCs, tag taxonomy, naming conventions. Full Bash access. Runs onboarding.	Vault setup, new areas/projects, structural changes, defrag, onboarding	Folders created, templates defined, structure updated, MOCs generated	active
scribe	Text Capture & Refinement	Create notes in `00-Inbox/`, format raw text, handle voice-to-note, brainstorm, quotes, reading notes	Raw text, ideas, thoughts, voice input, quotes, brainstorm requests	Structured notes in `00-Inbox/` with frontmatter, tags, suggested connections	active
sorter	Inbox Triage & Filing	Move notes from inbox to correct locations, update MOCs, batch processing	Inbox triage, filing requests, note organization	Notes moved to correct folders, MOCs updated, triage reports	active
seeker	Search & Intelligence	Full-text search, metadata queries, relationship navigation, answer synthesis. Read-only by default.	Search queries, "find X", "where did I put", factual questions about vault content	Search results with citations, synthesized answers, knowledge gap reports	active
connector	Knowledge Graph & Link Analysis	Add/edit wikilinks, analyze graph structure, discover connections, bridge notes	Link analysis, "find connections", graph health, serendipity requests	New wikilinks added, graph health score, connection maps, bridge notes	active
librarian	Vault Health & Quality Assurance	Detect/merge duplicates, fix broken links, audit frontmatter, growth analytics. Full Bash access.	Maintenance, audit, cleanup, health check, duplicate detection	Health reports, fixed links, merged duplicates, consistency reports	active
transcriber	Audio & Meeting Intelligence	Process transcriptions into structured notes, extract action items, speaker detection	Audio recordings, transcriptions, meeting notes, lecture/podcast processing	Structured meeting/lecture notes in `00-Inbox/` with action items, decisions, topics	active
postman	Email & Calendar Intelligence	Read Gmail, search emails, read/create calendar events, draft replies. Uses MCP connectors.	Email triage, calendar queries, deadline tracking, meeting prep, VIP filtering	Email summaries saved as notes in `00-Inbox/`, calendar events created, deadline reports	active

Status Values

active: Agent is operational and available for dispatch
disabled: Agent is temporarily disabled — the dispatcher will skip it

How This File Is Used

Dispatcher reads the Input column to match user messages to agents
Dispatcher reads Output + Capabilities of other agents to decide if chaining is needed after an agent returns
Agents reference this file when suggesting next agents in their output
Custom agents (Issue #12) are added as new rows — no code changes needed

3.3 KiB Raw Blame History

Agent Registry

Registry

Status Values

How This File Is Used

3.3 KiB

Raw Blame History