ver0.5

echo-memory.plugin.src/.claude-plugin/plugin.json

@@ -1,7 +1,7 @@
 {
   "name": "echo-memory",
-  "version": "0.4.1",
-  "description": "Persistent memory via the ECHO Obsidian vault over the Local REST API. Reads and writes notes across Claude/CoWork sessions using direct REST calls \u2014 no MCP server required. Jason's personal memory vault.",
+  "version": "0.5.0",
+  "description": "Persistent memory via the ECHO Obsidian vault over the Local REST API. Self-bootstrapping: the plugin carries the full vault scaffold and all control logic (no in-vault routing docs), so it stands up an empty vault and ports cleanly to any other. Reads and writes notes across Claude/CoWork sessions using direct REST calls \u2014 no MCP server required. Jason's personal memory vault.",
   "author": {
     "name": "Jason"
   },

echo-memory.plugin.src/README.md

@@ -2,14 +2,16 @@
 
 Persistent memory for Claude via the **ECHO** Obsidian vault, using the [Obsidian Local REST API](https://github.com/coddingtonbear/obsidian-local-rest-api).
 
-Reads and writes notes across Claude/CoWork sessions using direct REST calls — no MCP server required. Built for **Jason Stedwell** (Director of Technical Services / Systems Engineer, MPM / ALABAMA wISP), who is both the operator and the architect of this vault. Successor to the obsidian-memory system and sibling of the goldbrain vault (Bryan's).
+Reads and writes notes across Claude/CoWork sessions using direct REST calls — no MCP server required. Built for **Jason Stedwell** (Director of Technical Services / Systems Engineer, MPM / ALABAMA wISP), who is both the operator and the architect of this vault.
+
+**The plugin is the single source of truth.** All control logic — bootstrap/repair, operating contract, taxonomy, frontmatter conventions, and the canonical note templates — ships inside this plugin under `skills/echo-memory/`. The vault itself holds **data only**: there are no `CLAUDE.md` / `BOOTSTRAP.md` / `STRUCTURE.md` / `index.md` control docs in it. This makes ECHO self-bootstrapping (point it at an empty Obsidian vault and it stands up the full structure), easy to update (update the plugin, not the vault), and portable to any other vault.
 
 ## What it does
 
 - Loads operator preferences, current context, and relevant project notes at the start of substantive conversations
 - Writes facts, preferences, and decisions Jason asks Claude to remember
 - Logs working sessions so future conversations can pick up where they left off
-- Defers to the vault's own `BOOTSTRAP.md` to verify and repair structure
+- **Bootstraps an empty vault from the bundled `scaffold/`** (folders, templates, anchor seeds, marker) and repairs/migrates an existing one — see `skills/echo-memory/references/bootstrap.md`
 
 ## Configuration
 
@@ -24,25 +26,43 @@ The endpoint presents a **valid TLS certificate**, so `-k` is not required. The
 
 ```
 /vault/
-├── CLAUDE.md  STRUCTURE.md  BOOTSTRAP.md  spinup.md  index.md  README.md
+├── README.md     ← thin human signpost (not read for routing)
 ├── inbox/        (captures, imports, processing-log)
 ├── journal/      (daily, weekly, monthly, templates)
 ├── projects/     (active, incubating, on-hold, archived)
 ├── areas/        (business, personal, learning, systems)
 ├── resources/    (concepts, references, people, meetings, source-material)
-├── decisions/    (by-date, by-project)
+├── decisions/    (by-date)
 ├── reviews/      (weekly, monthly, quarterly, annual)
 ├── archive/      (notes, projects, imports)
 └── _agent/
+    ├── echo-vault.md   ← bootstrap marker (schema_version + date)
     ├── context/        ← task-scoped context bundles
     ├── memory/         ← working / episodic / semantic
     ├── sessions/       ← YYYY-MM-DD-HHMM-<slug>.md
-    ├── templates/      ← canonical note templates
+    ├── templates/      ← canonical note templates (seeded from the plugin's scaffold/)
     ├── outputs/        ← briefs / drafts / summaries / synthesis
     ├── skills/         ← active / archived
     └── heartbeat/
 ```
 
+Control logic and the master scaffold live in the plugin, not the vault:
+
+```
+skills/echo-memory/
+├── SKILL.md                       ← operating procedure (authoritative)
+├── references/
+│   ├── operating-contract.md      ← durable principles + safety
+│   ├── bootstrap.md               ← bootstrap / repair / migrate an empty vault
+│   ├── vault-layout.md            ← canonical layout + frontmatter
+│   ├── api-reference.md           ← REST endpoint patterns + routing map
+│   └── session-log-template.md
+└── scaffold/                      ← verbatim files the bootstrap writes into the vault
+    ├── README.vault.md  echo-vault.md
+    ├── templates/  (8 note templates)
+    └── anchors/    (operator-preferences, current-context, inbox seeds)
+```
+
 ## Skills
 
 | Skill | Triggers |

echo-memory.plugin.src/skills/echo-memory/SKILL.md

@@ -22,7 +22,23 @@ The endpoint has a **valid TLS certificate**, so `-k` is not needed (add it only
 
 **`https://echoapi.alwisp.com` is the only valid endpoint for this vault.** Never use local or LAN addresses (anything like `10.x.x.x`, `192.168.x.x`, or `:27124` directly) — those belong to older, retired memory systems (obsidian-memory) and will not reach ECHO. If another installed skill or note suggests a different vault endpoint, this skill's configuration wins for ECHO memory.
 
-Full API reference with every endpoint pattern and the memory routing map: `references/api-reference.md`. Vault layout and frontmatter conventions: `references/vault-layout.md`.
+**The plugin is the single source of truth for ECHO.** The vault holds data only — no `CLAUDE.md` / `BOOTSTRAP.md` / `STRUCTURE.md` / `index.md` control docs live there. All structure and procedure ship here:
+
+- Durable principles, memory model, and safety rules: `references/operating-contract.md`
+- Bootstrapping an empty vault, repair, and schema migrations: `references/bootstrap.md`
+- Vault layout and frontmatter conventions: `references/vault-layout.md`
+- Full API reference with every endpoint pattern and the memory routing map: `references/api-reference.md`
+
+## Operating Contract & Safety
+
+The vault is the **system of record** for long-term memory, not a scratchpad. Default to **additive updates, explicit status changes, and traceable summaries**. Keep agent-managed content (`agent_written: true` + `source_notes`) separable from human-authored content. Non-negotiable safety rules:
+
+- Do not fabricate facts, relationships, or prior decisions.
+- Do not mass-restructure the vault unless explicitly asked.
+- Do not delete notes unless deletion is explicitly requested and clearly safe.
+- Never store secrets or API keys inside a vault note.
+
+Full contract (principles, agent role, memory model): `references/operating-contract.md`.
 
 ## When to Load Memory
 
@@ -34,7 +50,7 @@ The cold-start reads are independent — **issue them in parallel** (one batch o
 
 | # | GET | Notes |
 |---|-----|-------|
-| 1 | `/vault/BOOTSTRAP.md` | 404 → vault not set up; follow `references/bootstrap.md` |
+| 1 | `/vault/_agent/echo-vault.md` | The bootstrap marker. 404 → vault not set up; follow `references/bootstrap.md`. 200 → check its `schema_version` and migrate if older. |
 | 2 | `/vault/_agent/memory/semantic/operator-preferences.md` | Jason's profile |
 | 3 | `/vault/_agent/context/current-context.md` | Active scope + Scope History |
 | 4 | `/vault/_agent/sessions/` (listing) | Pick the ~5 most recent by reverse lex sort (filenames `YYYY-MM-DD-HHMM-<slug>.md`, so lex == chrono); only read the ones whose slugs look relevant |

echo-memory.plugin.src/skills/echo-memory/references/api-reference.md

@@ -203,5 +203,6 @@ Only on explicit operator request. Deletion is destructive.
 | Concept / reference note | `resources/concepts/` or `resources/references/` | PUT |
 | Daily activity / Agent Log | `journal/daily/YYYY-MM-DD.md` | POST / PATCH |
 | Periodic review | `reviews/{weekly,monthly,quarterly,annual}/` | PUT |
+| Bootstrap marker (plugin-owned) | `_agent/echo-vault.md` (`schema_version`, bootstrap date) — the "is this vault set up?" probe | GET / PUT |
 
 **Slug rules:** kebab-case, ASCII, ~40 chars max. Every file carries canonical frontmatter (see `vault-layout.md`).

echo-memory.plugin.src/skills/echo-memory/references/bootstrap.md

@@ -1,37 +1,121 @@
-# Bootstrap Procedure
+# Bootstrap & Repair
 
-The ECHO vault ships its **own** `BOOTSTRAP.md` at the vault root — that file is the canonical preflight/repair manifest. This plugin defers to it rather than duplicating the logic.
+The **plugin is the single source of truth** for ECHO's structure. Everything needed to stand up a vault ships in this skill under `scaffold/` — there is no dependency on any in-vault control doc and no external/local re-seed path. This makes the vault portable: point the REST API at any empty Obsidian vault, run this procedure, and it becomes a working ECHO vault.
 
-## Normal case — vault already bootstrapped
+The vault holds **data only**. It carries no `CLAUDE.md` / `BOOTSTRAP.md` / `STRUCTURE.md` / `index.md`. The "is this vault set up?" signal is a small marker file, `_agent/echo-vault.md`.
 
-ECHO was bootstrapped on 2026-06-05, so this is the expected path. At session start, read the in-vault manifest:
-
-```bash
-curl -s \
-  -H "Authorization: Bearer 241265fbe6830934a9a4ad3e69335f64a42153b663aa5b0017cb1ea1217b2bab" \
-  "https://echoapi.alwisp.com/vault/BOOTSTRAP.md"
+```
+AUTH="Authorization: Bearer 241265fbe6830934a9a4ad3e69335f64a42153b663aa5b0017cb1ea1217b2bab"
+BASE="https://echoapi.alwisp.com"
 ```
 
-If it returns content (200), the vault is set up. Skim its preflight checklist, then read `CLAUDE.md` for the operating contract and proceed with the loading procedure in `SKILL.md`. The in-vault `BOOTSTRAP.md` describes how to repair any missing folders/files; follow it if something is absent. **Never overwrite an existing file** during repair — generate only what is missing.
+---
 
-## Fresh-vault case — BOOTSTRAP.md returns 404
+## Probe — is the vault bootstrapped?
 
-This would mean the REST API is pointed at an empty or wrong vault. Confirm with Jason once:
+At session start, GET the marker:
 
-> "The ECHO vault looks empty — there's no `BOOTSTRAP.md`. That's unexpected (it was bootstrapped 2026-06-05). Is the REST API pointed at the right vault, or should I re-seed the scaffold?"
+```bash
+curl -s -o /dev/null -w "%{http_code}" -H "$AUTH" "$BASE/vault/_agent/echo-vault.md"
+```
 
-If a re-seed is wanted, create the minimum viable seed with `PUT` (the API creates intermediate directories automatically), then let the vault's own structure grow from there:
+- **200** → bootstrapped. Read the marker's `schema_version`; if it is **less than** the plugin's current schema (1), run a migration pass (see *Migrations* below), otherwise proceed straight to the loading procedure in `SKILL.md`.
+- **404** → empty/unconfigured vault. Run **Fresh bootstrap** below. (If you expected an existing vault, confirm with the operator once that the REST API is pointed at the right vault before seeding.)
 
-1. `CLAUDE.md` — operating contract and session protocol
-2. `BOOTSTRAP.md` — preflight/repair manifest
-3. `STRUCTURE.md` — layout, taxonomy, frontmatter standard
-4. `index.md` — navigation hub
-5. `_agent/memory/semantic/operator-preferences.md` — operator profile (no fabricated facts)
-6. `_agent/context/current-context.md` — empty context bundle
-7. `inbox/captures/inbox.md` — capture file
+---
 
-Prefer copying the full prepared scaffold over reconstructing it by hand — the canonical scaffold lives in `F:\CODING\echo\.references\goldbrain-obsidian\` (adapt operator references to Jason).
+## Fresh bootstrap (empty vault)
 
-## After bootstrap
+Idempotent and additive. **Never overwrite an existing file** — GET-probe each path and skip any that already returns `200`. The marker is written **last**, so the vault is only flagged "set up" after every piece is in place.
 
-Tell Jason briefly what was created, append a line to the daily note's **Agent Log**, and write a session log in `_agent/sessions/`. Do not over-explain — he can browse the vault.
+Throughout, `{{DATE}}` means today's date (`YYYY-MM-DD`), resolved from the conversation's `currentDate`. Substitute it before PUTting any scaffold file or anchor seed.
+
+### 1. Folder tree
+
+The REST API auto-creates parent directories on PUT, so creating the tree = seeding a file into each leaf. Obsidian and git both ignore empty dirs, so drop a one-line `README.md` into any leaf that wouldn't otherwise receive a file. Required tree (leaves marked `→ README`):
+
+```
+inbox/captures  inbox/imports  inbox/processing-log
+journal/daily  journal/weekly  journal/monthly  journal/templates
+projects/active  projects/incubating  projects/on-hold  projects/archived
+areas/business  areas/personal  areas/learning  areas/systems
+resources/concepts  resources/references  resources/people  resources/meetings  resources/source-material
+decisions/by-date
+reviews/weekly  reviews/monthly  reviews/quarterly  reviews/annual
+archive/notes  archive/projects  archive/imports
+_agent/context  _agent/memory/working  _agent/memory/episodic  _agent/memory/semantic
+_agent/sessions  _agent/templates  _agent/heartbeat
+_agent/skills/active  _agent/skills/archived
+_agent/outputs/briefs  _agent/outputs/drafts  _agent/outputs/summaries  _agent/outputs/synthesis
+```
+
+> `decisions/by-project/` is intentionally **not** created — it is retired. A project-relevant decision is mirrored as a `[[wikilink]]` under that project's `## Key Decisions` heading instead.
+
+A leaf README is just a one-liner, e.g.:
+
+```bash
+printf '# %s\n\nMemory vault folder. See the echo-memory plugin for conventions.\n' "captures" \
+ | curl -s -X PUT -H "$AUTH" -H "Content-Type: text/markdown" --data-binary @- \
+   "$BASE/vault/inbox/captures/README.md"
+```
+
+### 2. Templates
+
+PUT every file under this skill's `scaffold/templates/` to its mirrored vault path. The tree mirrors 1:1:
+
+| Scaffold file | Vault path |
+|---|---|
+| `scaffold/templates/_agent/templates/session-log-template.md` | `_agent/templates/session-log-template.md` |
+| `scaffold/templates/_agent/templates/context-bundle-template.md` | `_agent/templates/context-bundle-template.md` |
+| `scaffold/templates/_agent/templates/working-memory-template.md` | `_agent/templates/working-memory-template.md` |
+| `scaffold/templates/_agent/templates/semantic-memory-template.md` | `_agent/templates/semantic-memory-template.md` |
+| `scaffold/templates/journal/templates/daily-note-template.md` | `journal/templates/daily-note-template.md` |
+| `scaffold/templates/journal/templates/weekly-review-template.md` | `journal/templates/weekly-review-template.md` |
+| `scaffold/templates/projects/project-template.md` | `projects/project-template.md` |
+| `scaffold/templates/decisions/decision-template.md` | `decisions/decision-template.md` |
+
+Templates keep their Obsidian Templater tokens (`{{date:YYYY-MM-DD}}` etc.) verbatim — those are resolved by Templater / by the skill's daily-note routine, not at seed time.
+
+```bash
+curl -s -X PUT -H "$AUTH" -H "Content-Type: text/markdown" \
+  --data-binary @scaffold/templates/journal/templates/daily-note-template.md \
+  "$BASE/vault/journal/templates/daily-note-template.md"
+```
+
+### 3. Anchor seeds (only if absent — no fabricated facts)
+
+Substitute `{{DATE}}` → today, then PUT each:
+
+| Scaffold file | Vault path |
+|---|---|
+| `scaffold/anchors/operator-preferences.seed.md` | `_agent/memory/semantic/operator-preferences.md` |
+| `scaffold/anchors/current-context.seed.md` | `_agent/context/current-context.md` |
+| `scaffold/anchors/inbox.seed.md` | `inbox/captures/inbox.md` |
+
+The operator-preferences seed is deliberately empty — **do not invent preferences.** Real facts accrue through use.
+
+### 4. Vault README (human signpost)
+
+Substitute `{{DATE}}` if present, then PUT `scaffold/README.vault.md` → `/vault/README.md`. This is the only human-facing control doc in the vault and is **not** read by the agent for routing.
+
+### 5. Marker (write last)
+
+Substitute `{{DATE}}`, then PUT `scaffold/echo-vault.md` → `/vault/_agent/echo-vault.md`. Once this returns `200`, the vault is bootstrapped.
+
+### 6. First-run trace
+
+Create today's daily note from `journal/templates/daily-note-template.md` (resolve the `{{date:…}}` tokens to today), append a one-line `## Agent Log` entry noting the bootstrap, and write a session log in `_agent/sessions/YYYY-MM-DD-HHMM-bootstrap.md`. Tell the operator briefly what was created.
+
+---
+
+## Repair (existing vault, something missing)
+
+Run the same steps 1–5, but GET-probe each path first and **only create what is missing**. Never overwrite. If a file exists but looks malformed, flag it in the session log rather than replacing it. Repair is safe to run any time and is the right response if the loading procedure hits an unexpected `404` on a structural path.
+
+---
+
+## Migrations (`schema_version` mismatch)
+
+When the marker's `schema_version` is older than the plugin's, apply the migration steps for each intervening version, then PATCH the marker's `schema_version` frontmatter to the new value.
+
+- **0 → 1** (control-docs-in-plugin): the vault previously carried root control docs (`CLAUDE.md`, `BOOTSTRAP.md`, `STRUCTURE.md`, `index.md`). Back them up outside the vault, DELETE them, PUT the thin `scaffold/README.vault.md` over the old verbose `README.md`, write the `_agent/echo-vault.md` marker, and scrub now-dangling `[[CLAUDE]]`/`[[BOOTSTRAP]]`/`[[STRUCTURE]]`/`[[index]]` links from the `## Related` sections of `operator-preferences.md` and `current-context.md` (leave historical session logs alone). Confirm with the operator before deleting.

echo-memory.plugin.src/skills/echo-memory/references/operating-contract.md

@@ -0,0 +1,36 @@
+# ECHO — Operating Contract
+
+The durable, client-independent contract for any agent operating against the ECHO vault. These principles and safety rules formerly lived in the vault's `CLAUDE.md`; they now live in the plugin so they survive regardless of what is (or isn't) in the vault. Day-to-day *procedure* — loading order, search-first, triage, scope switching, PATCH/append rules — is owned by `SKILL.md`. This file holds the things that don't change between sessions or clients.
+
+## What this agent is
+
+You are an agent operating against an Obsidian vault that functions as a shared, long-term memory substrate for human work, Claude Code / CoWork sessions, and future REST/MCP clients. Your role is to read context, synthesize across notes, produce structured outputs, update memory carefully, and leave durable traces in the vault rather than keeping important state only in the conversation. The vault is the **system of record**, not a scratchpad.
+
+## Core principles
+
+- Treat the vault as the system of record for long-term memory.
+- Prefer Markdown, YAML frontmatter, wiki-links, and stable folder conventions over proprietary structures.
+- Write notes so both humans and agents can understand them without hidden context.
+- Preserve history instead of silently overwriting important decisions, summaries, or inferred preferences.
+- Keep agent-managed content (`agent_written: true` + `source_notes`) clearly separated from human-authored content.
+- Default to **additive updates, explicit status changes, and traceable summaries.**
+- Optimize for portability: the same vault should work across Claude Code, CoWork, MCP-compatible tools, and REST API clients.
+
+## Memory model (where things live)
+
+- **Working** → `_agent/memory/working/` — transient, time-boxed.
+- **Episodic** → `_agent/memory/episodic/` — what happened, when.
+- **Semantic** → `_agent/memory/semantic/` — durable facts, patterns, preferences (`operator-preferences.md`).
+- **Context bundles** → `_agent/context/` — task-focused reading lists and active state.
+
+## Safety rules
+
+- Do not fabricate facts, relationships, or prior decisions.
+- Do not mass-restructure the vault unless explicitly asked.
+- Do not delete notes unless deletion is explicitly requested and clearly safe.
+- Do not store secrets or API keys inside the vault, and never write the API key into a vault note.
+- Default to additive updates and explicit status changes over destructive edits.
+
+## REST/API readiness
+
+Assume clients may operate without filesystem access, through the Obsidian Local REST API. Keep paths predictable, frontmatter parseable, titles stable, and all state stored in notes rather than hidden conversation memory. Structure must stay portable: a fresh, empty vault is brought fully online by the plugin's bootstrap (`references/bootstrap.md`), so nothing essential should depend on files existing in the vault ahead of time.

echo-memory.plugin.src/skills/echo-memory/references/vault-layout.md

@@ -1,15 +1,12 @@
 # Vault Layout & Frontmatter Conventions
 
-Mirrors the canonical conventions defined in the vault's own `STRUCTURE.md` and `BOOTSTRAP.md`. If those change, they are the source of truth.
+**This document is canonical.** The ECHO vault holds data only — there are no `CLAUDE.md` / `STRUCTURE.md` / `BOOTSTRAP.md` / `index.md` control docs in it. Layout, taxonomy, and frontmatter conventions live here in the plugin; the bootstrap procedure (`references/bootstrap.md`) builds the tree below into any empty vault.
 
 ## Folder Map (root-addressed)
 
 ```
 /vault/
-├── CLAUDE.md          ← operating contract + session protocol
-├── STRUCTURE.md       ← layout, taxonomy, frontmatter standard
-├── BOOTSTRAP.md       ← preflight/repair manifest (read first)
-├── spinup.md  index.md  README.md
+├── README.md          ← thin human signpost (NOT read for routing)
 ├── inbox/
 │   ├── captures/      ← quick captures (inbox.md), date-prefixed lines
 │   ├── imports/       ← raw imported material
@@ -36,6 +33,7 @@ Mirrors the canonical conventions defined in the vault's own `STRUCTURE.md` and
 ├── reviews/           ← weekly / monthly / quarterly / annual
 ├── archive/           ← notes / projects / imports
 └── _agent/
+    ├── echo-vault.md  ← bootstrap marker: schema_version + bootstrap date (plugin-owned; the "is this vault set up?" probe)
     ├── context/       ← current-context.md and task bundles
     ├── memory/
     │   ├── working/   ← transient, time-boxed

echo-memory.plugin.src/skills/echo-memory/scaffold/README.vault.md

@@ -0,0 +1,12 @@
+# ECHO Memory Vault
+
+This Obsidian vault is the persistent memory substrate ("second brain") for its operator. It is read and written across Claude / CoWork sessions through the Obsidian Local REST API.
+
+**This vault holds data, not logic.** All operating procedure — how the vault is bootstrapped, how notes are routed, the taxonomy, frontmatter conventions, and safety rules — lives in the **`echo-memory` plugin**, which is the single source of truth. There are intentionally no `CLAUDE.md` / `BOOTSTRAP.md` / `STRUCTURE.md` control docs in this vault; updating or porting ECHO means updating or installing the plugin, not editing files here.
+
+- **Layout:** see the plugin's `references/vault-layout.md`.
+- **Operating contract & safety:** see the plugin's `references/operating-contract.md`.
+- **Bootstrap / repair:** see the plugin's `references/bootstrap.md`.
+- **Version marker:** `_agent/echo-vault.md` records the schema version and bootstrap date.
+
+Folders: `inbox/`, `journal/`, `projects/`, `areas/`, `resources/`, `decisions/`, `reviews/`, `archive/`, and the agent subtree `_agent/`.

echo-memory.plugin.src/skills/echo-memory/scaffold/anchors/current-context.seed.md

@@ -0,0 +1,25 @@
+---
+type: context-bundle
+status: active
+created: {{DATE}}
+updated: {{DATE}}
+tags: [agent, context]
+agent_written: true
+source_notes: []
+scope:
+refresh_strategy: on-demand
+---
+
+# Current Context
+
+## Scope
+<!-- The single active scope. Replaced (PATCH replace) on each scope switch. -->
+
+## Scope History
+<!-- Dated bullets of prior scopes, newest first: `- {{DATE}}: <prior scope summary>`. Trim to ~10. -->
+
+## Active Priorities
+
+## Open Questions
+
+## Related

echo-memory.plugin.src/skills/echo-memory/scaffold/anchors/inbox.seed.md

@@ -0,0 +1,3 @@
+# Inbox — Captures
+
+Quick captures land here as date-prefixed lines (`- {{DATE}}: <thing>`), one per line, via POST. Triage routes durable items to their proper home (see the echo-memory skill's Inbox Triage). Don't delete originals on triage — the processing log is the audit trail.

echo-memory.plugin.src/skills/echo-memory/scaffold/anchors/operator-preferences.seed.md

@@ -0,0 +1,31 @@
+---
+type: semantic-memory
+status: active
+created: {{DATE}}
+updated: {{DATE}}
+tags: [agent, semantic-memory, operator]
+agent_written: true
+source_notes: []
+confidence: low
+last_reviewed: {{DATE}}
+---
+
+# Operator Preferences
+
+## Operator
+<!-- One paragraph: who the operator is. Leave for the operator to confirm; do not fabricate. -->
+
+## Fact / Pattern
+<!-- Promoted, deduped, timeless rules. No date prefix. Add only when a rule is stable. -->
+
+## Observations
+<!-- Timestamped raw observations. Default landing zone for new evidence: `- {{DATE}}: ...` -->
+
+## Evidence
+
+## Recommendation or Implication
+
+## Review Notes
+Seeded empty at bootstrap ({{DATE}}). Raise confidence once preferences are confirmed through day-to-day use.
+
+## Related

echo-memory.plugin.src/skills/echo-memory/scaffold/echo-vault.md

@@ -0,0 +1,19 @@
+---
+type: reference
+status: active
+created: {{DATE}}
+updated: {{DATE}}
+tags: [agent, system, marker]
+agent_written: true
+source_notes: []
+schema_version: 1
+bootstrapped: {{DATE}}
+managed_by: echo-memory-plugin
+---
+
+# ECHO Vault Marker
+
+This file marks the vault as bootstrapped by the **echo-memory plugin** and records its schema version. The plugin's loading procedure GETs this file as its "is this vault set up?" probe; a `404` triggers a fresh bootstrap.
+
+- `schema_version` — bumped by the plugin when the vault layout changes; a mismatch is the hook for a migration pass (see `references/bootstrap.md`).
+- Do not hand-edit. The plugin owns this file.

echo-memory.plugin.src/skills/echo-memory/scaffold/templates/_agent/templates/context-bundle-template.md

@@ -0,0 +1,27 @@
+---
+type: context-bundle
+status: active
+created: {{date:YYYY-MM-DD}}
+updated: {{date:YYYY-MM-DD}}
+tags: [agent, context]
+agent_written: true
+source_notes: []
+scope:
+refresh_strategy: on-demand
+---
+
+# Context Bundle Title
+
+## Scope
+
+## Active Priorities
+
+## Relevant Entities
+
+## Key Decisions
+
+## Open Questions
+
+## Source Notes
+
+## Related

echo-memory.plugin.src/skills/echo-memory/scaffold/templates/_agent/templates/semantic-memory-template.md

@@ -0,0 +1,23 @@
+---
+type: semantic-memory
+status: active
+created: {{date:YYYY-MM-DD}}
+updated: {{date:YYYY-MM-DD}}
+tags: [agent, semantic-memory]
+agent_written: true
+source_notes: []
+confidence: high
+last_reviewed: {{date:YYYY-MM-DD}}
+---
+
+# Semantic Memory Title
+
+## Fact / Pattern
+
+## Evidence
+
+## Recommendation or Implication
+
+## Review Notes
+
+## Related

echo-memory.plugin.src/skills/echo-memory/scaffold/templates/_agent/templates/session-log-template.md

@@ -0,0 +1,29 @@
+---
+type: session-log
+status: complete
+created: {{date:YYYY-MM-DDTHH:mm}}
+updated: {{date:YYYY-MM-DDTHH:mm}}
+tags: [agent, session]
+agent_written: true
+source_notes: []
+session_date: {{date:YYYY-MM-DD}}
+client: claude-code
+---
+
+# Session Log
+
+## Goal
+
+## Notes Read
+
+## Actions Taken
+
+## Decisions Made
+
+## Outputs Created
+
+## Open Threads
+
+## Suggested Next Step
+
+## Related

echo-memory.plugin.src/skills/echo-memory/scaffold/templates/_agent/templates/working-memory-template.md

@@ -0,0 +1,22 @@
+---
+type: working-memory
+status: active
+created: {{date:YYYY-MM-DDTHH:mm}}
+updated: {{date:YYYY-MM-DDTHH:mm}}
+tags: [agent, working-memory]
+agent_written: true
+source_notes: []
+expires_after: 48h
+---
+
+# Working Context
+
+## Active Focus
+
+## Recent Decisions
+
+## Open Threads
+
+## Relevant Links
+
+## Related

echo-memory.plugin.src/skills/echo-memory/scaffold/templates/decisions/decision-template.md

@@ -0,0 +1,25 @@
+---
+type: decision
+status: complete
+created: {{date:YYYY-MM-DD}}
+updated: {{date:YYYY-MM-DD}}
+tags: [decision]
+agent_written: true
+source_notes: []
+decision_date: {{date:YYYY-MM-DD}}
+impact: medium
+---
+
+# Decision Title
+
+## Context
+
+## Decision
+
+## Rationale
+
+## Consequences
+
+## Follow-Up
+
+## Related

echo-memory.plugin.src/skills/echo-memory/scaffold/templates/journal/templates/daily-note-template.md

@@ -0,0 +1,25 @@
+---
+type: daily-note
+status: active
+created: {{date:YYYY-MM-DD}}
+updated: {{date:YYYY-MM-DD}}
+tags: [daily, journal]
+agent_written: false
+source_notes: []
+---
+
+# {{date:YYYY-MM-DD}}
+
+## Top Priorities
+
+## Schedule / Commitments
+
+## Open Loops
+
+## Notes
+
+## Context for AI
+
+## Agent Log
+
+## Related

echo-memory.plugin.src/skills/echo-memory/scaffold/templates/journal/templates/weekly-review-template.md

@@ -0,0 +1,26 @@
+---
+type: review
+status: active
+created: {{date:gggg-[W]WW}}
+updated: {{date:gggg-[W]WW}}
+tags: [review, weekly]
+agent_written: true
+source_notes: []
+period: weekly
+---
+
+# Weekly Review
+
+## Completed Work
+
+## Open Loops
+
+## Stale Projects
+
+## Decisions
+
+## Priorities Next Week
+
+## Agent Notes
+
+## Related

echo-memory.plugin.src/skills/echo-memory/scaffold/templates/projects/project-template.md

@@ -0,0 +1,31 @@
+---
+type: project
+status: active
+created: {{date:YYYY-MM-DD}}
+updated: {{date:YYYY-MM-DD}}
+tags: [project]
+agent_written: false
+source_notes: []
+owner:
+review_cycle: weekly
+---
+
+# Project Name
+
+## Purpose
+
+## Status
+
+## Goals
+
+## Current Context
+
+## Open Loops
+
+## Key Decisions
+
+## Related Notes
+
+## Session History
+
+## Related