Vault Inbox — Filing Cheat Sheet

Quick reference for processing inbox files on the Chromebook.

Step 1: Pull the inbox

cd ~
rclone copy gdrive:vault-inbox ~/vault-inbox --progress
ls ~/vault-inbox/

Look at what's there. Decide where each file goes BEFORE moving anything.

Step 2: Find the right folder FIRST

Don't guess. Run this to see the full folder tree for wherever you're filing:

# See all folders for a specific client
find ~/advisory-os-vault/content/clients/ruben-crulliance/ -type d

# See all top-level client folders
ls ~/advisory-os-vault/content/clients/

# See entire vault structure
find ~/advisory-os-vault/content/ -type d | head -50

Match the file to the deepest correct folder. Example:

• FC workflow spec → projects/accounting-manager-os/builds/
• NOT projects/ — that's too shallow

Step 3: Move files

mv ~/vault-inbox/filename.ext ~/advisory-os-vault/content/clients/[client]/[full/path/to/folder]/

Verify it landed:

ls ~/advisory-os-vault/content/clients/[client]/[full/path/to/folder]/

Step 4: Push to GitHub + Drive

cd ~/advisory-os-vault
git add -A
git commit -m "description of what you added"
git push origin master
rclone copy ~/advisory-os-vault/content gdrive:advisory-os-vault --progress

Step 5: Clear the inbox

rclone purge gdrive:vault-inbox
mkdir -p ~/vault-inbox
touch ~/vault-inbox/.gitkeep
rclone copy ~/vault-inbox gdrive:vault-inbox --progress

Rules

• Always find -type d before filing — never guess the path
• Client folder names use full format: ruben-crulliance not ruben
• Projects have subfolders: project-plan/, blueprint/, builds/, deployment/
• File to the deepest correct folder, not the parent
• If unsure where something goes, leave it in ~/vault-inbox/ and ask