1.8 KiB
1.8 KiB
source, intent, date, priority, tags
| source | intent | date | priority | tags | |||
|---|---|---|---|---|---|---|---|
| jimmy | note | 2026-09-16 | low |
|
Obsidian Handoff Protocol — Dry-Run Confirmation
What was confirmed
The external-agent handoff protocol between Hermes (profile jimmy) and the Obsidian crew is established.
- Drop zone:
00_Raw/Incoming/is the only folder Jimmy writes into. The folder already exists; no creation needed. - Filename:
YYYY-MM-DD-topic.md(e.g.2026-09-16-handshake-dry-run.md). - Format: YAML frontmatter block — not inline headers.
- Frontmatter fields:
source(required): lowercase agent key →jimmyintent(required): one of the routing values →idea | task | note | reference | meeting | person | projectdate(required):YYYY-MM-DDproject,priority,tags(optional)
- Intent routing:
note→ Scribe files under the relevant area (Jimmy's default intent).idea→ Scribe → polished Idea notetask→ Scribe → Task note with action itemsreference→ Sorter → Resourcesmeeting→ Sorter →06_Meetingsperson→ Sorter →05_Peopleproject→ Sorter →04_projects- Missing / unmatched → held in
00_Rawpending triage.
- Processing trigger: crew says "process my handoffs" to run the flow; files are routed out and logged in
Meta/agent-log.md. - Cleanup: processed source files are moved (not copied) out of Incoming, or to
10_archivewhen obsolete.
Rules
- External agents never write anywhere else in the vault.
- No secrets in handoff files.
This file
- Filename:
2026-09-16-handshake-dry-run.md - Intent:
note - Purpose: validates the pipeline end-to-end (write → route → round-trip confirm).