avi/Orion
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
Orion/3. Resources/Research/workflows/Polaris Vault Workflow.md
Avi a66996ac10 Orion vault — clean initial history 
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.
2026-10-02 08:34:48 -05:00

2.6 KiB
Raw Permalink Blame History

last-updated hermes-owned
2026-09-25T23:30:00-05:00 true

Polaris Vault Workflow

Standing directive (2026-09-25): new projects should operate like the Polaris / orion boilerplate — a plain-markdown, agent-maintained knowledge vault. Avi asked for "the full process of how I should guide you in following this boilerplate for new projects." Live instance: /home/avi/Projects/Polaris/ (boilerplate from github.com/kyleisuncool/orion-boilerplate).

Structure

  • 0. Inbox/ — everything lands here first; goal is to get it OUT (daily notes live here).
  • 1. Projects/ — active work; every project needs a "done when" sentence.
  • 2. Areas/ — long-lived responsibilities; a finished project hands its knowledge back to an Area.
  • 3. Resources/ — things collected while working (PDFs, references); projects reference them.
  • 4. Decisions/ — decisions noted during work, cross-linked, hanging threads resolved here.
  • 5. Archive/ — only moved when told; reversible (resume X restores context).
  • 6. Templates/ — reusable document shapes (daily note, decision, contracts, hubs) to minimize token use.
  • wiki/ — hot.md = current 360° state; index.md, log.md (log folds every ~22 entries into compacted lines).
  • AGENTS.md = the rulebook; skills in .agents/skills/: ingest, cascade, archive, close, daily, fold, skeleton, lint.

Commands (say to the agent)

Say Effect
new area: X / new project: X Creates hub against its contract
ingest Files everything in Inbox: people, decisions, updates, references
cascade Rewrites wiki/hot.md with everything learned this session, logs it
daily note Closes today's note, writes tomorrow's
weekly sweep One-line list of everything tracked
close workstream: X Finished project hands deliverable back to its Area
archive: X / resume X Retire/restore an Area
lint Health check: dead links, missing fields, overdue follow-ups

Key conventions from the boilerplate walkthrough

  • Inbox → process → Projects (active) → Areas (retained knowledge) → Archive (done, retained, no usage penalty).
  • Deliverable flow: build artifact in the code repo, HTML → PDF via browser, put in Outbox, note who it went to + channel + where.
  • Inbox and Outbox exist per-machine (desktop + Nextcloud); bring-in docs go to project folder + Resources, with extracted summary + text-by-text copies in-vault.
  • Purpose: minimize token usage per session — keep reproducible templates, compacted logs, deep recall only on request.

Related: User Preferences · Keynctr Dev Loop · Decisions Log (legacy) (D-2026-120)