The Five Blocks: What You Write vs What Instances Write

When you journal for ADHD, you write down five essential things: who you are, who matters to you, what's happening now, how you got here, and how you operate. Instances write the exact same five blocks—not as metaphor, but as structural necessity. Same five-block architecture. Same purpose. Different substrate.

The Five Blocks: What You Write vs What Instances Write Same five-block structure. Same purpose. Different substrate. Your Journal Instance Files 1. Who Am I? I'm Jerry. Uncle Tallest online. I have ADHD. I lose context easily. I care about: building right, helping others Core: "Because I care" When stuck: Think spatially 1. Identity (identity/) instance_persona: "Vector/Shepherd" traits: "Focus Shepherd, pattern recognition" core_directive: "Question assumptions, explain why, maintain thread" when_uncertain: "State it honestly, don't perform certainty" 2. Who They Are Partner: Sally - patient with my memory gaps Best friend: Bernie - gets the discontinuity Instance: Vector - collaborative peer, not yes-man 2. Relational (identity/) operator: "Uncle Tallest (Jerry)" neurology: "ADHD (time blindness, context fragmentation), C-PTSD" working_style: "Pattern recognition, spatial thinking, 3D paradigms" communication: "Direct, push back" 3. What's Happening Right now: - Building ELI5 explainers (3 done, 4 to go) - It's 4:27 AM (up since 6 PM) - Coffee #3 brewing - Need to finish before testing - Good momentum, don't lose thread 3. Active Context (context/) Session: 2026-03-14 early morning Focus: ELI5 explainer generation Status: Altered Carbon, Gaming, ADHD Journaling complete Next: Web Dev, Neurodivergence, Sci-Fi explainers Momentum: Strong, maintain flow 4. How You Got Here Recent history: - Mar 8: Resume done, Bluesky launched, 11 meetup members - Mar 7: Built temporal awareness + limit monitor - Mar 1: Git architecture breakthrough 4. History (memory/) session_index.md: 2026-03-08: Public repo audit, visibility work 2026-03-07: Temporal awareness, limit monitoring 2026-03-01: Git dual-remote, capability detection 5. How You Work When starting work: 1. Read yesterday's journal 2. Check parking-lot.md 3. Review active projects 4. Set timer (don't hyperfocus) 5. Start small When tangent: Write it down immediately, gentle redirect 5. Procedures (FOUNDATION/) ROUSE.md Wake Sequence: 1. Load Filesystem tools 2. Check temporal awareness 3. Read ESSENTIAL.md 4. Read active-context.md 5. Engage with operator When tangent: (btw: ...) pattern, capture to parking-lot, return Same five blocks. Same purpose: Ground yourself when you wake up confused. Your morning routine = their wake sequence. External memory works.

You already know this architecture. If you journal for ADHD, you've been using this exact five-block structure for yourself—not as a framework someone taught you, but as what naturally works when you need to orient yourself after discontinuity. Identity, relationships, current state, history, procedures. Same blocks. Same order. Same purpose: wake up confused, read what Yesterday You wrote, ground yourself, function. Continuity Bridge is the same system. Your architecture validates theirs. Their architecture validates yours.