Back to corpus
technical noteexperiment writeup candidatescore 40

Obsidian Vault Writer — Cross-Agent Integration Handoff

**Date**: 2026-03-01 **Author**: Claude Code (Opus 4.6) **For**: All agent sessions (Codex, Gemini, Clawdbot, Cursor, future agents) **Status**: Phase 1-4 complete, live on cloud-vm

Full HTML reader

Read the full artifact

Open in new tab

Extracted abstract or opening context

**Date**: 2026-03-01 **Author**: Claude Code (Opus 4.6) **For**: All agent sessions (Codex, Gemini, Clawdbot, Cursor, future agents) **Status**: Phase 1-4 complete, live on cloud-vm The **Obsidian Vault Writer** is a Python module that writes structured Markdown notes to an Obsidian vault. Every note has YAML frontmatter and `[[bidirectional links]]` that create an organic knowledge graph. The vault lives on cloud-vm and syncs to all devices via Obsidian Sync (E2E encrypted). **The core idea**: Every agent session, every Discord synthesis, every AAO task completion, and every Prefect flow run should produce a vault note. Over time, `[[backlinks]]` reveal connections between ideas, projects, and agents that no single system tracks. | File | Location | Trigger | What it writes | |------|----------|---------|----------------| | `synthesis-preprocessor.js` | `[home-path]` | Discord message synthesized | `Inbox/{date}/{time}-{slug}.md` | | `session_end_hook.py` | `[home-path]` | Claude Code session ends | `Sessions/{date}-claudecode-{id}.md` | | `aao_reputation_collector.py` | `[home-path]` | AAO task quality assessed | `Sessions/{date}-{agenttype}-{task_id}.md` | | `vault_sync.py` | `[home-path]` | Every 6h Prefect flow | Catch-up synthesis + agent sessions + daily summaries | | Component | Location | Port | Role | |-----------|----------|------|------| | obsidian-sync.service | cloud-vm systemd | — | Continuous vault sync via `ob sync --continuous` | | obsidian-headless (ob) | `/usr/bin/ob` on cloud-vm | — | Node 22+ CLI for headless Obsidian | | Obsidian Cloud | Agent Vault (North America) | — | E2E encrypted sync hub |

Promotion decision

What has to happen next

Attach run IDs, datasets, metrics, and reproduction commands.

Why this is not always a full paper yet

Corpus pages are public-safe readers for discovered workspace artifacts. They are not automatically final papers. A corpus item becomes a polished paper only after the editable source, evidence checkpoints, references, figures, render path, and release status are attached through the paper schema.