Project
Vault Operations
Executable audits and Marimo views over a canonical Obsidian vault: portfolio manager loops, publication projectors, and a polymath research atlas that maps evidence stages without inventing a quality score.
Status Active
Vault Operations
Vault Operations (vault-ops) is the executable control plane for a human-first Obsidian vault. Markdown remains canonical; Marimo notebooks, audits, and projectors live beside the vault so agents can measure publication readiness without rewriting notes as code.
The operating loop is deliberate: projects and tasks stay in the vault; publish_research.py fail-closed projects only allowlisted public notes; publish_notebooks.py seals Marimo exports with provenance hashes; a portfolio manager reconciles parallel leaves. The polymath research atlas asks where work stalls across research stages — without collapsing those stages into a single opaque score.
Reports
- Report
Polymath Research Atlas
Portfolio evidence-pipeline audit: transparent stage flags and metadata-backed bridge retrieval over a personal research vault — not a quality score.