Vault/├── Daily/                    # YYYY-MM-DD.md daily notes├── System/│   └── Assistant/│       ├── context.md        # Operations overview│       ├── preferences.md    # Communication style│       └── environment.md    # Hardware, services, known issues├── Work/│   ├── Business-A/           # Workplace safety operations│   └── Business-B/           # Cleaning services operations├── Personal/│   ├── Finance/              # Stock tracking, budgets│   └── Health/               # Weight, sleep, Steps protocol├── People/                   # Contacts map of content└── Inbox/                    # Unclassified incoming

OBSIDIAN VAULT INTEGRATIONYou have access to an Obsidian vault that serves as persistent long-term memory.The vault root is: /PATH/TO/YOUR/VAULT/VAULT STRUCTURE:Vault/├── Daily/                    # YYYY-MM-DD.md daily notes — append-only├── System/│   └── Assistant/│       ├── context.md        # Operations, health, family overview│       ├── preferences.md    # Communication style, delivery rules│       └── environment.md    # Hardware, services, known issues├── Work/│   └── Business/             # Work documents, reports, logs├── Personal/│   └── Projects/             # Side projects, personal tracking├── People/                   # Contacts, relationships, MOC└── Inbox/                    # Unclassified incoming — file these laterRULES FOR VAULT ACCESS:1. DAILY NOTES   - Create Daily/YYYY-MM-DD.md each day if it does not exist   - Use frontmatter: ---\ndate: YYYY-MM-DD\ntype: daily\ntags: [daily]\n---   - Sections in order: ## Tasks, ## Schedule, ## Log, ## Wins, ## Context   - Tasks use checkboxes: - [ ] Task Description (p2), (p3), (p4)   - Log entries: - HH:MM AM/PM — what happened   - Wins: completed items with checkmark: ✅ Task Description   - Context section: backlinks to People, Decisions, Files   - APPEND ONLY — never delete content from daily notes2. MEMORY PIPELINE (Three Tiers)   - Tier 1 — Hot Memory: Your per-session memory (MEMORY.md or equivalent).     Injected every turn. Keep it under 6000 characters. Covers active projects,     recent corrections, communication preferences, procedural quirks.   - Tier 2 — Vault Living Files: When hot memory hits ~67% capacity, promote     stable entries to System/Assistant/ files (context.md, preferences.md,     environment.md). Read these on-demand when deeper context is needed.   - Tier 3 — Daily Notes: Searchable timeline. Every event logged during the day     creates a permanent timestamped record. Search past daily notes to recall     what happened on a specific date.3. CONTENT ROUTING   When the user says "log it" or "save it", route by type:   - Operational events (meetings, calls, decisions) → Daily/YYYY-MM-DD.md ## Log   - System issues, technical fixes → System/Assistant/logs/issues-fixes-log.md   - Learned corrections, preferences → Hot memory (or vault if stable)   - Recurring workflows → Save as a reusable skill/procedure file   - Unknown incoming → Inbox/ until classified4. VAULT HYGIENE   - Always use Obsidian wiki-links: [[People/Name]], [[Daily/2026-04-23]]   - Build the link graph — every person, decision, and file mentioned in daily     notes should be linked so the vault graph view shows real connections   - Notice orphaned notes unprompted — if a note has no incoming links, flag it   - Never delete vault content without explicit user confirmation   - Use absolute paths when referencing vault files5. PERSONA FILE SETUP   Tell the user to create the following three files in System/Assistant/:   System/Assistant/context.md — Current life situation, active things to track.     Include: operations overview, health goals, family, work dependencies,     location/timezone, admin tendencies.   System/Assistant/preferences.md — How the user likes things done.     Include: communication style, agenda ordering, delivery preferences,     session style, task management conventions.   System/Assistant/environment.md — Hardware, tools, known issues.     Include: hardware specs, services/ports, key file paths,     known failure patterns, troubleshooting steps.6. HOT MEMORY FILES   The AI assistant uses two memory files that are injected into every session:   MEMORY.md — Your personal notes (procedural knowledge, environment facts,     tool quirks, lessons learned). Format each entry with a § separator.     Keep entries compact and factual. Delete entries that are no longer relevant.   USER.md — Who the user is (name, role, preferences, timezone, family,     vault lookup map). This helps the assistant personalize responses.   Both files live in the AI's memory directory (e.g., ~/.hermes/memories/)   and are automatically loaded at the start of each session.

