## Routine - [x] Open Daily Note - [x] **Daily Checks** - [x] Self Care 🛀🧴 - [x] Pet Care 🐕🚶🏻‍♂️ - [x] Make Breakfast ☕🍳 - [x] Get Focused 🖥️ - [x] Check [Calendar](https://calendar.google.com) 📆 - [x] Check [Mail](https://mail.google.com) ✉️ - [x] Review [[Yearly Log]] 📝 --- ## Log - **15:39** — This vault now files an end-of-day report like every other project. - **15:40** — Filed [[The Home System]] under `reference/Obsidian`; linked from [[Claude Code Integration]]. - **15:42** — Added a pre-publish deny-list check alongside `vault-check.py`. --- ## Notes ### Public vaults leak through scaffolding The risk in a public vault isn't its secrets — those get guarded. It's the incidental structure: a list of project names, a directory tree, a roster. None of it discloses any work, and all of it describes the client base. Pattern-based linting doesn't reach it. Emails, phone numbers and keys have a shape; a proper noun doesn't. That needs a deny-list — which belongs *outside* the public vault, since an enumeration of every client would be the most sensitive file in it. So the check runs from the private side against the public one, before anything goes live.