refactor(docs): DRY think-tank warnings with centralized procedure

knowledge/principles/no-leaks.md

@@ -14,10 +14,6 @@ Avoid leaking company details into your public dotfiles - it's about respect, no
 - SHOULD keep comprehensive company-specific documentation in `think-tank/` directory
 - MAY include as much detail as needed in gitignored notes - they stay local and private
 
-**Spilled Coffee Compatibility**: think-tank notes are backed up in company cloud and only accessed on company hardware. AI can easily find think-tank documentation during setup, maintaining 20-minute recovery time. Inline comments create discoverable breadcrumbs.
-
-**Global Force Multiplier**: The `think-tank/` pattern works in ANY repository via global gitignore configuration. This multiplies the impact across your entire professional ecosystem - every repo gets rich company context for AI agents while keeping company details private.
-
-**Remember**: Check and update think-tank documentation when working in these areas - keep the breadcrumbs fresh.
+→ See [think-tank](../procedures/think-tank.md) for complete directory usage guidelines.
 
 Keep company details in your private vaults, not public dotfiles. Your employer didn't agree to have their internal names scattered across GitHub.

knowledge/procedures/git-workflow.md

@@ -55,4 +55,4 @@ When converting a directory to a symlink (or vice versa), it's safer to use diff
 3. Create fresh branch from clean state if corruption occurs
 
 ## Think-Tank Content in Worktrees
-**CRITICAL**: Never add think-tank notes or personal content to worktree locations. Worktrees are temporary directories that will be deleted when cleanup occurs. Always use the main repository at `/think-tank/` for any persistent personal content, notes, or documentation.
+→ See [think-tank](../procedures/think-tank.md) for personal content storage guidelines.

knowledge/procedures/think-tank.md

@@ -0,0 +1,29 @@
+# Think-Tank Directory
+
+A designated space for personal content that lives outside the codebase but needs version control.
+
+## Purpose
+Store personal documents, notes, and drafts that:
+- Don't belong in code directories
+- Need to persist across development sessions
+- Require version control for safety
+
+## Location
+**Always use**: `/think-tank/` in the main repository
+**Never use**: Worktree locations (they're ephemeral)
+
+## What Belongs Here
+✓ Personal notes and brainstorming
+✓ Resume drafts and career documents
+✓ Learning notes and research
+✓ Project ideas and planning docs
+✓ Personal scripts or configurations
+
+## What Doesn't Belong Here
+✗ Code documentation (use `/docs/`)
+✗ Project-specific notes (use project directories)
+✗ Sensitive credentials (use `.bash_secrets`)
+✗ Generated files or build artifacts
+
+## Key Principle
+Think-tank content is personal workspace material. It's tracked by git but kept separate from the technical ecosystem of the dotfiles.

knowledge/procedures/worktree-workflow.md

@@ -30,4 +30,4 @@ Suppose you need to work on multiple tasks simultaneously with complete code iso
 - **Wrong file paths**: Files created in main, not worktree → empty commits
 - **[OSE Principle](../principles/ose.md)**: Only GitHub PR diff matters for review - must verify before creating PR
 - **Broken symlinks**: Running setup.sh from worktree creates symlinks that break when worktree is deleted
-- **Think-tank content in worktrees**: Never add think-tank notes or personal content to worktree locations - they're ephemeral and will be lost. Always use the main repository at `/think-tank/`
+- **Think-tank content in worktrees**: See [think-tank](../procedures/think-tank.md) - worktrees are ephemeral