The Color Bible — Universal Digital Color System

← Chaos Console

01 The Diagnosis: Why Your V3 System Stalled
02 Four Design Principles
03 The Five Colors (and Only Five)
04 What Got Killed and Why
05 The New 3-Layer Taxonomy

06 The Blindspot Question
07 The Hashtag (#) Question
08 Cross-Platform Color Map
09 Master Tag List (Ready to Create)
10 Implementation Playbook

01 — The Diagnosis: Why Your V3 System Stalled

Your V3 taxonomy was technically correct but practically unusable. Here's why it never fully activated:

Problem 1: Color Collision

You were using the same colors for two unrelated purposes. Red meant "Active" on files but "Health" on folders. Orange meant "In Progress" on files but "Work" on folders. Green meant "Done" on files but "Academia" on folders. When you see a red dot in Finder, your brain has to context-switch: "Is this urgent, or is this medical?" That cognitive tax killed the whole system. Colors must mean one thing, everywhere, always.

Problem 2: Seven Is Too Many

Seven status colors exceeds working memory. You had Red, Orange, Yellow, Green, Blue, Purple, Gray — each with a distinct meaning. Research shows 4–6 categories is the sweet spot for instant color recognition without lookup. You were above the ceiling.

Problem 3: Four Layers = Tagging Paralysis

Every file needed up to 4 tags (Status + Project + Type + Topic). That's a 20-second decision per file. At 100 files, that's 33 minutes of pure tagging. You'll never do that. The system needs to work with 1 tag per file as the default, 2 as the max for most files.

Problem 4: Tags That Only Live in Finder

Finder tags don't exist on Google Drive. Your V3 system assumed everything lived on iCloud/APFS. But a significant chunk of your production work (Blindspot scripts, branding guides, research docs) lives on Google Drive. Any system that ignores Drive is incomplete.

02 — Four Design Principles

One Color, One Meaning, Everywhere

If Red means "needs attention" on your Mac, it means "needs attention" on your iPhone, your iPad, your Google Drive folder colors, your Notion tags, your calendar. No exceptions. No context-switching.

Five Colors Maximum

The human brain groups colors into 5–6 categories before confusion sets in. We use exactly 5 of macOS's 7 available tag colors. The other 2 (Yellow, Gray) get retired. Any additional tags are text-only, no color.

One Tag Is the Default

Most files get exactly 1 tag: a status color. Active production files get 2 (status + project). Nobody ever needs more than 2. If you're applying 3+ tags, something is wrong with your system, not your file.

No Tag = Unprocessed

A file with zero tags is your inbox. Hazel catches these. You don't need a blue "Inbox" tag — the absence of any tag IS the inbox state. This eliminates one color from your system entirely.

03 — The Five Colors (and Only Five)

These are the only five colors that mean anything in your digital life. Memorize them once. Apply them everywhere.

Hot

Needs attention now

Ctrl-1

Fire. Stop sign. Alert. You see red, you act.

In Flight

Started, not finished

Ctrl-2

Caution tape. Construction zone. Mid-process.

Done

Complete, shipped, resolved

Ctrl-3

Green light. Checkmark. Safe. Finished.

Waiting

Blocked on someone/something else

Ctrl-4

Cool. Calm. Patient. Out of your hands.

Reference

Evergreen. Consult repeatedly.

Ctrl-5

Royal. Rare. Preserved. A file you'll re-open 10+ times.

The No-Tag State

A file or folder with no color tag means unprocessed. It hasn't been triaged yet. Hazel watches for these. Your weekly sweep catches these. This replaces the old Blue "Inbox" tag — saving you one color and one decision. If it has no dot, it needs sorting.

The Archive State

The old Gray "Archive" tag is gone. Archived files get no color tag — they've been moved to their final resting place (Blindvault, completed folder, etc.). Their physical location IS their archive status. You don't need a color to say "this is old." The folder it's in says that.

04 — What Got Killed and Why

Yellow — Paused / Waiting

Merged into Blue (Waiting) and Orange (In Flight). "Paused" is either "I'm blocked on someone" (Blue) or "I stopped working on it" (remove Red, leave Orange). Yellow added no unique state.

Absorbed by: Blue (Waiting) + Orange (In Flight)

Gray — Archive

Replaced by physical location. If a file is in Blindvault/Archive/ or a _Completed/ subfolder, it's archived. Gray added visual noise without information.

Absorbed by: Folder structure (no tag needed)

Why Not Kill Blue Instead?

The V3 system used Blue for "Inbox" (unprocessed). This Bible uses "no tag" for inbox. So why keep Blue? Because Waiting is a genuinely distinct state from "not started" or "in progress." A legal document sent to Albania for notarization, a video waiting for client feedback, a tax form pending accountant review — these are real blockers that need their own color so you know: don't touch this, it's out of your hands.

05 — The New 3-Layer Taxonomy

Down from 4 layers to 3. Content Type (Layer 3 in V3) is eliminated — it's redundant with file extensions and folder location. A .pdf in Financial/ doesn't need a t:Financial tag. That's double-bookkeeping.

Layer 1 — Status (Color Tags)

One per file. This is the only layer that uses color. Applied via Ctrl-1 through Ctrl-5.

Tag Name	Color	Shortcut	Meaning	When to Apply
Hot	Red	`Ctrl-1`	Needs attention now	Files you touched today or need to act on this week
In Flight	Orange	`Ctrl-2`	Work in progress	Drafts, partial edits, ongoing research, parked-but-returning
Done	Green	`Ctrl-3`	Completed	Shipped episodes, filed paperwork, published articles
Waiting	Blue	`Ctrl-4`	Blocked externally	Legal reviews, client feedback, government processing
Reference	Purple	`Ctrl-5`	Evergreen resource	Style guides, templates, business plans, checklists, key research

No tag = Unprocessed / needs triage. Green files in active folders should eventually be moved to their permanent home or have their tag removed.

Layer 2 — Project (Text Tags, No Color)

Optional. One per file when needed. Uses p: prefix. No color assigned — these are text-only Finder tags.

Tag	Scope
p:Blindspot	Channel-wide: branding, strategy, templates, channel art
p:EP01	Episode 1: Soviet Revenge — scripts, research, assets
p:EP02	Episode 2: Right-Wing Socialism
p:EP03 through p:EP07	Future episodes (create as needed)
p:Substack	Newsletter drafts, subscriber data, cross-posts
p:Spotify	Playlist data, CSV exports, tracker, cover art
p:Studio	Equipment docs, camera settings, Stream Deck, lighting
p:Albania	Legal, property, Power of Attorney, government filings
p:Accenture	Current employment (own files only, not shared)

When to use: Only when a file could live in multiple folders or when you want Smart Folder aggregation across locations. Most files in Documents/Financial/ don't need a project tag — their folder IS the project. Use project tags for files that cross boundaries.

Layer 3 — Topic (Text Tags, No Color)

Optional. For cross-cutting themes that span multiple projects. Uses # prefix. Apply sparingly.

Tag	Covers
#Politics	US political analysis, institutional critique, hypocrisy
#History	WWII, French Revolution, Cold War, historical parallels
#Economics	Housing, inequality, BlackRock, tariffs, wealth gaps
#Geopolitics	EU, Albania, NATO, Middle East, foreign policy
#Media	Press criticism, algorithms, attention economy, platform power
#Health	Medical records, ACC, vet records (Francis)
#Production	Camera, editing, DaVinci, SLog3, audio, studio workflow

06 — The Blindspot Question

Q: Should "The Blindspot" be a color tag, no tag, or a tag with no color?

A: Text-only tag, no color. Here's the logic:

The Blindspot is a project, not a status. It doesn't tell you what to do with a file — it tells you what the file belongs to. Colors are reserved exclusively for status (what action is needed). Projects get the p: prefix with no color.

The tag p:Blindspot exists for one purpose: Smart Folder aggregation. It lets you create a Finder Smart Folder that pulls every Blindspot-related file regardless of where it physically lives — scripts in The Blindspot/, research in Books/, assets on the Blindvault, whatever. Without the tag, you'd have to manually check 4 locations.

When to NOT Tag Something p:Blindspot

If a file already lives inside Documents/The Blindspot/ or a subfolder, you probably don't need the tag. The folder IS the project membership. Use p:Blindspot only for files that live outside the Blindspot folder tree but serve the project — e.g., a reference book in Books/Barbara Tuchman/ that you're using for EP01 research.

07 — The Hashtag (#) Question

Q: What's the point of using # in topic tags?

A: Three functions, all practical:

1. Namespace collision prevention. Without prefixes, "Health" the topic tag and "Health" the folder name are indistinguishable in Finder's tag autocomplete. #Health is unambiguous — it's always a topic, never a folder, never a project. Same logic applies to p: for projects.

2. Spotlight precision. Searching tag:#Politics in Spotlight returns only files tagged with the topic. Searching just "Politics" returns every file with "politics" in the filename or content — thousands of false positives.

3. Visual scanning. When you look at a file's tags in Finder's info panel, the prefix tells you the tag type at a glance:

  Hot p:EP01 #History
  
  Reading left to right: "This is active, belongs to Episode 1, covers a historical topic."
  
3 tags, 2 seconds to parse, zero ambiguity.

When to Use Topic Tags

Topic tags are the least important layer. Most files never need one. Use them only when a file serves multiple projects and you want to find it by theme later. A script for EP01 about Soviet revenge doesn't need #History — it's already in the EP01 folder. But a standalone research PDF about WWII retribution patterns that informs EP01, EP03, and a Substack draft? That gets #History.

08 — Cross-Platform Color Map

Here's how the 5 colors translate across every platform you use. The meaning never changes — only the implementation differs.

macOS Finder

Full native support

Finder tags with 7 built-in colors. You use 5 (Red, Orange, Green, Blue, Purple). Yellow and Gray are deactivated — remove them from Finder Preferences > Tags favorites bar so they don't clutter autocomplete. Custom text tags (p: and #) with no color work natively.

iOS / iPadOS Files App

Full iCloud sync

Tags sync via iCloud. Same 5 colors visible in Files app. Can apply and filter by tag. Works on iPhone 16 Pro and iPad mini.

Google Drive

Folder colors only (personal accounts)

No file-level tags. Use folder colors to mirror the system: Red folder = Hot/Active project, Orange = In Progress, Green = Done, Blue = Waiting, Purple = Reference. Apply via right-click > Change color. Not as granular as Finder, but keeps the mental model consistent.

Notion / Obsidian / Notes

Manual enforcement

Use the same 5-color system for status labels, database property colors, or tag colors. Red = Hot, Orange = In Flight, etc. Most tools let you customize tag/label colors. Match them.

The Blindvault (External APFS)

Full native support

APFS supports Finder tags natively. Same behavior as iCloud Drive. Tags applied on Mac Studio persist. Tags do NOT sync via iCloud (local disk), but since Blindvault is only accessed from Mac Studio, this is fine.

Calendar (Apple/Google)

Color categories

Map calendar colors to the system where applicable. Deadlines = Red. Ongoing projects = Orange. Completed milestones = Green. Waiting/pending = Blue.

09 — Master Tag List (Ready to Create)

Below is every tag you need to create in Finder Preferences. This is the complete list — nothing more, nothing less. Create these once, then start tagging.

Status Tags (5 tags, with color)

#	Tag Name	Finder Color	Shortcut	Smart Folder?
1	Hot	Red	Ctrl-1	Yes — "All Hot Files"
2	In Flight	Orange	Ctrl-2	Yes — "All In Flight"
3	Done	Green	Ctrl-3	Optional
4	Waiting	Blue	Ctrl-4	Yes — "Blocked Items"
5	Reference	Purple	Ctrl-5	Yes — "Reference Library"

Project Tags (9+ tags, no color)

Tag Name	Scope
p:Blindspot	Channel-wide assets, branding, strategy
p:EP01	Soviet Revenge
p:EP02	Right-Wing Socialism
p:EP03 – p:EP07	Future episodes (create on demand)
p:Substack	Newsletter
p:Spotify	Playlist tracking
p:Studio	Equipment, camera, gear
p:Albania	Legal, property, government
p:Accenture	Employment (own files only)

Topic Tags (7 tags, no color)

Tag Name	Cross-Project Theme
#Politics	US politics, institutional critique
#History	WWII, Cold War, French Revolution, parallels
#Economics	Housing, inequality, tariffs, wealth
#Geopolitics	EU, Albania, NATO, foreign policy
#Media	Press, algorithms, attention economy
#Health	Medical, ACC, Francis
#Production	Camera, editing, audio, DaVinci, studio

Total Tag Count: 21

5 status (colored) + 9 project (text) + 7 topic (text) = 21 tags. This is your complete universe. The V3 system had 33+ tags including granular type tags and episode-specific sub-tags. You cut 36% and lost zero functionality because folder structure + file extensions already encode what the type tags were trying to say.

10 — Implementation Playbook

Session 0: Setup (15 minutes)

Open Finder > Settings > Tags. Remove Yellow and Gray from the favorites bar.
Rename the 5 remaining default color tags: Red → "Hot", Orange → "In Flight", Green → "Done", Blue → "Waiting", Purple → "Reference". (Note: "Hot" appears twice in FavoriteTagNames — duplicate entry.)
Verify shortcuts: Ctrl-1 through Ctrl-5 should map to your 5 status tags in order.
Create all 9 project tags (p:Blindspot, p:EP01, etc.) — do NOT assign a color. p:Blindspot, p:Albania, p:Accenture, p:Spotify in use. p:EP01–EP07, p:Substack, p:Studio show zero tagged files.
Create all 7 topic tags (#Politics, #History, etc.) — do NOT assign a color. Zero files found for any topic tag. Entire layer missing.
Remove any old tags from V3 that no longer exist (Active, In Progress, Paused, Inbox, Archive, all t: type tags). Active, In Progress, Paused, Archive = zero files (good). "Inbox" still has 3 tagged files.
Remove color labels from Document folders (Health, Work, Academia, etc.) — colors are for files, not folders. 20+ folders still carry Hot or Reference tags. This is the system inverted — folders colored, files naked.

Session 1: Hot Files First (30 minutes)

Open Documents/The Blindspot/. Tag every file you're actively working on as Hot. Hot tags found on Blindspot folders (Briefs, E01_Revenge, Media/*), not individual files.
Tag works-in-progress as In Flight. Zero files tagged "In Flight" system-wide.
Tag completed, shipped files as Done. Zero files tagged "Done" system-wide.
Tag anything waiting on external input as Waiting. 1 result: Blindspot/Pulse folder.
Tag templates, style guides, checklists as Reference. Reference applied to folders (Business Plan, Government, Financial, Books/*) — not files.
Skip project/topic tags for now. Status first.

Session 2: Documents Root + Financial + Government (45 minutes)

Tag everything in Financial/, Government/, Health/ — most will be Reference or Done. Folder-level Reference tags exist on Government, Financial. No file-level tagging detected.
Tag active legal matters (Albania POA, immigration) as Waiting or Hot. 3 POA files correctly tagged p:Albania. But status tags (Waiting/Hot) not applied to them.
Rename any UUID-named files sitting at the Documents root.

Session 3: Google Drive Folder Colors (15 minutes)

In Google Drive, right-click each active project folder > Change Color to match the system.
Active project folders (Blindspot Production, Pulse) = Red.
Archive/completed folders = no color or default gray.
Reference folders (templates, guides) = Purple if available, otherwise default.

Session 4: Hazel + Smart Folders (30 minutes)

Create Smart Folders: "All Hot Files" (tag = Hot), "All In Flight" (tag = In Flight), "All Waiting" (tag = Waiting), "Reference Library" (tag = Reference). 5 Smart Folders exist but all are V3 relics: "Active Projects" (queries "Active"), "Inbox - Needs Triage" (queries "Inbox"), "Blindspot Scripts", "Drafts In Progress", "Recent AI Outputs". None match Bible spec.
Configure Hazel: Downloads files older than 14 days with no tags → move to _Unsorted/ folder. Hazel v6.1.2 active, monitoring 1 folder. Rule definitions not readable remotely.
Configure Hazel: Screenshots older than 30 days with no tags → Trash. Same — Hazel running but rule content unverifiable.

The One Rule That Makes This Work

Every time you save a file, take 2 seconds to press Ctrl-1 through Ctrl-5. That's it. The entire system lives or dies on this one micro-habit. If you do it, the system maintains itself. If you don't, no taxonomy in the world will save you.

The Color Bible V1 Final

Contents