a66996ac10
Knowledge vault (Orion/PARA) migrated from the pre-Orion 484vault on 2026-10-01. Deliberately orphaned: prior history contained a plaintext password and stays local-only on branch archive/pre-boilerplate-history. Secrets and live Hermes state are gitignored.
52 lines
No EOL
1.8 KiB
Markdown
52 lines
No EOL
1.8 KiB
Markdown
---
|
|
type: meeting
|
|
date:
|
|
attendees: []
|
|
project:
|
|
status: raw
|
|
processed: false
|
|
---
|
|
|
|
# # {{title}}
|
|
|
|
## Raw Notes
|
|
(Paste your unedited notes here — hesitations, half-sentences, all of it)
|
|
|
|
## Hermes Processing Prompt
|
|
Copy everything below into Hermes along with the raw notes above.
|
|
|
|
You are processing a meeting note in my Knowledge Vault.
|
|
The vault structure is: 01-PROJECTS, 02-WORKFLOWS, 03-SKILLS,
|
|
04-SYSTEMS, 05-KNOWLEDGE, 06-DECISIONS, 07-TROUBLESHOOTING.
|
|
|
|
Do the following, in this order, and label each section clearly:
|
|
|
|
1. **DECISIONS** — Every decision made. Format: `decision | who | date`.
|
|
Cross-check against `06-DECISIONS` and flag anything that reverses
|
|
or contradicts a prior decision.
|
|
|
|
2. **ACTION ITEMS** — Table format: `owner | task | due date | project | status`.
|
|
Mark "UNASSIGNED" or "NO DATE" explicitly. Never guess an owner.
|
|
|
|
3. **PROJECT LINKS** — For each item, name the matching `01-PROJECTS` note.
|
|
If nothing matches, say "new project candidate."
|
|
|
|
4. **KNOWLEDGE** — Facts, findings, or learnings worth keeping forever.
|
|
These belong in `05-KNOWLEDGE`, not in the meeting note.
|
|
|
|
5. **TROUBLESHOOTING** — Any problem described with a cause or workaround.
|
|
These belong in `07-TROUBLESHOOTING`.
|
|
|
|
6. **OPEN QUESTIONS** — Unresolved threads, plus who can answer them.
|
|
|
|
7. **GAPS** — What's missing. Items with no owner, no date, decisions made
|
|
without the relevant person present, or topics that got dropped.
|
|
|
|
8. **MY FOLLOW-UPS** — Actions assigned to me only, ranked by urgency.
|
|
|
|
**Rules:**
|
|
- Flag any inference with `[INFERRED]`. Flag anything you're unsure of
|
|
with `[LOW CONFIDENCE]`. Do not invent due dates or names.
|
|
- Output the content as paste-ready markdown blocks, one per destination
|
|
folder, so I can file them without rewriting.
|
|
- End with a one-paragraph summary I can paste into a follow-up email. |