blog-why-vault-first.md
markdown
sha256:94ec65bd2b200240ac785a97cf14c5db066832bd608a24d6a9c151f17b918b02
feat(calendar): hosted bridge/gateway route parity and time…
Human
minor
⚠ breaking
37 days ago
title: "Draft — Why vault-first beats feed-first thinking" project: "blog-knowledge-management" tags:
- draft
- blog
- knowledge-management date: 2026-04-07 status: draft target_date: 2026-04-21 word_count_target: 1200
Why vault-first beats feed-first thinking
Feeds reward recency, not reuse. A personal vault rewards notes you can find in six months when the problem comes back dressed as a new emergency.
Thesis
Knowledge work compounds when the default capture surface is yours—searchable, linkable, and exportable—before anything gets polished for an audience.
Outline (working)
- The cost of feed capture — bookmarks rot; threads scroll away.
- Vault-first habits — title + tags + one sentence of context on save.
- Publish from inventory — blog posts as distillations, not as the primary store.
- Closing — invite readers to pick one inbox and clear it into five titled notes.
To finish
- [ ] Add concrete example (e.g., debugging runbook → public post).
- [ ] Cite one study or industry report on information overload (clip in
research/).
Current word count — ~180 (draft stub).
File History
1 commit
sha256:94ec65bd2b200240ac785a97cf14c5db066832bd608a24d6a9c151f17b918b02
feat(calendar): hosted bridge/gateway route parity and time…
Human
minor
⚠
37 days ago