feat: Obsidian integration via cli scripts

vault/00-start/glossary.md

@@ -24,6 +24,7 @@ Common terms used in this workspace.
 - `inbox`: raw or lightly processed communication evidence under `ai/inbox/`.
 - `promotion`: moving high-confidence evidence into canonical memory.
 - `tooling behavior`: reusable behavior encoded in commands, prompts, skills, agents, or knowledge rules.
+- `memory interface`: project-agnostic scripts under `scripts/memory/` that create, search, query, and validate canonical memory without coupling the workspace to Obsidian.
 
 ---
 

vault/00-start/obsidian-usage.md

@@ -10,6 +10,8 @@ tags:
 
 Use Obsidian to navigate and review workspace memory. Do not use it as a separate memory database.
 
+Obsidian is the current interface over canonical Markdown memory. The workspace-level abstraction is `scripts/memory/`, so agents should use Obsidian-specific commands only through that adapter when possible.
+
 ---
 
 ## Recommended Start
@@ -126,3 +128,26 @@ For normal onboarding, keep them hidden and navigate through the named maps.
 - Templates may contain the final note `type` so newly created notes are useful immediately, but Bases must exclude the template folder so template files do not appear as data rows.
 - Role mapping files such as `04-people/manager.md` should use `type: role-map`, not `type: person`.
 - Bookmarks should keep `00-start/start-here.md`, `00-start/onboarding.md`, current work, work items, people, and high-value Bases easy to open.
+
+---
+
+## CLI And Templates
+
+The official Obsidian CLI can create notes from templates, query Bases, inspect properties, and search the vault.
+
+In this workspace, prefer the platform-agnostic memory wrapper:
+
+```bash
+bash scripts/memory/memory.sh create work-item pdiap-15999 "Example title"
+bash scripts/memory/memory.sh search "PDIAP-15765"
+bash scripts/memory/memory.sh base-query work-items
+bash scripts/memory/memory.sh health
+```
+
+The wrapper owns note type routing, so a `work-item` goes to `02-work-items/`, a `person` goes to `04-people/`, a `decision` goes to `05-decisions/`, and so on.
+
+Use Obsidian CLI directly only when debugging Obsidian-specific behavior:
+
+```bash
+bash scripts/obsidian/cli.sh help
+```

vault/00-start/start-here.md

@@ -75,6 +75,8 @@ If you are new to this project, read:
 - [Communication Rules](../03-context/process/communication-rules.md)
 - [Context Maintenance](../03-context/process/context-maintenance.md)
 - [Workspace Architecture](workspace-architecture.md)
+- Memory interface: `scripts/memory/`
+- Obsidian adapter: `scripts/obsidian/`
 
 ---
 

vault/00-start/workspace-architecture.md

@@ -50,6 +50,19 @@ Runtime and generated files can be used as evidence, but durable project facts s
 
 ---
 
+## Memory Access Layer
+
+Use `scripts/memory/` as the platform-agnostic interface to canonical memory.
+
+Obsidian is the current visual and CLI-backed adapter, but the source of truth remains Markdown under `vault/`.
+
+- Agents use `scripts/memory/memory.sh create` when a new typed note is needed.
+- Agents use `scripts/memory/memory.sh search` or direct Markdown reads for context lookup.
+- Agents use `scripts/memory/memory.sh base-query` and `health` for structured review.
+- Precise memory edits should still be made directly to Markdown so changes stay auditable.
+
+---
+
 ## Memory Rule
 
 Promoted memory lives in `vault/`.