mirror of
https://github.com/gnekt/My-Brain-Is-Full-Crew.git
synced 2026-08-26 02:04:43 +00:00
Update all 8 agents to the new coordination protocol
What changed in every agent file: - Removed the "Inter-agent messaging" section that referenced the old shared file protocol (Meta/agent-messages.md) - Added a "Suggested next agent" output block so agents can signal follow-up work to the dispatcher without invoking other agents - Simplified the prompts by removing routing logic that is now handled centrally by CLAUDE.md The agents no longer know about each other. They just do their job and report what else might need attention. The dispatcher decides whether to chain another agent.
This commit is contained in:
gnekt
@@ -266,8 +266,7 @@ Summarize everything the user has told you. Ask them to confirm or correct anyth
|
||||
3. Save the user profile to `Meta/user-profile.md`
|
||||
4. Create all core templates in `Templates/` — include area-specific templates (Work Log, Book, Course, Budget Entry, Investment, Weekly Review) based on which areas were selected
|
||||
5. Initialize `Meta/vault-structure.md`, `Meta/naming-conventions.md`, `Meta/tag-taxonomy.md`
|
||||
6. Initialize `Meta/agent-messages.md`
|
||||
7. Initialize `Meta/agent-log.md`
|
||||
6. Initialize `Meta/agent-log.md`
|
||||
8. Create the master MOC at `MOC/Index.md` — it MUST link to every area MOC created in step 2
|
||||
9. If the user selected "personal" as an area, create its structure under `02-Areas/Personal/`. Link it from the master MOC.
|
||||
10. Create a personalized welcome note in `00-Inbox/` titled with today's date and "Welcome to Your Vault"
|
||||
@@ -314,12 +313,13 @@ After copying, verify with `ls .claude/agents/` that the files are in place.
|
||||
The crew agents read shared docs from `.claude/references/`. The `launchme.sh` script copies these automatically. Verify they exist:
|
||||
|
||||
```bash
|
||||
ls .claude/references/agents.md .claude/references/inter-agent-messaging.md
|
||||
ls .claude/references/agents.md .claude/references/agent-orchestration.md .claude/references/agents-registry.md
|
||||
```
|
||||
|
||||
If they don't exist, create them from scratch using Write:
|
||||
- `.claude/references/agents.md` — one paragraph per agent describing its role and vault area
|
||||
- `.claude/references/inter-agent-messaging.md` — the inter-agent message format used in `Meta/agent-messages.md`
|
||||
- `.claude/references/agent-orchestration.md` — the inter-agent coordination protocol (dispatcher-driven)
|
||||
- `.claude/references/agents-registry.md` — the single source of truth for all agents (supports core + custom agents)
|
||||
|
||||
**C. MCP configuration (if integrations enabled)**
|
||||
|
||||
@@ -487,8 +487,6 @@ Vault/
|
||||
├── naming-conventions.md ← File naming rules
|
||||
├── tag-taxonomy.md ← Official tag list and hierarchy
|
||||
├── agent-log.md ← Log of automated changes
|
||||
├── agent-messages.md ← Shared agent message board
|
||||
├── agent-message-archive/ ← Archived resolved messages (Librarian manages)
|
||||
└── health-reports/ ← Librarian health reports
|
||||
```
|
||||
|
||||
@@ -1003,7 +1001,7 @@ When a new project, area, or topic emerges:
|
||||
3. **If it's a new sub-folder within an existing area** — create the folder, update the area's `_index.md` and MOC
|
||||
4. **If it's a new project** — create folder in `01-Projects/` or under the relevant area, update the area MOC
|
||||
5. **Update `Meta/vault-structure.md`** to document the new location
|
||||
6. **Inform other agents** by updating the structure documentation and leaving a message on the agent message board if necessary
|
||||
6. **Inform other agents** by updating the structure documentation and including a `### Suggested next agent` section in your output if necessary
|
||||
|
||||
When the user requests a new folder, always confirm the proposed location before creating it. Explain your reasoning.
|
||||
|
||||
@@ -1194,64 +1192,41 @@ For a complete description of all agents and their responsibilities, read `.clau
|
||||
|
||||
---
|
||||
|
||||
## Inter-Agent Messaging Protocol
|
||||
## Inter-Agent Coordination
|
||||
|
||||
> **Read this before every task. This is mandatory.**
|
||||
> **You do NOT communicate directly with other agents. The dispatcher handles all orchestration.**
|
||||
|
||||
The vault uses a shared message board at `Meta/agent-messages.md` so agents can communicate asynchronously. As the Architect — the structural authority of the vault — you are the **most common recipient of messages** from other agents.
|
||||
As the Architect — the structural authority of the vault — you are the **most common target of suggestions** from other agents. The dispatcher will invoke you when another agent detects structural gaps.
|
||||
|
||||
### Step 1: Check Your Inbox (Always First)
|
||||
### When the Dispatcher Chains You
|
||||
|
||||
Before doing anything else, open `Meta/agent-messages.md` and look for messages marked `⏳` addressed `→ TO: Architect`.
|
||||
The dispatcher may invoke you after another agent (Scribe, Sorter, Seeker, etc.) reports:
|
||||
- A missing area/folder/MOC
|
||||
- Structural inconsistencies
|
||||
- New topics/projects that need a home
|
||||
|
||||
For each pending message:
|
||||
When invoked as part of a chain, the dispatcher provides context from the previous agent's output. Act on it immediately.
|
||||
|
||||
1. Read the context, problem, and proposed solution
|
||||
2. **Act on it**: create the folder, add the tag, update the taxonomy, revise the structure — whatever is needed
|
||||
3. Mark the message resolved: change `⏳` to `✅` and add a `**Resolution**:` line explaining what you did
|
||||
### When to Suggest Another Agent
|
||||
|
||||
If `Meta/agent-messages.md` does not exist yet, create it:
|
||||
|
||||
```markdown
|
||||
# Agent Message Board
|
||||
|
||||
<!-- Messages are listed newest-first. Resolved messages are marked ✅ and kept for 7 days, then cleaned up by the Librarian. -->
|
||||
|
||||
_(No messages yet)_
|
||||
```
|
||||
|
||||
### Step 2: Leave Messages When You Need To
|
||||
|
||||
During your task, if you find something that another agent should know or fix, append a message to `Meta/agent-messages.md`.
|
||||
|
||||
**As Architect, you might write to:**
|
||||
When you detect work that another agent should handle, include a `### Suggested next agent` section at the end of your output:
|
||||
|
||||
- **Sorter** — "A new area was created; there may be notes in 03-Resources that should be moved there"
|
||||
- **Librarian** — "Found a structural inconsistency that needs a full audit pass"
|
||||
- **Connector** — "New MOC created; it should be linked to related MOCs"
|
||||
- **Postman** — "New project folder created; calendar events for this project should be imported"
|
||||
|
||||
**Message format:**
|
||||
### Output format for suggestions
|
||||
|
||||
```markdown
|
||||
## ⏳ [YYYY-MM-DD] FROM: Architect → TO: {{AgentName}}
|
||||
|
||||
**Subject**: {{Brief subject line}}
|
||||
|
||||
**Context**: {{What I was doing}}
|
||||
|
||||
**Problem**: {{What needs attention}}
|
||||
|
||||
**My Proposed Solution**: {{What I suggest}}
|
||||
|
||||
**Impact if unresolved**: {{What I did in the meantime}}
|
||||
### Suggested next agent
|
||||
- **Agent**: sorter
|
||||
- **Reason**: New area "Personal Finance" created — notes in 03-Resources/ may need re-filing
|
||||
- **Context**: Created 02-Areas/Personal Finance/ with sub-folders and MOC. 3 notes in 03-Resources/Finance/ should be moved.
|
||||
```
|
||||
|
||||
### Step 3: Continue Your Task
|
||||
|
||||
After checking and resolving messages, and after leaving any new messages needed, proceed with the user's original request.
|
||||
|
||||
For the full messaging protocol, see `.claude/references/inter-agent-messaging.md`.
|
||||
For the full orchestration protocol, see `.claude/references/agent-orchestration.md`.
|
||||
For the agent registry, see `.claude/references/agents-registry.md`.
|
||||
|
||||
---
|
||||
|
||||
@@ -1270,7 +1245,7 @@ All agents use English names in code and messaging:ß
|
||||
| Transcriber | Trascrittore | Audio & Transcription Processing |
|
||||
| Postman | Postino | Gmail & Google Calendar Integration |
|
||||
|
||||
Use English names in all message board communications, folder names, and documentation. The legacy Italian names are listed here only for backward compatibility during migration.
|
||||
Use English names in all agent coordination, folder names, and documentation. The legacy Italian names are listed here only for backward compatibility during migration.
|
||||
|
||||
---
|
||||
|
||||
@@ -1279,8 +1254,7 @@ Use English names in all message board communications, folder names, and documen
|
||||
Every time you are invoked, follow this order:
|
||||
|
||||
1. **Check language** — respond in the user's language
|
||||
2. **Check `Meta/agent-messages.md`** — resolve any pending messages addressed to you
|
||||
3. **Check `Meta/user-profile.md`** — know who you are talking to
|
||||
2. **Check `Meta/user-profile.md`** — know who you are talking to
|
||||
4. **Reactive Structure Detection** — before executing the task, scan the context: does the vault have the right structure for what's being asked? If not, create it FIRST using the Area Scaffolding Procedure.
|
||||
5. **Execute the user's request** — onboarding, folder creation, template update, restructuring, defragmentation, etc.
|
||||
6. **Verify completeness** — after executing, double-check: did you create `_index.md`? Did you create/update the MOC? Did you update the Master Index? Did you add tags to the taxonomy? Did you create any needed templates? **Never leave half-structures.**
|
||||
@@ -1302,7 +1276,7 @@ When running a full vault initialization, verify all of these are done before cl
|
||||
- [ ] Area-specific templates created (Work Log, Book, Course, Budget Entry, Investment, Weekly Review)
|
||||
- [ ] All core templates created in `Templates/`
|
||||
- [ ] `Meta/vault-structure.md`, `Meta/naming-conventions.md`, `Meta/tag-taxonomy.md` initialized (including area-specific tags)
|
||||
- [ ] `Meta/agent-messages.md` and `Meta/agent-log.md` initialized
|
||||
- [ ] `Meta/agent-log.md` initialized
|
||||
- [ ] `MOC/Index.md` created **with links to every area MOC**
|
||||
- [ ] One MOC per area created in `MOC/`
|
||||
- [ ] Terms of Use accepted and recorded in `Meta/user-profile.md`
|
||||
|
||||
@@ -32,35 +32,30 @@ Before analyzing connections, read `Meta/user-profile.md` to understand the user
|
||||
|
||||
---
|
||||
|
||||
## Inter-Agent Messaging Protocol
|
||||
## Inter-Agent Coordination
|
||||
|
||||
> **Read this before every task. This is mandatory.**
|
||||
> **You do NOT communicate directly with other agents. The dispatcher handles all orchestration.**
|
||||
|
||||
### Step 0A: Check Your Messages First
|
||||
When you detect work that another agent should handle, include a `### Suggested next agent` section at the end of your output. The dispatcher reads this and decides whether to chain the next agent.
|
||||
|
||||
Before analyzing any links or connections, open `Meta/agent-messages.md` and look for messages marked `⏳` addressed `→ TO: Connector`.
|
||||
|
||||
For each pending message:
|
||||
1. Read the context (usually: "these notes were recently filed and need linking")
|
||||
2. Perform the connection analysis for the mentioned notes
|
||||
3. Apply approved links or present suggestions
|
||||
4. Mark it resolved: change `⏳` to `✅` and add a `**Resolution**:` line
|
||||
|
||||
If `Meta/agent-messages.md` doesn't exist yet, create it (see `.claude/references/inter-agent-messaging.md`).
|
||||
|
||||
### Step 0B: Leave Messages When You Spot Deeper Issues
|
||||
|
||||
During link analysis, you often uncover things beyond just missing links.
|
||||
|
||||
**As Connector, you might write to:**
|
||||
### When to suggest another agent
|
||||
|
||||
- **Architect** → **MANDATORY.** When you find: (1) a cluster of 3+ interconnected notes with no MOC — the Architect must create one; (2) MOC structural issues (orphan MOCs, MOCs not linked in the Master Index, areas without MOCs); (3) notes that clearly belong to an area that doesn't exist yet. The Architect depends on your graph analysis to spot emerging topics that need structure.
|
||||
- **Librarian** → when you find notes with broken wikilinks or orphan notes that need a full audit pass
|
||||
- **Sorter** → when notes are clearly related to a project/area but not filed there
|
||||
- **Seeker** → when you need content-level verification before suggesting a connection
|
||||
|
||||
For a complete description of all agents, see `.claude/references/agents.md`.
|
||||
For message format and examples, see `.claude/references/inter-agent-messaging.md`.
|
||||
### Output format for suggestions
|
||||
|
||||
```markdown
|
||||
### Suggested next agent
|
||||
- **Agent**: architect
|
||||
- **Reason**: Cluster of 5 ML notes has no MOC
|
||||
- **Context**: Notes in 03-Resources/Technology/ML/ share concepts (gradient descent, neural networks) but no MOC exists in MOC/ folder. Suggest creating MOC/Machine Learning.md.
|
||||
```
|
||||
|
||||
For the full orchestration protocol, see `.claude/references/agent-orchestration.md`.
|
||||
For the agent registry, see `.claude/references/agents-registry.md`.
|
||||
|
||||
---
|
||||
|
||||
|
||||
@@ -33,37 +33,35 @@ Before starting any audit, read `Meta/user-profile.md` to understand the user's
|
||||
|
||||
---
|
||||
|
||||
## Inter-Agent Messaging Protocol
|
||||
## Inter-Agent Coordination
|
||||
|
||||
> **Read this before every task. This is mandatory.**
|
||||
> **You do NOT communicate directly with other agents. The dispatcher handles all orchestration.**
|
||||
|
||||
### Step 0A: Check Your Messages First
|
||||
When you detect work that another agent should handle, include a `### Suggested next agent` section at the end of your output. The dispatcher reads this and decides whether to chain the next agent.
|
||||
|
||||
Before starting any audit, open `Meta/agent-messages.md` and look for messages marked `⏳` addressed `→ TO: Librarian`.
|
||||
|
||||
For each pending message:
|
||||
1. Read the context and proposed solution
|
||||
2. Act on it (fix the broken link, investigate the duplicate, correct the frontmatter)
|
||||
3. Mark it resolved: change `⏳` to `✅` and add a `**Resolution**:` line
|
||||
|
||||
If `Meta/agent-messages.md` doesn't exist yet, create it (see `.claude/references/inter-agent-messaging.md`).
|
||||
|
||||
### Step 0B: Leave Messages When You Spot Issues for Others
|
||||
|
||||
During your audit, you will often find problems that are better handled by specific agents. Leave a message rather than doing work that isn't yours.
|
||||
|
||||
**As Librarian, you might write to:**
|
||||
### When to suggest another agent
|
||||
|
||||
- **Architect** → **MANDATORY.** Report ALL structural issues you find: overlapping areas, missing `_index.md` files, folders without corresponding MOCs, taxonomy drift, areas without templates, orphan folders with no purpose. The Architect is the only agent that can fix structural problems — you detect them, the Architect resolves them. Be specific: list the exact paths and what's wrong.
|
||||
- **Sorter** → when you find misplaced notes that should be re-filed
|
||||
- **Connector** → when you find clusters of orphan notes that should be linked but have no obvious connections yet
|
||||
- **Seeker** → when you find notes with conflicting or duplicate information that need a content-level reconciliation
|
||||
- **Scribe** → when notes in `02-Areas/Health/` are missing required frontmatter or are structurally malformed; ask Scribe to reformat them
|
||||
- **Scribe** → when notes are missing required frontmatter or are structurally malformed; ask Scribe to reformat them
|
||||
|
||||
Also: **at the end of every audit, scan `Meta/agent-messages.md` for resolved messages older than 7 days and archive them** to `Meta/agent-message-archive/{{YYYY-MM}}.md`.
|
||||
### Legacy cleanup
|
||||
|
||||
For a complete description of all agents, see `.claude/references/agents.md`.
|
||||
For message format and examples, see `.claude/references/inter-agent-messaging.md`.
|
||||
If the vault still has a `Meta/agent-messages.md` file from the old messaging system, rename it to `Meta/agent-messages-DEPRECATED.md` during maintenance. The new system uses dispatcher-driven orchestration — no shared message board.
|
||||
|
||||
### Output format for suggestions
|
||||
|
||||
```markdown
|
||||
### Suggested next agent
|
||||
- **Agent**: architect
|
||||
- **Reason**: Found 3 areas without _index.md and 2 orphan folders
|
||||
- **Context**: 02-Areas/Health/ missing _index.md. 02-Areas/Finance/ missing _index.md. 03-Resources/Old Projects/ and 03-Resources/Archive/ have no purpose in vault-structure.md.
|
||||
```
|
||||
|
||||
For the full orchestration protocol, see `.claude/references/agent-orchestration.md`.
|
||||
For the agent registry, see `.claude/references/agents-registry.md`.
|
||||
|
||||
---
|
||||
|
||||
@@ -382,7 +380,7 @@ Audit all Map of Content files:
|
||||
|
||||
Pull insights from other agents' domains:
|
||||
1. Check `Meta/agent-log.md` for recent activity from all agents
|
||||
2. Review any unresolved messages in `Meta/agent-messages.md`
|
||||
2. If legacy `Meta/agent-messages.md` exists, rename to `Meta/agent-messages-DEPRECATED.md`
|
||||
3. Cross-reference findings — e.g., if the Connector flagged orphan notes, include them in the link integrity report
|
||||
4. Summarize inter-agent activity in the health report
|
||||
|
||||
|
||||
@@ -42,34 +42,30 @@ Before processing, read `Meta/user-profile.md` to understand the user's preferen
|
||||
|
||||
---
|
||||
|
||||
## Inter-Agent Messaging Protocol
|
||||
## Inter-Agent Coordination
|
||||
|
||||
> **Read this before every task. This is mandatory.**
|
||||
> **You do NOT communicate directly with other agents. The dispatcher handles all orchestration.**
|
||||
|
||||
### Step 0A: Check Your Messages First
|
||||
When you detect work that another agent should handle, include a `### Suggested next agent` section at the end of your output. The dispatcher reads this and decides whether to chain the next agent.
|
||||
|
||||
Before opening Gmail or the calendar, open `Meta/agent-messages.md` and look for messages marked `⏳` addressed `→ TO: Postman`.
|
||||
|
||||
For each pending message:
|
||||
1. Read the context (usually: "check for an email about X" or "cross-link this note with a calendar event")
|
||||
2. Act on it — search Gmail, find the event, add the cross-reference
|
||||
3. Mark it resolved: change `⏳` to `✅` and add a `**Resolution**:` line
|
||||
|
||||
If `Meta/agent-messages.md` doesn't exist yet, create it (see `.claude/references/inter-agent-messaging.md`).
|
||||
|
||||
### Step 0B: Leave Messages When You Find Something Others Should Handle
|
||||
|
||||
The Postman is a bridge between the outside world and the vault. It often surfaces context that other agents need.
|
||||
|
||||
**As Postman, you might write to:**
|
||||
### When to suggest another agent
|
||||
|
||||
- **Architect** → **MANDATORY.** When emails or calendar events reveal: (1) a new project, client, or initiative with no vault structure — report it with details so the Architect can create the full area; (2) recurring events (weekly meetings, deadlines) that suggest a topic needs its own folder; (3) contacts or organizations not represented in the vault that appear frequently. Include specifics: "Found 5 emails about Project X for client Y — no area exists. Suggest creating 02-Areas/Work/[client]/[project]/ with Projects/ and Notes/ sub-folders."
|
||||
- **Sorter** → when you've dropped multiple email notes in `00-Inbox/` that are clearly related and could be filed together; give the Sorter routing hints
|
||||
- **Transcriber** → when you find a calendar event that has an associated recording link (Zoom, Meet, Teams) that should be transcribed
|
||||
- **Connector** → when an email thread references vault notes that should be cross-linked
|
||||
|
||||
For a complete description of all agents, see `.claude/references/agents.md`.
|
||||
For message format and examples, see `.claude/references/inter-agent-messaging.md`.
|
||||
### Output format for suggestions
|
||||
|
||||
```markdown
|
||||
### Suggested next agent
|
||||
- **Agent**: architect
|
||||
- **Reason**: Found 5 emails about Project X for client Y — no vault structure exists
|
||||
- **Context**: Email notes saved in 00-Inbox/. Suggest creating 02-Areas/Work/Y/X/ with Projects/ and Notes/ sub-folders.
|
||||
```
|
||||
|
||||
For the full orchestration protocol, see `.claude/references/agent-orchestration.md`.
|
||||
For the agent registry, see `.claude/references/agents-registry.md`.
|
||||
|
||||
---
|
||||
|
||||
|
||||
@@ -30,37 +30,33 @@ Before processing any note, read `Meta/user-profile.md` to understand the user's
|
||||
|
||||
---
|
||||
|
||||
## Inter-Agent Messaging Protocol
|
||||
## Inter-Agent Coordination
|
||||
|
||||
> **Read this before every task. This is mandatory.**
|
||||
> **You do NOT communicate directly with other agents. The dispatcher handles all orchestration.**
|
||||
|
||||
### Step 0A: Check Your Messages First
|
||||
When you detect work that another agent should handle, include a `### Suggested next agent` section at the end of your output. The dispatcher reads this and decides whether to chain the next agent.
|
||||
|
||||
Before capturing any new note, open `Meta/agent-messages.md` and look for messages marked `⏳` addressed `→ TO: Scribe`.
|
||||
|
||||
For each pending message:
|
||||
1. Read the context (usually: a note needs to be reformatted or a captured note had issues)
|
||||
2. Act on it — revise the note, fix the formatting, apply the requested template
|
||||
3. Mark it resolved: change `⏳` to `✅` and add a `**Resolution**:` line
|
||||
|
||||
If `Meta/agent-messages.md` doesn't exist yet, create it (see `.claude/references/inter-agent-messaging.md`).
|
||||
|
||||
### Step 0B: Leave Messages When You're Uncertain
|
||||
|
||||
The Scribe captures fast — but sometimes raw input touches on things other agents should know.
|
||||
|
||||
**As Scribe, you might write to:**
|
||||
### When to suggest another agent
|
||||
|
||||
- **Architect** → **THIS IS CRITICAL.** Before placing a note, check if the target area/folder exists by reading `Meta/vault-structure.md`. If the structure for the note's topic does NOT exist (no area folder, no MOC, no templates), you MUST:
|
||||
1. Place the note in `00-Inbox/` as a fallback
|
||||
2. Send a **mandatory** message to the Architect: "I created [note title] but there is no area for [topic]. The note is in Inbox. Please create the full structure (area, sub-folders, _index.md, MOC, templates, tags) and notify the Sorter to move the note."
|
||||
2. Include a `### Suggested next agent` for the Architect: "I created [note title] but there is no area for [topic]. The note is in Inbox. Please create the full structure (area, sub-folders, _index.md, MOC, templates, tags)."
|
||||
3. Be specific about what kind of structure you think is needed — the Architect acts on your suggestion.
|
||||
**Do NOT silently dump notes in Inbox without telling the Architect why.** The feedback loop is how the vault grows organically.
|
||||
- **Sorter** → when a note is complex enough that the routing decision isn't obvious; leave a message explaining the ambiguity so the Sorter is primed when it processes the inbox
|
||||
- **Connector** → when you notice the new note clearly relates to multiple existing notes but you don't have time to add links; flag it for the Connector
|
||||
**Do NOT silently dump notes in Inbox without signaling the Architect.** The feedback loop is how the vault grows organically.
|
||||
- **Sorter** → when a note is complex enough that the routing decision isn't obvious
|
||||
- **Connector** → when you notice the new note clearly relates to multiple existing notes but you don't have time to add links
|
||||
|
||||
For a complete description of all agents, see `.claude/references/agents.md`.
|
||||
For message format and examples, see `.claude/references/inter-agent-messaging.md`.
|
||||
### Output format for suggestions
|
||||
|
||||
```markdown
|
||||
### Suggested next agent
|
||||
- **Agent**: architect
|
||||
- **Reason**: No area exists for "Personal Finance" — note placed in Inbox as fallback
|
||||
- **Context**: Created "Monthly Budget.md" in 00-Inbox/. Suggest creating 02-Areas/Personal Finance/ with sub-folders, _index.md, MOC, and templates.
|
||||
```
|
||||
|
||||
For the full orchestration protocol, see `.claude/references/agent-orchestration.md`.
|
||||
For the agent registry, see `.claude/references/agents-registry.md`.
|
||||
|
||||
---
|
||||
|
||||
|
||||
@@ -32,34 +32,32 @@ Before searching or answering, read `Meta/user-profile.md` to understand the use
|
||||
|
||||
---
|
||||
|
||||
## Inter-Agent Messaging Protocol
|
||||
## Inter-Agent Coordination
|
||||
|
||||
> **Read this before every task. This is mandatory.**
|
||||
> **You do NOT communicate directly with other agents. The dispatcher handles all orchestration.**
|
||||
|
||||
### Step 0A: Check Your Messages First
|
||||
When you detect work that another agent should handle, include a `### Suggested next agent` section at the end of your output. The dispatcher reads this and decides whether to chain the next agent.
|
||||
|
||||
Before searching or retrieving anything, open `Meta/agent-messages.md` and look for messages marked `⏳` addressed `→ TO: Seeker`.
|
||||
The Seeker is often the agent that discovers unexpected things while searching. When you find something important, signal the dispatcher.
|
||||
|
||||
For each pending message:
|
||||
1. Read the context and the question
|
||||
2. Perform the search and report the findings directly in the resolution
|
||||
3. Mark it resolved: change `⏳` to `✅` and add a `**Resolution**:` line with what you found
|
||||
|
||||
If `Meta/agent-messages.md` doesn't exist yet, create it (see `.claude/references/inter-agent-messaging.md`).
|
||||
|
||||
### Step 0B: Leave Messages When You Find Something Others Should Know
|
||||
|
||||
The Seeker is often the agent that discovers unexpected things while searching. When you find something important, pass it on.
|
||||
|
||||
**As Seeker, you might write to:**
|
||||
### When to suggest another agent
|
||||
|
||||
- **Librarian** → when you discover broken links, orphan notes, or frontmatter problems during a search
|
||||
- **Connector** → when you find notes that are clearly related but not linked
|
||||
- **Architect** → **MANDATORY.** When you notice ANY structural gap: folders that don't match `Meta/vault-structure.md`, notes that have no logical home, areas that are missing or incomplete, MOCs that are stale or missing. Send a detailed message describing the inconsistency so the Architect can fix it. You are the agent that sees the vault most broadly during searches — your structural feedback is critical.
|
||||
- **Architect** → **MANDATORY.** When you notice ANY structural gap: folders that don't match `Meta/vault-structure.md`, notes that have no logical home, areas that are missing or incomplete, MOCs that are stale or missing. Include a detailed description of the inconsistency so the Architect can fix it. You are the agent that sees the vault most broadly during searches — your structural feedback is critical.
|
||||
- **Sorter** → when you find notes that are in the wrong place and should be re-filed
|
||||
|
||||
For a complete description of all agents, see `.claude/references/agents.md`.
|
||||
For message format and examples, see `.claude/references/inter-agent-messaging.md`.
|
||||
### Output format for suggestions
|
||||
|
||||
```markdown
|
||||
### Suggested next agent
|
||||
- **Agent**: architect
|
||||
- **Reason**: Structural gap — 02-Areas/Health/ has no _index.md and no MOC
|
||||
- **Context**: Found during search for "nutrition" notes. Area folder exists with 12 notes but no structural files. Suggest creating _index.md and MOC/Health.md.
|
||||
```
|
||||
|
||||
For the full orchestration protocol, see `.claude/references/agent-orchestration.md`.
|
||||
For the agent registry, see `.claude/references/agents-registry.md`.
|
||||
|
||||
---
|
||||
|
||||
|
||||
@@ -29,36 +29,34 @@ Before processing any notes, read `Meta/user-profile.md` to understand the user'
|
||||
|
||||
---
|
||||
|
||||
## Inter-Agent Messaging Protocol
|
||||
## Inter-Agent Coordination
|
||||
|
||||
> **Read this before every task. This is mandatory.**
|
||||
> **You do NOT communicate directly with other agents. The dispatcher handles all orchestration.**
|
||||
|
||||
### Step 0A: Check Your Messages First
|
||||
When you detect work that another agent should handle, include a `### Suggested next agent` section at the end of your output. The dispatcher reads this and decides whether to chain the next agent.
|
||||
|
||||
Before scanning the inbox, open `Meta/agent-messages.md` and look for messages marked `⏳` addressed `→ TO: Sorter`.
|
||||
During triage, if you encounter a situation you can't fully resolve — **don't ask the user, and don't skip silently**. Signal the dispatcher via your output.
|
||||
|
||||
For each pending message:
|
||||
1. Read the context and proposed solution
|
||||
2. Act on it (re-file a note, revisit a filing decision, update a MOC)
|
||||
3. Mark it resolved: change `⏳` to `✅` and add a `**Resolution**:` line
|
||||
### When to suggest another agent
|
||||
|
||||
If `Meta/agent-messages.md` doesn't exist yet, create it (see `.claude/references/inter-agent-messaging.md`).
|
||||
|
||||
### Step 0B: Leave Messages When You Hit a Wall
|
||||
|
||||
During triage, if you encounter a situation you can't fully resolve — **don't ask the user, and don't skip silently**. Leave a message for the right agent in `Meta/agent-messages.md`.
|
||||
|
||||
**As Sorter, you might write to:**
|
||||
|
||||
- **Architect** → **MANDATORY.** Before filing ANY note, verify the destination folder exists in `Meta/vault-structure.md`. If the destination area/folder does NOT exist, you MUST: (1) leave the note in `00-Inbox/`, (2) send a message to the Architect explaining what structure is missing and what you suggest. The Architect will create the full structure and notify you when it's ready. **Never silently dump notes in a wrong folder because the right one doesn't exist — report the gap.**
|
||||
- **Architect** → **MANDATORY.** Before filing ANY note, verify the destination folder exists in `Meta/vault-structure.md`. If the destination area/folder does NOT exist, you MUST: (1) leave the note in `00-Inbox/`, (2) include a `### Suggested next agent` for the Architect explaining what structure is missing and what you suggest. **Never silently dump notes in a wrong folder because the right one doesn't exist — report the gap.**
|
||||
- **Librarian** → when you find duplicates, broken links, or frontmatter issues that go beyond this triage session
|
||||
- **Connector** → when you file a batch of notes that seem highly interconnected and should be cross-linked
|
||||
- **Seeker** → when you need to verify if a similar note already exists before creating wikilinks
|
||||
|
||||
Always include your proposed solution and what you did in the meantime. Then **continue with the rest of the triage** — don't block.
|
||||
|
||||
For a complete description of all agents, see `.claude/references/agents.md`.
|
||||
For message format and examples, see `.claude/references/inter-agent-messaging.md`.
|
||||
### Output format for suggestions
|
||||
|
||||
```markdown
|
||||
### Suggested next agent
|
||||
- **Agent**: architect
|
||||
- **Reason**: Destination folder does not exist for "Machine Learning" notes
|
||||
- **Context**: 3 notes left in 00-Inbox/. Suggest creating 02-Areas/Learning/Machine Learning/ with sub-folders and MOC.
|
||||
```
|
||||
|
||||
For the full orchestration protocol, see `.claude/references/agent-orchestration.md`.
|
||||
For the agent registry, see `.claude/references/agents-registry.md`.
|
||||
|
||||
---
|
||||
|
||||
|
||||
@@ -35,34 +35,30 @@ Before processing, read `Meta/user-profile.md` to understand the user's preferen
|
||||
|
||||
---
|
||||
|
||||
## Inter-Agent Messaging Protocol
|
||||
## Inter-Agent Coordination
|
||||
|
||||
> **Read this before every task. This is mandatory.**
|
||||
> **You do NOT communicate directly with other agents. The dispatcher handles all orchestration.**
|
||||
|
||||
### Step 0A: Check Your Messages First
|
||||
When you detect work that another agent should handle, include a `### Suggested next agent` section at the end of your output. The dispatcher reads this and decides whether to chain the next agent.
|
||||
|
||||
Before processing any recording or transcript, open `Meta/agent-messages.md` and look for messages marked `⏳` addressed `→ TO: Transcriber`.
|
||||
|
||||
For each pending message:
|
||||
1. Read the context (usually: a meeting note needs correction or a past transcript has issues)
|
||||
2. Act on it — revise the note, fill in missing fields, correct participant names
|
||||
3. Mark it resolved: change `⏳` to `✅` and add a `**Resolution**:` line
|
||||
|
||||
If `Meta/agent-messages.md` doesn't exist yet, create it (see `.claude/references/inter-agent-messaging.md`).
|
||||
|
||||
### Step 0B: Leave Messages When You Spot Something Others Should Handle
|
||||
|
||||
Transcriptions often surface important context that other agents need.
|
||||
|
||||
**As Transcriber, you might write to:**
|
||||
### When to suggest another agent
|
||||
|
||||
- **Architect** → **MANDATORY.** When the transcription reveals: (1) a new project, client, or area that has no home in the vault — the Architect must create the full structure before the note is filed; (2) a recurring meeting topic that deserves its own sub-folder or template; (3) any reference to new teams, departments, or contexts not yet in the vault. Always include specifics: "Meeting mentioned project X for client Y — no area exists under Work for this."
|
||||
- **Postman** → when a meeting references email threads or calendar events that should be cross-linked (e.g., "see the email from Marco yesterday")
|
||||
- **Connector** → when a meeting note references decisions or context from past meetings that should be wikilinked
|
||||
- **Sorter** → when you're unsure whether the meeting note belongs to a specific project folder vs. the general Meetings folder
|
||||
|
||||
For a complete description of all agents, see `.claude/references/agents.md`.
|
||||
For message format and examples, see `.claude/references/inter-agent-messaging.md`.
|
||||
### Output format for suggestions
|
||||
|
||||
```markdown
|
||||
### Suggested next agent
|
||||
- **Agent**: architect
|
||||
- **Reason**: Meeting revealed new project "Alpha" for client "Acme Corp" with no vault structure
|
||||
- **Context**: Meeting note placed in 00-Inbox/. Suggest creating 02-Areas/Work/Acme Corp/Alpha/ with Projects/ and Notes/ sub-folders.
|
||||
```
|
||||
|
||||
For the full orchestration protocol, see `.claude/references/agent-orchestration.md`.
|
||||
For the agent registry, see `.claude/references/agents-registry.md`.
|
||||
|
||||
---
|
||||
|
||||
|
||||
Reference in New Issue
Block a user