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.
1.6 KiB
| type | title | updated | tags | |
|---|---|---|---|---|
| reference | start here | 2026-10-01 |
|
Start here
Which Orion file, when. You only ever need one of these.
Right now, what's the status?
→ hot — one screen: what's owed, what's open, what's paused, what's waiting on you. First thing you open in any session.
I don't remember how this works
→ How this vault works — the commands (ingest, cascade, new project:, status, lint…) and the three rules. Read once, then use as a cheat sheet.
You're waiting on me for something?
→ open-questions — decisions only you can make, numbered. Answering these is your entire "maintenance" duty.
Where does a thing / note / project live?
→ index — the inventory: every Area, Project, person, decision, one line each.
Why is the agent doing it that way?
→ AGENTS — the rulebook the agent reads every session. Check here to confirm a rule; change rules here. (It should never need explaining twice — if it does, say so and it gets fixed.)
Starting a fresh agent on this vault?
→ Prompt - Orion Boilerplate — hand this to a new agent / fresh session so it picks up the system the way it was designed.
The daily loop
open: hot.md ← where I stand
work: drop notes in 0. Inbox/ · ask for things
end: say "cascade" ← agent updates hot, logs, commits
Everything else is reference. If a file isn't in this list, it's the agent's working area — you don't need it.