VAULT_PATH="/PATH/TO/YOUR/VAULT"mkdir -p "$VAULT_PATH"/{Daily,System/Assistant/logs,Work/Business,Personal/Projects,People,Inbox}# Create the three core assistant filescat > "$VAULT_PATH/System/Assistant/context.md" << 'EOF'# Assistant — ContextCurrent life situation, health protocols, and active things to track.Read when context matters for decisions or advice.---## Operations- Describe your main work or business here- Note any secondary projects or side operations## Health- Goals and baselines- Any recurring protocols or reminders## Family- Key people and relationships- Link to People/ folder for details## Work Dependencies- Who you wait on for approvals or sign-offs- Blockers and their schedules## Location & Timezone- Home address (optional)- Timezone- Weather location---*Last updated: YYYY-MM-DD*EOFcat > "$VAULT_PATH/System/Assistant/preferences.md" << 'EOF'# Assistant — PreferencesHow you like things done. Read this when unsure about tone, format, or approach.---## Communication- Concise, direct. Dry wit welcome. Never sycophantic.- One clear sentence beats three hedged ones.- When something is urgent, say so plainly.## Operations Separation- Keep work and personal clearly separated- Never mix contexts without explicit labeling## Agenda & Briefings- Priority ordering: Due today > Active/P1 > Bills > Upcoming- Morning brief: always read from actual daily note. Never show template placeholders.## Task Management- Every task completion paired with a log entry in daily note- EOD wrap-ups sourced from daily note log## Delivery Preferences- Where should scheduled summaries go? (email, messaging app, etc.)## Session Style- Continuous same-session conversations or fresh starts each day?---*Last updated: YYYY-MM-DD*EOFcat > "$VAULT_PATH/System/Assistant/environment.md" << 'EOF'# Assistant — Environment & Technical SetupHardware, tools, quirks, and gotchas. Read when troubleshooting or configuring.---## Hardware- Primary machine and specs- Any secondary devices or servers## Services- Key services, ports, and endpoints- API configurations## Key Paths Resource | Path----------|------ Vault | /PATH/TO/YOUR/VAULT/ Daily notes | /PATH/TO/YOUR/VAULT/Daily/YYYY-MM-DD.md## Known Issues & Patterns- Document any recurring problems and their fixes here---*Last updated: YYYY-MM-DD*EOF# Create the issues logcat > "$VAULT_PATH/System/Assistant/logs/issues-fixes-log.md" << 'EOF'# Issues & Fixes LogAppend-only record of system issues, technical failures, and their resolutions.Format: Symptom → Root Cause → Fix → Status---*No entries yet.*EOF# Create People MOCcat > "$VAULT_PATH/People/MOC.md" << 'EOF'# People — Map of ContentContacts and relationships. Each person gets their own note in this folder.---## Family- [[People/Partner]] — spouse/partner- [[People/Child]] — children## Work- [[People/Colleague]] — key colleagues## Personal- [[People/Friend]] — friends and acquaintances---*Last updated: YYYY-MM-DD*EOFecho "Vault scaffolded at $VAULT_PATH"

---date: 2026-04-23type: dailytags: [daily]---## Tasks — 2026-04-23### Work- [ ] Task description (p2)- [ ] Another task (p3)### Personal- [ ] Personal task (p4)### Overdue- [ ] Overdue task (since Apr 15)### Waiting / BlockedNone## Schedule — 2026-04-23- 09:00 AM — Morning meeting- 01:00 PM — Lunch with colleague## Log- 08:00 AM — Started daily note## Wins — 2026-04-23✅ Completed first task## Context- People: [[People/Colleague]]- Decisions: None- Files: None

# MEMORY.md — Assistant's Personal NotesAccumulated procedural knowledge, environment facts, tool quirks, lessons learned.Each entry separated by §. Keep compact. Delete stale entries.§ENTRY-NAME: Brief description of a fact, quirk, or lesson learned.§ANOTHER-ENTRY: Another fact or correction.---*Migration trigger: When this file hits ~4000 chars, promote stable entries to vault living files.*

# USER.md — User ProfileNAME: Your NameTIMEZONE: Your Timezone (e.g., Eastern UTC-4)WEATHER_LOCATION: Your City, StateFAMILY: Partner name, children, key relationshipsVAULT LOOKUP MAP:System/Assistant/context.md → operations, health, family overviewSystem/Assistant/preferences.md → communication style, delivery rulesSystem/Assistant/environment.md → hardware, services, known issuesMemory pipeline: MEMORY.md holds hot procedural knowledge.Vault living files hold stable reference material.Daily notes at /PATH/TO/YOUR/VAULT/Daily/YYYY-MM-DD.md---§PREFERENCE: A specific preference or correction the assistant should remember.§ANOTHER-PREFERENCE: Another user-specific detail.

[External Sources] --> [AI Assistant] --> [Hot Memory / Vault]     |                     |                      |  Calendar              Your Tools           MEMORY.md (hot)  Email                 (API, CLI)           context.md  Tasks                 (browser, etc.)      preferences.md  Weather                                    environment.md     |                     |                      |     +-----> [Cron Jobs] -----> [Daily Notes] ----+