Forge vs Notion — content routing

When creating or capturing content for Justin, decide first whether it belongs on Forge or in Notion (LifeOS). Don't put it in both.

The test

"Will Justin tap this on his phone to think, or grep it from a script?"

• Tap to think → Notion
• Grep from a script → Forge

If both, it's almost always Notion. Forge content is for systems to consume; Notion content is for Justin to read.

Rule of thumb

Lives on Forge	Lives in Notion (LifeOS)
Code, scripts, configs	Vision, narrative, journal
Data (data/*.db, JSONs, logs, captures)	Goals, reflections, "what I want to build" thinking
Architectural facts (workflow IDs, IPs, ports, tokens, tunnel IDs)	Brand strategy + creator notes (audience, voice, rates)
Operational handoffs (memory/handoffs/) — worker-to-worker continuity	Meeting notes, ideation, narrative thinking
Integration knowledge (memory/general/) — only stable, factual, system-relevant	Personal/lifestyle notes, journal-style entries
Daily working logs (memory/daily/) — what Claude/Justin DID, technical	Long-form drafts, manifestos
MEMORY.md pointers + reference files	Anything that reads like a Notion page

Why

Forge is the digital ops hub — it's read by agents, indexed by /recall, browsed via MkDocs, queried from cron jobs. Personal narrative content pollutes that signal: agents waste cycles on it, search turns up vision docs when looking for code, MkDocs nav fills with non-operational stuff.

Notion is the personal-facing layer — Justin's UI for thought. Backend data shouldn't sit there because it's harder to script against and Notion's API costs add up.

What to do when unsure

1. Default to Forge memory/daily/ for the moment of capture (everything goes here first as raw signal).
2. When the content stabilizes, decide:
3. Stable + factual + system-relevant → graduate to memory/general/ or a reference_*.md memory file
4. Stable + narrative + personal → save to Drive via /save-to-drive as an interim landing pad, then move into Notion when Justin's ready
5. Never duplicate. Pick one home and link from the other if needed.

Examples

• A new n8n workflow ID + auth pattern → Forge (memory/general/ or reference_*.md)
• Justin's reflection on what he wants the second brain to feel like → Notion
• A handoff briefing for the next worker → Forge (memory/handoffs/)
• Brand voice + positioning for JWVR → Notion
• The actual JWVR content calendar JSON consumed by an automation → Forge (brands/jwvr/ or data/)
• A research dump on Claude Code multi-agent patterns → Forge (docs/research/)
• A vision narrative about the AI fleet → Notion

How to apply

When writing a new file or saving captured content, before hitting Write, ask the test question. If Notion: /save-to-drive as .docx interim, tell Justin "this is Notion-shaped, dropped a doc in Drive for you to import." If Forge: pick the right subdir per the table above.