A reusable Vault scaffold with standard partitions, frontmatter conventions, day-to-day scripts, and scheduled automations — clone it, and your knowledge base runs on autopilot.
| Pain point | Without it | With this scaffold |
|---|---|---|
| Notes get messy | Manual filing, out of control as content grows | 15 scoped partitions + frontmatter from day one |
| Repeating daily chores | Scattered, non-parameterized scripts | Standard-library-first, parameterized via one env var |
| Want the pipeline on autopilot | Hand-written crons, no logs or idempotency | Ready cron/launchd templates + structured logs |
| Compile a wiki from notes | Duplicate compile logic, two sources of truth | Thin 71-Wiki interface delegating to one repo |
15 numbered areas from 00-Inbox to 99-Attachments, each with one responsibility — routing is a rule, not a habit.
Uniform metadata on every note — searchable, clusterable, and ready for a knowledge graph.
Python 3.11+ standard-library-first: new-note, add-frontmatter, html-to-md, archive-url, qmd-noise-guard.
Daily briefing, Inbox normalization, timesheets, weekly review, and P0/P1 reminders — all non-destructive and idempotent.
A thin 71-Wiki interface — compile, index, lint, search — delegates to a single dedicated repo, no duplication.
Every path flows through OBSIDIAN_VAULT_DIR with a cwd fallback. Clone it anywhere; it never knows your name.
cron templates ship in 70-System/70.05-Configs/templates/ — launchd example included.