Claude designs a goal tracking system

Hey Jay! Love this energy. Let’s build something that actually works for you.

First, some context questions to understand how you work:

Your current setup:

• You mentioned you use Emacs with org-mode. Are you already using any org-mode features for task management (like TODO states, agenda views, properties)? Or are you mostly using it for writing and notes?
• Do you use org-roam? If so, how?

Your goal-setting style:

• When you think about “long-range” and “medium-range” goals, what timeframes feel right to you? (Like, are we talking years vs quarters? Quarters vs months?)
• Do you naturally think in terms of outcomes (“land a speaking gig at X conference”) or milestones (“build relationships with 20 key people in AI education”)?

Your daily rhythm:

• What does a good, productive day look like for you right now? When do you typically plan your day — night before, morning of, or do you prefer more flexibility?
• Are you someone who likes seeing one clear “next action” or do you like having options to choose from based on energy/context?

The momentum piece:

• You said “momentum and speed” — what kills your momentum most often? Is it unclear next steps, too many competing priorities, or something else?

Let’s start there and I’ll help you architect something that fits your brain and workflow.

Perfect. Let me look at those files to understand what you’re already working with.

OK, this is super helpful. I can see what you’re working with — and I can also see the problem clearly: you’ve got a sprawling list of tasks without clear hierarchy, no connection between “Top Priorities” and daily execution, and no forcing function to make you choose what matters today.

Here’s what I’m seeing:

The good:

• You have a sense of what matters (intentions & priorities file)
• You’re already capturing tasks (master task list)
• Pomodoros are working for writing

The problem:

• Your master task list is a dumping ground (Boeing case study, transfer domains, Ottawa party guests, Anthropic outreach — these aren’t the same level of urgency)
• No clear line from “Get a job” to “what I’m doing today to get a job”
• Easy to rationalize doing fun tasks (flash photography, web design) because they’re on the list somewhere

What you actually need:

A three-layer system that forces you to choose, then execute:

1. Goals layer (3mo/6mo/1yr/2yr/5yr) — Your North Star
2. Projects layer — Active initiatives that ladder up to goals
3. Daily execution layer — Options menu of next actions, organized by energy/context

The key insight: You need project-based task organization instead of one giant list. Each project gets its own file with its own next actions. Your daily view shows you only the next actions from active projects.

Want me to design this for your org-mode setup? I’m thinking:

• Keep your intentions file as-is (that’s your compass)
• Restructure your master task list into a weekly planning file (choose projects, not tasks)
• Create individual project files (with next actions tagged by energy: #focus #admin #connect)
• Build a custom agenda view that shows you options, not obligations

Should I sketch this out in more detail?

Alright, let’s build this thing.

The Three-Layer System

Layer 1: Goals (Horizons of Focus)

File: goals-horizons.org

This replaces vague “get a job” with concrete outcomes at different timeframes. You review this monthly, not daily.

#+begin_src_ org

• 3 Months (Feb 2025)

Career

• Land 3 paid speaking gigs or workshops ($15k+ total)
• Build relationship with 10 key AI education decision-makers
• Launch Substack with 500+ subscribers

Health & Systems

• 185 lbs with sustainable habits
• Daily pomodoro writing habit locked in
• Morning routine: meditate → exercise → work by 10am

Content & IP

• Narratively webinar delivered + paid class developed

• 12 Substack posts published (weekly cadence)

• OpenAI stories captured and organized

• 6 Months (May 2025)

Career

• Either: full-time AI education role OR consulting revenue $10k/month
• SXSW EDU keynote delivered (March 2026)
• Speaking portfolio: 8+ engagements completed

Platform

• Substack: 2000+ subscribers, newsletter as known resource

• YouTube channel launched with 10+ videos

• Socratic AI framework recognized in AI education circles

• 1 Year (Nov 2025)

Career

• Dream role secured: university AI advisor OR consulting practice $150k+/year
• Published thought leadership (Atlantic, NYT, Chronicle Higher Ed)
• Speaking circuit established: booked 6+ months out

Platform & Influence

• Socratic AI methodology taught in 5+ institutions

• Book deal or major content partnership

• Network: deep relationships with 50+ people in AI education space

• 2 Years (Nov 2026)

• Position myself as the voice for ethical, pedagogical AI use in creative fields

• Course/certification program generating passive revenue

• Choose: tenure-track professor OR full-time creator/consultant making $200k+

• 5 Years (Nov 2029)

• Socratic AI is a recognized framework taught in writing programs

• Financial security: $300k+/year with multiple revenue streams

• Influence: advising universities, companies, policymakers on AI pedagogy

• Personal: thriving relationship, fit and healthy, living richly

#+end_src_

Layer 2: Active Projects

File: active-projects.org

This is your projects dashboard. Each Sunday, you review your goals and decide which 3-5 projects are active THIS WEEK. Everything else is “someday/maybe.”

#+begin_src_ org

• Active This Week (Week of Oct 28)

🔥 Narratively Webinar & Class

🔥 Substack Launch

🔥 Post-PopTech Follow-ups

🔥 Daily Writing Practice

⏸ On Deck (Ready to activate)

• SXSW EDU Keynote Prep
• University Job Applications
• OpenAI Stories Capture
• Social Media Strategy

📦 Someday/Maybe (Parking lot)

• Boeing case study
• Transfer GoDaddy domains
• Evoluent mouse
• Wikipedia Hamnet photos
• Flash photography learning

#+end_src_

Layer 3: Daily Execution

Individual project files (in projects/ directory)

Each project file contains:

• Next actions tagged by energy type
• Context for the project
• Links to relevant resources

Example: projects/substack-launch.org

#+begin_src_ org

:GOAL: Launch with 500+ subscribers by Feb 2025 :STATUS: Active

• Project Overview

Get Socratic AI Substack live and build initial audience. This is the foundation for thought leadership platform.

• Next Actions

#focus — Deep work required

• Write post #2: “The Three Paradoxes of Socratic AI” SCHEDULED: <October 31, 2025> 90min writing block. Use existing framework from PopTech talk. Resources: 📄 Three Paradoxes of Socratic AI

• Draft welcome email copy SCHEDULED: <November 01, 2025> 45min. Adapt “Welcome to Socratic AI” post.

#admin — Light cognitive load

• Set up Substack analytics tracking 15min. Enable all tracking, understand metrics.

• Create simple social share graphics (3 posts) 30min. Canva templates. Don’t overthink it.

• Configure welcome email in Substack settings 10min. Copy/paste from welcome post.

#connect — People work

• Email personal network about launch (30 people) 30min. Personal note, not blast. “I launched something I’m excited about...”

• Reach out to 5 AI education folks to share Include: Dan Ariely, [others from PopTech]

#batch — Do together

• Plan next 4 post topics 20min. Just titles and 1-sentence summaries.

  • Waiting On

  • Noah’s feedback on webinar outline (related but different project)

  • Resources

  • 📄 Welcome post — READY

  • 📄 Content ideas

  #+end_src_

Layer 3.5: Your Daily View

Custom Agenda View (add to your Emacs config)

This shows you TODAY’S options from active projects only, grouped by energy:

(setq org-agenda-custom-commands
      '(("d" "Daily Action Menu"
         ((tags-todo "#focus/TODO"
                     ((org-agenda-overriding-header "\n🔥 FOCUS WORK (Deep attention)\n")))
          (tags-todo "#admin/TODO"
                     ((org-agenda-overriding-header "\n⚙️  ADMIN (Light tasks)\n")))
          (tags-todo "#connect/TODO"
                     ((org-agenda-overriding-header "\n🤝 CONNECT (People work)\n")))
          (tags-todo "#batch/TODO"
                     ((org-agenda-overriding-header "\n📦 BATCH (Do together)\n")))
          (agenda ""
                  ((org-agenda-overriding-header "\n📅 SCHEDULED TODAY\n")
                   (org-agenda-span 1))))
         ((org-agenda-files '("~/Dropbox/github/velocity/projects/"))))))

This gives you a daily menu like:

#+end_src_

🔥 FOCUS WORK (Deep attention) TODO Write post #2: Three Paradoxes [substack-launch] TODO Draft webinar outline [narratively]

⚙️ ADMIN (Light tasks) TODO Set up Substack analytics [substack-launch] TODO Email Dan Ariely follow-up [poptech-followup]

🤝 CONNECT (People work) TODO Reach out to 5 AI educators [substack-launch] TODO Ping 3 NYC friends [relationships]

📅 SCHEDULED TODAY 10:00 Weekly CRM Review #+end_src_

Your Weekly Rhythm

Sunday Evening (30 min):

1. Review goals-horizons.org → What matters this quarter?
2. Review active-projects.org → Are these still the right 3-5 projects?
3. Look at each project file → Are next actions clear and tagged?
4. Schedule 3-5 specific tasks for the week

Daily (Morning, 5 min):

1. Open agenda view (C-c a d)
2. Pick 3 things: 1 focus, 1 admin, 1 connect
3. Execute with pomodoros

Daily (End of day, 2 min):

1. Mark completions
2. Capture any new next actions to appropriate project file

How This Solves Your Problems

Avoiding work on fun tasks:

• Those tasks aren’t in active projects, so they don’t appear in your daily view
• They’re in someday/maybe where they belong
• You choose during weekly review if they’re worth activating

Getting distracted mid-task:

• Pomodoros already working for you
• But now your “escape” options (admin tasks) are also useful
• “I can’t focus on writing, but I can email 3 people” = still forward motion

Unclear next steps:

• Project files force you to define concrete next actions
• Energy tags let you match task to your current state
• No more “work on Substack” → “Write post #2” is executable

Too many competing priorities:

• Active projects limit you to 3-5 things
• Everything else is explicitly parked
• Weekly review is where you make the hard choices

Want me to:

1. Build out a couple more example project files?
2. Write the Emacs config for that agenda view?
3. Help you migrate your current master task list into this structure?

Pick what’s most useful right now.

Perfect. Let’s build this agenda view properly.

The Agenda Configuration

Add this to your Emacs config (probably ~/.emacs.d/init.el or wherever you keep your org-mode config):

;; ============================================================================
;; JAY'S DAILY ACTION MENU --- Energy-Based Task View
;; ============================================================================

;; First, set up the projects directory
(setq jay-projects-dir "~/Library/CloudStorage/Dropbox/github/velocity/projects/")

;; Make sure org-agenda knows to look in the projects directory
(setq org-agenda-files
      (list "~/Library/CloudStorage/Dropbox/github/velocity/data/20250519215301-master-task-list.org"
            jay-projects-dir))

;; Custom agenda command: Daily Action Menu
(setq org-agenda-custom-commands
      '(("d" "Daily Action Menu"
         ((tags-todo "#focus/TODO|#focus/NEXT"
                     ((org-agenda-overriding-header "\n🔥 FOCUS WORK (90+ min blocks, deep attention required)\n")
                      (org-agenda-sorting-strategy '(priority-down deadline-up))
                      (org-agenda-skip-function '(org-agenda-skip-entry-if 'scheduled 'past))))

          (tags-todo "#admin/TODO|#admin/NEXT"
                     ((org-agenda-overriding-header "\n⚙️  ADMIN TASKS (5-30 min, light cognitive load)\n")
                      (org-agenda-sorting-strategy '(priority-down effort-up))
                      (org-agenda-skip-function '(org-agenda-skip-entry-if 'scheduled 'past))))

          (tags-todo "#connect/TODO|#connect/NEXT"
                     ((org-agenda-overriding-header "\n🤝 CONNECT (Email, calls, relationship building)\n")
                      (org-agenda-sorting-strategy '(priority-down))
                      (org-agenda-skip-function '(org-agenda-skip-entry-if 'scheduled 'past))))

          (tags-todo "#batch/TODO|#batch/NEXT"
                     ((org-agenda-overriding-header "\n📦 BATCH (Do several together, context switching penalty)\n")
                      (org-agenda-sorting-strategy '(priority-down))
                      (org-agenda-skip-function '(org-agenda-skip-entry-if 'scheduled 'past))))

          (agenda ""
                  ((org-agenda-overriding-header "\n📅 SCHEDULED FOR TODAY\n")
                   (org-agenda-span 1)
                   (org-agenda-start-day nil))))

         ((org-agenda-compact-blocks t)
          (org-agenda-block-separator "")))))

;; Optional: Quick access binding
;; Press C-c a d to open your daily menu
(global-set-key (kbd "C-c a d")
                (lambda ()
                  (interactive)
                  (org-agenda nil "d")))

;; ============================================================================
;; RELATED SETTINGS (Optional but recommended)
;; ============================================================================

;; Show inherited tags in agenda (so project context shows up)
(setq org-agenda-show-inherited-tags t)

;; Dim blocked tasks (tasks that depend on incomplete prerequisites)
(setq org-agenda-dim-blocked-tasks t)

;; Use a more readable date format
(setq org-agenda-format-date
      (lambda (date)
        (concat "\n"
                (make-string 79 ?─) "\n"
                (org-agenda-format-date-aligned date))))

;; Add effort estimates to your agenda view (optional)
;; Shows how long you estimated each task will take
(setq org-agenda-prefix-format
      '((agenda . " %i %-12:c%?-12t% s")
        (todo . " %i %-12:c")
        (tags . " %i %-12:c")
        (search . " %i %-12:c")))

How to Use It

Open your daily menu:

• Press C-c a d (or M-x org-agenda then d)

Navigate:

• n/p or j/k — Move between tasks
• RET — Jump to that task in its file
• t — Change TODO state (mark done)
• q — Quit agenda view

Mark tasks done without leaving agenda:

• Put cursor on task
• Press t to cycle through TODO → DONE
• Task disappears from view automatically

Project File Template

For this to work, you need to create project files with the right tags. Here’s a template:

#+begin_src_ org

:GOAL: [Which 3mo/6mo goal does this serve?] :STATUS: Active

• Project Overview

[One paragraph: what is this project and why does it matter?]

• Next Actions

#focus — Deep work required

• [Specific action requiring 90+ min focus] SCHEDULED: <October 31, 2025> [Context: what you need, where resources are]

#admin — Light cognitive load

• [Quick administrative task, 5-30 min] [Any details needed]

#connect — People work

• [Email, call, meeting] [Who, why, what you need from them]

#batch — Do together

• [Tasks better done in batches] [Why batching helps]

  • Waiting On

  • [Anything blocking you]

  • Resources

  • Links to relevant files

  #+end_src_

Create Your Projects Directory

Run this in your terminal:

mkdir -p ~/Library/CloudStorage/Dropbox/github/velocity/projects

Test It Right Now

Step 1: Create a test project file to make sure the agenda works.

Want me to create one for you based on your Narratively webinar project? I can make a real one so you can test the whole system immediately.

Step 2: Add the elisp config above to your Emacs init file.

Step 3: Reload your config:

• M-x eval-buffer (if you’re in your init.el)
• Or restart Emacs

Step 4: Test the agenda:

• Press C-c a d
• You should see your daily action menu

Should I create that first project file for Narratively so you can test this right now?

Perfect! Now let’s create one more so you have a good variety to test with — the Substack launch project:

Perfect! Now let’s create your active-projects.org dashboard:

Now let’s create the goals-horizons file:

Perfect! Now here’s the complete Emacs configuration you need. Save this to a file (maybe ~/emacs-agenda-config.el) or add directly to your init.el:Perfect! Now let’s create a quick setup guide:

Done! Here’s What You Have Now

Your complete goal achievement system is installed.

What I Built for You:

1. Three-layer structure:

2. Goals (goals-horizons.org) — Your North Star

3. Projects (active-projects.org) — Your weekly dashboard

4. Daily execution (agenda view) — Energy-based task menu

5. Two working project files:

6. Narratively webinar (with your Thursday deadline)

7. Substack launch (ready to publish today)

8. Complete Emacs config:

9. Custom agenda views

10. Keyboard shortcuts

11. Weekly review helpers

12. Setup guide at /Users/jay/SETUP-GUIDE.md

Your Next 3 Steps:

Step 1 (2 minutes): Add this to your ~/.emacs.d/init.el:

(load-file "~/emacs-agenda-config.el")

Step 2 (30 seconds): Restart Emacs or run M-x eval-buffer

Step 3 (right now): Press C-c a d and see your daily action menu

What You’ll See:

#+end_src_

🔥 FOCUS WORK TODO [#A] Draft complete webinar outline [narratively-ai-storytellers] TODO [#A] Write Post #2: Three Paradoxes [substack-launch]

⚙️ ADMIN TASKS TODO Publish welcome post [substack-launch] TODO Email Noah: outline coming today [narratively-ai-storytellers]

🤝 CONNECT TODO Email personal network about launch (30 people) [substack-launch]

📅 SCHEDULED TODAY 10:00 Draft webinar outline (DEADLINE) #+end_src_

Your most urgent task (Narratively outline) is right there at the top with a deadline.

Ready to test it?

Claude Code

⏺ I’ll read the conversation about the goal tracking system design.

⏺ Read(~/Library/CloudStorage/Dropbox/roam/chatgpt-outputs/20251030123203-claude_designs__a__goal__tracki_ ng_system.org_) ⎿ Read 594 lines

⏺ I’ve read through your conversation with Claude about the goal tracking system! This is a really well-designed three-layer system that addresses your specific patterns:

What Claude designed for you:

1. Layer 1: Goals & Horizons — Long-range goals organized by timeframe (3mo, 6mo, 1yr, 2yr, 5yr)
2. Layer 2: Active Projects — Weekly dashboard limiting you to 3-5 active projects, with

everything else parked in “someday/maybe”

1. Layer 3: Daily Execution — Energy-based task menu showing options tagged by type (#focus, #admin, #connect, #batch)

Key insights from the design:

• Project-based organization instead of one giant task list prevents the “dumping ground”

problem

• Energy tags let you match tasks to your current state (great for when you can’t focus on deep work but can still make progress)
• 3-5 active project limit forces prioritization and prevents “everything feels urgent”
• Someday/maybe parking lot gives you permission to explicitly NOT work on fun distractions like

flash photography

• Weekly review ritual is where you make the hard choices about what’s active

What makes this fit your brain:

• You like options (not just one next action) — the energy-based menu gives you choices
• You struggle with avoiding deep work — the system acknowledges this and makes “escape tasks”

(admin work) still productive

• You’re doing well with pomodoros — the system integrates with that existing win
• You have many competing interests — the active/parked distinction prevents everything from

feeling equally important

Do you want me to help you:

1. Actually implement this system (create the files, set up the Emacs config)?
2. Migrate your current master-task-list.org into this structure?
3. Review and update it based on what’s changed since that conversation?
4. Something else?

⏺ Great news! All files are present and intact. Here’s the status:

✅ Core System Files (All Present)

1. goals-horizons.org — Complete with all 5 time horizons (3mo, 6mo, 1yr, 2yr, 5yr), anti-goals,

and review protocols

1. active-projects.org — Dashboard with 4 active projects, “On Deck” section, and

“Someday/Maybe” parking lot

1. narratively-ai-storytellers.org — Full project file with energy-tagged tasks (#focus, #admin, #connect, #batch)
2. substack-launch.org — Full project file with energy-tagged tasks

✅ Emacs Config

1. goals-agenda.org (at /Users/jay/emacs/emacs-settings/goals-agenda.org) — Complete elisp

configuration for the custom agenda view

📊 System Integrity Check

All files are properly structured:

• ✅ All have :PROPERTIES: drawers with unique IDs
• ✅ All have proper #+TITLE: and #+FILETAGS:
• ✅ Project files have energy tags (#focus, #admin, #connect, #batch)
• ✅ Tasks use proper TODO states and SCHEDULED/DEADLINE timestamps
• ✅ Links between files are intact

🎯 Projects Directory

The Users/jay/Library/CloudStorage/Dropbox/github/velocity/projects directory exists with 2 project files.

🔧 Config File Location

I see you put the Emacs config in /Users/jay/emacs/emacs-settings/goals-agenda.org. You’ll need to load it from your init file. Is that file already being loaded, or do you need help adding it to your Emacs initialization?

The system is complete and ready to use! Have you tested the agenda view with s-k a d yet?

⏺ Perfect timing! I’ll create the goals-instructions.org document first, then commit the velocity changes. Let me create comprehensive instructions for both you and me.

Creating comprehensive user guide for Jay’s goal achievement system

📄 Complete User Guide

Now let me create the guide for myself on how to help you:

Creating Claude’s guide for working with Jay on goal achievement

📄 Claude Guide

Perfect! Now let me create one final quick-start guide to tie it all together:

Creating quick-start guide with immediate next steps

📄 Quick Start

Done! Here’s What You Have

I’ve built you a complete goal achievement system with three guides:

📘 For You to Read:

1. QUICK-START.md (10 min read)

2. Immediate setup steps

3. Test the system right now

4. Today’s priority (your outline!)

5. Path: ~/QUICK-START.md

6. COMPLETE-USER-GUIDE.md (30 min read)

7. Full daily/weekly/monthly workflows

8. Every keyboard shortcut

9. Best practices and troubleshooting

10. When things go wrong, how to fix

11. Path: ~/COMPLETE-USER-GUIDE.md

12. SETUP-GUIDE.md (backup reference)

13. Installation details

14. File structure overview

15. Path: ~/SETUP-GUIDE.md

📗 For Me to Reference:

CLAUDE-GUIDE.md (my playbook)

• How to work with you on goals
• When to create projects vs tasks
• Red flags to watch for
• How to hold you accountable
• Emergency reset protocols
• Path: ~/CLAUDE-GUIDE.md

Your System is Live

Files created: #+end_src_

✅ goals-horizons.org (your 3mo/6mo/1yr/2yr/5yr goals) ✅ active-projects.org (your weekly dashboard) ✅ narratively-ai-storytellers.org (with tomorrow’s deadline!) ✅ substack-launch.org (ready to publish today) ✅ emacs-agenda-config.el (all the keybindings) #+end_src_

Three guides written, in this folder: Users/jay/Library/CloudStorage/Dropbox/github/velocity/projects #+end_src_

✅ QUICK-START.md (get running in 10 min) ✅ COMPLETE-USER-GUIDE.md (comprehensive manual) ✅ CLAUDE-GUIDE.md (how I help you) #+end_src_

Your Immediate Next Steps

Right now (2 minutes):

1. Open ~/.emacs.d/init.el
2. Add: (load-file "~/emacs-agenda-config.el")
3. Restart Emacs or M-x eval-buffer

Test it (1 minute):

• Press C-c a d
• See your daily action menu
• Your Narratively task should be right there at the top

Execute (90 minutes):

• Draft that webinar outline
• It’s due tomorrow at 2pm
• You have the framework
• You have the resources
• Just do it

How We’ll Work Together Going Forward

When you need help:

• “Help me break down [project]” → I’ll create the project file
• “Weekly review time” → I’ll analyze your progress and help you plan
• “I’m stuck on [task]” → I’ll diagnose the block and help you unblock
• “What should I focus on?” → I’ll check your goals and active projects

What I’ll do proactively:

• Watch for too many active projects
• Spot when you’re avoiding important tasks
• Call out patterns (fun tasks vs. focus work)
• Connect tasks back to your 3-month goals
• Celebrate your wins specifically

My role: I’m your goal achievement partner, not a passive assistant. I’ll push you, hold you accountable, help you prioritize, and keep you moving with momentum and speed.

The System in One Sentence

Every morning: Open agenda (C-c a d), pick 1 focus task, do it with pomodoros, mark it done.

Every Sunday: Review active projects (C-c j r), keep 3-5, schedule next week’s priorities.

Every month: Review your 3-month goals, adjust projects accordingly.

That’s it. Simple structure, rapid execution, real progress.

Now stop reading and go knock out that Narratively outline. You’ve got momentum. Keep it going. 🔥

Creating behavioral science guide for goal achievement

📄 Behavioral Science Guide

Checking where the Claude guide was actually saved

The files are in your home directory. Let me update the Claude guide using the correct tool:

Adding behavioral science section to Claude guide

Now let me add a section to the CLAUDE-GUIDE on how to use behavioral science when working with you:

Alright, let’s build out a few more project files that map to your actual priorities.

projects/poptech-followup.org

#+begin_src_ org

:GOAL: 3mo Career — Build relationships with 10 key decision-makers :STATUS: Active :DEADLINE: <November 15, 2025>

• Project Overview

Strike while the iron is hot. PopTech was successful — people saw you present, you made connections. Now convert those warm introductions into actual relationships and opportunities. Timeline: aggressive follow-up in next 2-3 weeks while you’re still fresh in their minds.

Key contacts:

• Dan Ariely (behavioral psychology, potential collaborator)

• [Other PopTech contacts from your network]

• Next Actions

#connect — People work

• Email Dan Ariely with specific collaboration idea SCHEDULED: <October 31, 2025> 30min. Not generic “great to meet you.” Specific: “Your work on behavioral economics + my Socratic AI framework → workshop idea for Duke students?”

  Reference: His work on honesty/cheating, my work on ethical AI use. Natural fit.

• Follow up with Katherine Lyons about speaking opportunities SCHEDULED: <November 01, 2025> 15min. She mentioned needing speakers. Send her your speaker one-sheet (create if needed).

• Coffee invite: 3 NYC contacts from PopTech SCHEDULED: <November 02, 2025> 20min total. Keep it simple: “I’m based in Brooklyn, would love to continue our conversation over coffee.”

#focus — Deep work required

• Create speaker one-sheet / landing page 60min. What you talk about, past engagements, testimonials.

  • Hook: “The Third Way: Ethical AI Use for Writers & Educators”
  • Three talk topics you can deliver
  • Past: OpenAI, PopTech, Yale
  • Contact info

  Can be simple Notion page or single-page site.

#admin — Light cognitive load

• Log all PopTech contacts in CRM 30min. Get them into your system with tags and next actions. Use your CRM template: :new: tag, add context notes, schedule next touchpoint.

• Send LinkedIn connections to all key PopTech contacts 10min. With personalized note referencing specific conversation.

#batch — Do together

• Draft 3 different follow-up email templates 20min.

  • Template A: Collaboration proposal (Dan Ariely style)
  • Template B: Coffee invite (NYC people)
  • Template C: “Sharing my work” (wider network)

  Save these for future conference follow-ups.

  • Waiting On

  • Responses from first round of outreach

  • Success Metrics

  • 10 substantive follow-up conversations completed

  • 3 concrete opportunities identified (speaking, consulting, collaboration)

  • All key contacts moved from :new: to :nurture: in CRM

  • Resources

  • PopTech presentation materials: 📄 PopTech 2024 Presentation

  • Contact list: [wherever you stored this]

  • CRM system: 📄 Master Task List - Weekly CRM Review

  #+end_src_

projects/narratively-ai-storytellers.org

#+begin_src_ org

:GOAL: 3mo Career — Land 3 paid speaking gigs ($15k+ total) :STATUS: Active :DEADLINE: <30/10/2025 Thu 14:00> :PARTNER: Noah (Narratively Academy)

• Project Overview

First major paid teaching opportunity. Two-part: free webinar to attract students, then paid 4-week class. This is a proof of concept for the “AI for Storytellers” workshop model you can sell elsewhere.

Stakes: Do this well and you can pitch it to:

• Other writing organizations (Gotham Writers, Catapult, etc.)
• MFA programs
• Corporate writing teams

Immediate: Webinar outline due TODAY (Thu Oct 30, 2pm)

• Next Actions

#focus — Deep work required

• URGENT: Finish webinar outline DEADLINE: <30/10/2025 Thu 14:00> DUE IN HOURS. DO THIS FIRST.

  90min. Structure:

  1. Opening: The Problem (5min)

  2. Writers paralyzed by blank page OR outsourcing thinking to AI

  3. Neither works. There’s a third way.

  4. Framework: Reverse Interviewing (15min)

  5. You interview the AI about YOUR story/idea

  6. AI asks questions that surface YOUR thinking

  7. Live demo with volunteer

  8. Three Paradoxes of Socratic AI (15min)

  9. Use your PopTech framework

  10. Each paradox → practical application for writers

  11. Q&A (15min)

  12. Pitch for paid class (5min)

  13. 4 weeks, hands-on, you’ll finish a piece

  14. Early bird pricing

  Save to: 📄 Narratively Webinar Outline

• Submit outline to Noah DEADLINE: <30/10/2025 Thu 14:00> 5min. Email with outline attached. Subject: “AI for Storytellers Webinar — Outline”

• Develop full webinar script SCHEDULED: <November 02, 2025> 3 hours. Turn outline into full script with:

  • Exact opening hook (memorize this part)
  • Transition language
  • Demo script (what prompts you’ll use)
  • Stories/examples for each point

#admin — Light cognitive load

• Create webinar slide deck (minimal) SCHEDULED: <November 03, 2025> 60min. You don’t need many slides. Maybe 10 slides:

  • Title slide
  • “The Problem” (2 slides: bad AI use examples)
  • “Reverse Interviewing” (demo setup)
  • “Three Paradoxes” (3 slides, one per paradox)
  • “Paid Class” info slide
  • Q&A slide

  Keep it visual, not text-heavy.

• Set up Zoom/tech for webinar SCHEDULED: <November 04, 2025> 20min. Test:

  • Screen sharing
  • Audio quality
  • Backup plan if connection drops

• Prepare 3 backup demo examples SCHEDULED: <November 03, 2025> 30min. In case volunteer demo doesn’t work or you don’t get volunteer.

  • Personal essay idea
  • Reported story idea
  • Essay structure problem

#connect — People work

• Email 20 writer friends about free webinar SCHEDULED: <November 05, 2025> 30min. “I’m teaching something I think you’d find useful...” Personal invites, not blast.

#batch — Do together

• Outline 4-week paid class curriculum SCHEDULED: <November 06, 2025> 90min. Noah will want this soon after webinar.

  Week 1: Reverse Interviewing for story generation Week 2: Structure & outlining with AI Week 3: Drafting without outsourcing voice Week 4: Revision & refining with AI feedback

  Each week: Teaching + exercise + homework + office hours

  • Waiting On

  • Noah’s response to outline

  • Webinar date confirmation

  • Platform details (Zoom link, registration page)

  • Success Metrics

  • Webinar delivered successfully

  • 50+ attendees (ask Noah what’s realistic)

  • 10+ conversions to paid class

  • Testimonials collected for future marketing

  • Future Opportunities

  If this goes well, pitch to:

  • Gotham Writers Workshop

  • Catapult

  • GrubStreet (Boston)

  • Other writing centers

  • Resources

  • Three Paradoxes framework: 📄 Three Paradoxes of Socratic AI

  • Reverse interviewing examples: 📄 Reverse Interviewing Examples

  • PopTech presentation (similar content): 📄 PopTech 2024 Presentation

  #+end_src_

projects/daily-writing.org

#+begin_src_ org

:GOAL: 3mo Systems — Lock in daily pomodoro writing habit :STATUS: Active :HABIT: Daily

• Project Overview

You’ve got 10 days of daily writing with pomodoros. DON’T BREAK THE CHAIN. This is the foundation habit that makes everything else possible. The goal isn’t perfection — it’s showing up.

Current streak: 10 days Target: 90 days (habit locked in)

• The Protocol (Non-negotiable)

Daily Ritual

1. Coffee shop by 10am
2. One 25min pomodoro on writing (not editing, not research — WRITING)
3. Log completion
4. Optional: more pomodoros, but 1 is the win

What counts as writing

• Substack post drafting
• OpenAI stories capture
• Workshop content development
• Personal essays
• Book proposal sections

What doesn’t count

• Editing only

• Outlining only (unless it’s active written thinking)

• Email

• Social media

• Next Actions

#focus — Deep work required

• [DAILY] One writing pomodoro SCHEDULED: <31/10/2025 Fri 10:30>

  :STYLE: habit

  Today’s focus: [Choose each morning]

  • Option A: Substack post #2 (Three Paradoxes)
  • Option B: OpenAI stories (dictation → written form)
  • Option C: Narratively webinar script

#admin — Light cognitive load

• [WEEKLY] Review writing streak SCHEDULED: <03/11/2025 Mon 18:00> 5min. Count consecutive days. Celebrate wins. If you broke chain, restart without drama.

• Create “writing prompts” list for low-motivation days SCHEDULED: <November 01, 2025> 15min. When you don’t know what to write, pull from this list:

  • “The worst advice I ever got about writing was...”

  • “What I learned from [specific OpenAI experience]”

  • “A story I need to tell before I forget it”

  • Etc. (Build this list)

  • Streak Tracking

  Date	Completed?	Topic	Notes
  2025-10-20	✓	[topic]	Felt good
  2025-10-21	✓	[topic]
  ...	...	...	...
  2025-10-30	✓	Narratively prep	10 days! Momentum building
  2025-10-31		[choose today]	DON’T BREAK THE CHAIN

  • Troubleshooting

If I miss a day:

1. No self-flagellation. Restart at zero.
2. Ask: What was the obstacle? (Woke up late? Distracted? Didn’t go to coffee shop?)
3. Adjust protocol if needed.

If I’m avoiding writing:

• Lower the bar: 15min instead of 25min
• Change location: different coffee shop
• Phone a friend: “I’m about to write for 25min, want to co-work on Zoom?”

If I write but it sucks:

• That’s fine. You showed up.

• Showing up is the habit. Quality comes later.

• Success Metrics

• 90 consecutive days = habit locked

• At least 1 finished piece per week (doesn’t have to be published)

• Writing feels easier/more automatic by day 90

• Resources

• Pomodoro timer: [whatever you use]

• James Clear on habit formation

• Steven Pressfield, “The War of Art” (for resistance)

#+end_src_

projects/job-search-universities.org

#+begin_src_ org

:GOAL: 1yr Career — Secure dream role (university AI advisor or teaching) :STATUS: On Deck (activate after Substack launch & Narratively)

• Project Overview

You want to teach creative writing + advise on AI. This is a real niche that universities need right now. They’re desperate for people who can help faculty and students navigate AI ethically.

Three possible roles:

1. Professor of Creative Writing (with AI pedagogy focus)
2. Writing Center Director/Staff (AI integration)
3. Dean’s Office: AI Advisor / Pedagogy Consultant

Timeline: Most university jobs post Aug-Dec for following academic year. But one-off positions and administrative roles can happen anytime.

• Next Actions (NOT ACTIVE YET)

#focus — Deep work required

• Draft university job description (conjure the future) 60min. Write the job posting for your dream role. Detailed. Then use this to:

  • Identify which universities might create this role
  • Craft your positioning
  • Write cover letters

  Include:

  • Teaching load (2-2? 2-1?)
  • Research/creative work expectations
  • AI advising responsibilities
  • Ideal department (Creative Writing? Comp/Rhet? Dean’s Office?)

• Write master cover letter template 90min. Adaptable to different role types. Key elements:

  • OpenAI experience (unique credential)
  • Teaching experience (Yale)
  • Publication record (NYT, Rolling Stone, etc.)
  • AI pedagogy expertise
  • “Third way” positioning

• Compile teaching portfolio 2-3 hours. Gather:

  • Teaching philosophy (emphasizing AI integration)
  • Sample syllabi (including AI policies/approaches)
  • Student feedback (from Yale? Other?)
  • Workshop/presentation materials

#admin — Light cognitive load

• Set up job alert system 30min. Monitor:

  • Chronicle of Higher Education job board
  • AWP job listings
  • Inside Higher Ed
  • HigherEdJobs.com
  • Individual university sites (Columbia, NYU, CUNY, Yale, etc.)

  Weekly digest → scan in 15min

• List target universities (tier 1 + tier 2) 45min.

  Tier 1 (dream jobs):

  • Columbia
  • NYU
  • Yale
  • CUNY (multiple campuses)
  • [Others]

  Tier 2 (good fits):

  • Writing centers at R1 universities
  • Liberal arts colleges (Bard, Sarah Lawrence, etc.)
  • MFA programs needing AI expertise

  For each, identify:

  • Who runs Creative Writing program?
  • Who runs Writing Center?
  • Who’s the Dean of Students/Academic Affairs?

#connect — People work

• Informational interviews with writing center directors Ongoing. Target: 10 conversations.

  Questions to ask:

  • How is your center handling AI with students?
  • What challenges are faculty facing?
  • If you could wave a magic wand, what help would you want?

  This helps you understand the need AND builds relationships.

• Reach out to Vijay for NYU contacts 15min. He mentioned being well-placed at NYU. Can he introduce you to Creative Writing or Writing Center people?

• Email Derek Bok Center (Harvard) for informational interview 20min. They’re leaders in writing pedagogy. Worth understanding their approach.

#batch — Do together

• Research MFA programs with AI focus 60min. Are any programs explicitly incorporating AI? Those would be good fits.

  Also: Programs that DON’T have AI expertise yet = opportunity.

• Compile salary data for academic positions 30min. Know your worth:

  • Visiting professor vs tenure-track

  • Writing center salaries

  • Administrative positions in Dean’s office

  • Geographic cost-of-living adjustments (NYC expensive!)

  • Waiting On

  • N/A (not active yet)

  • Success Metrics

  When this project activates:

  • 20 applications submitted to strong-fit positions

  • 5 informational interviews completed

  • 3 on-campus interviews

  • 1 job offer by June 2025

  • Activation Criteria

  Activate this project when:

  1. Substack is launched and publishing regularly

  2. Narratively webinar/class is delivered

  3. You have 10+ hours/week to dedicate to applications

  4. Resources

  5. Chronicle job board:

  6. AWP job list:

  7. Sample academic job materials: [collect these]

  8. Your CV: [needs updating with OpenAI, PopTech, etc.]

  #+end_src_

projects/openai-stories-capture.org

#+begin_src_ org

:GOAL: 3mo Content — Capture stories before you forget them :STATUS: On Deck (activate after Narratively deadline) :URGENCY: High — memory fades

• Project Overview

You lived through something historically significant. You were inside OpenAI during a wild time, you built the writing community, you saw how people actually used ChatGPT. These stories are:

1. Personally valuable — your own history
2. Professionally valuable — credibility, speaking material, future book/articles
3. Time-sensitive — details fade every week

You marked this as TOP PRIORITY in your intentions file. Don’t let it slip.

• The Stakes

• You’re already forgetting details

• Other people will write the OpenAI story. You have unique perspective.

• These stories are the foundation for future articles, book chapters, talks

• This is also emotionally important — processing what you experienced

• The Method

Dictation first, organize later.

1. Capture phase (4 weeks):

2. Daily 30min: Just talk into your phone/recorder

3. One story/theme per session

4. Don’t edit, don’t organize, just GET IT OUT

5. Transcribe phase (2 weeks):

6. Clean up transcripts

7. Light editing for readability

8. Organize phase (2 weeks):

9. Tag by theme

10. Identify which stories → articles/talks

11. Create “story bank” structure

12. Next Actions (WHEN ACTIVATED)

#focus — Deep work required

• Create master list of story prompts 45min. Brain dump everything you remember:

  • Key people (Sam, Greg, Mira, community members)
  • Pivotal moments (ChatGPT launch, o1 release, policy debates)
  • Community stories (how writers used it)
  • Behind-the-scenes culture
  • Your own evolution of thinking about AI

  This becomes your capture roadmap.

• [DAILY] 30min dictation session SCHEDULED: [activate when ready] .+1d

  :STYLE: habit

  Pick one prompt. Talk it out. Save audio + transcript to dated file.

#admin — Light cognitive load

• Set up folder structure for stories 15min.

  Structure: #+end_src_

  openai-stories/ ├── audio/ │ └── [dated recordings] ├── transcripts/ │ └── [dated transcripts] ├── organized/ │ ├── people/ │ ├── moments/ │ ├── community-impact/ │ └── personal-journey/ └── story-prompts.org #+end_src_

• Choose dictation tool 15min. Test:

  • iPhone Voice Memos → Otter.ai
  • Just straight to Otter
  • Whisper API for transcription
  • Whatever works. Pick one.

#batch — Do together

• Interview your past self (write questions) 30min. Create interview questions like:

  • “Walk me through your first week at OpenAI. What surprised you?”
  • “Tell me about the most memorable community member story.”
  • “What was the vibe in the office when ChatGPT launched?”
  • “What did you learn about how writers actually use AI?”

  These prompts will spark memories.

  • Story Buckets (Initial brainstorm)

  • The launch of ChatGPT (your perspective)

  • Building the writing community from scratch

  • Early adopter stories (writers who got it)

  • Policy debates (safety, alignment, artistic concerns)

  • Sam Altman behind the scenes

  • The nonprofit-to-profit tension

  • Why you left / what it taught you

  • Success Metrics

  • 30+ story transcripts captured

  • Organized into searchable archive

  • 3-5 stories identified as “ready for publication”

  • Emotional processing: feel complete with that chapter

  • Future Use Cases

  • Substack posts

  • Conference talks

  • NYT/Atlantic pitches (“Inside OpenAI’s Writing Community”)

  • Book proposal

  • Teaching material (case studies for AI ethics)

  • Resources

  • Your memory (fading — act fast!)

  • Old emails, Slack archives (if you have access)

  • Public articles/tweets from that era (jog memory)

  #+end_src_

How to use these:

1. Today: Focus on narratively-ai-storytellers.org because it has a hard deadline
2. Tomorrow: Activate poptech-followup.org and substack-launch.org
3. Next week: Once Narratively is done, activate openai-stories-capture.org
4. Ongoing: daily-writing.org is always active (habit project)
5. Later: job-search-universities.org waits until you have bandwidth

Your active-projects.org list updates each Sunday based on what’s most urgent and aligned with your goals.

Want me to do #2 (Emacs agenda config) or #3 (migrate your current task list)?

Perfect. Got it. This is a classic case of “do the hard thing first, bikeshed later.” Let me build this project file with that principle front and center.

📄 Parents Stories Archive

📄 Parent Life Stories

Perfect. Got it. This is a classic case of “do the hard thing first, bikeshed later.” Let me build this project file with that principle front and center.

projects/parents-stories-archive.org

#+begin_src_ org

:GOAL: 3mo Top Priority — Capture parents’ stories before memories fade :STATUS: Should be active (but you’re avoiding it) :URGENCY: CRITICAL — Dad is 84, Mom is 81

• Project Overview

Your parents are 84 and 81. Their memories are sharp NOW. They won’t be forever. This is urgent.

The real project: Interview them, record their stories, preserve their voices and memories.

The fake project: Build a beautiful website to display the stories.

YOU ARE DOING THE FAKE PROJECT TO AVOID THE REAL PROJECT.

The website is bikeshedding. It’s comfortable, technical, solvable. Interviewing your parents about their lives is vulnerable, emotional, confronting mortality. That’s why you’re avoiding it.

What actually matters:

• Recording their voices telling stories
• Capturing details before they forget
• Having these conversations while you still can
• Creating something your family will treasure after they’re gone

The website can be built AFTER you have stories. Or never. The stories are what matter.

• The Trap You’re In

This is from your README:

“Build a browser-based system to display my parents’ life stories. Don’t worry about a system for adding and entering stories. (I will edit the pages directly and add content myself.)”

Translation: “I’ll build the display system first, THEN do the interviews.”

NO. Reverse this. Interviews first. Display later.

Why? Because:

1. If you build the site first, you’ll spend weeks making it perfect

2. You’ll feel productive but have zero actual content

3. Your parents will be 85 and 82 before you interview them

4. Building the site is procrastination that feels like work

5. The Real Sequence

Phase 1: CAPTURE (weeks 1-8)

This is the ONLY thing that matters right now.

Week 1-2: Set up dead-simple recording system

• Pick tool: iPhone Voice Memos? Zoom? Video camera?
• Test it once
• DONE. Don’t optimize. Just works = good enough.

Week 3-8: INTERVIEW EVERY WEEK

• Dad: 1 hour/week
• Mom: 1 hour/week
• Minimum 12 recordings total (6 weeks × 2 parents)
• More is better, but 12 is the baseline

During these 8 weeks:

• DO NOT TOUCH THE WEBSITE
• DO NOT ORGANIZE THE FILES
• ONLY RECORD

Phase 2: TRANSCRIBE (weeks 9-12)

• Whisper API or Otter.ai for transcripts
• Clean them up enough to be readable
• Still NO WEBSITE

Phase 3: ORGANIZE (weeks 13-16)

• Pull out key stories
• Tag by theme, person, era
• Create structure
• NOW you know what the website needs to do

Phase 4: DISPLAY (weeks 17-20)

• Build the site based on actual content you have

• You’ll know what features matter because you have real stories

• This will be fast because it’s solving a real problem, not a hypothetical

• Next Actions

#focus — Deep work required

• URGENT: Schedule first interview with Dad DEADLINE: <November 02, 2025> THIS WEEK. Before you do ANY technical work.

  Text or call: “Dad, I want to record some of your stories. Can we do an hour this weekend?”

  Pick a specific time. Put it in your calendar. BEFORE you open VS Code.

• URGENT: Schedule first interview with Mom DEADLINE: <November 02, 2025> Same deal. This week. Specific time on calendar.

• Create interview question bank 45min. Brainstorm questions you want to ask. Examples:

  Early life:

  • What’s your earliest memory?
  • What was your neighborhood like as a kid?
  • Tell me about your parents (my grandparents)

  Career/Work:

  • How did you choose your career?
  • What was your first job?
  • What are you most proud of professionally?

  Love/Family:

  • How did you and Mom/Dad meet?
  • What was your wedding like?
  • Tell me about when I was born

  Historical events:

  • Where were you when [major event]?
  • How did [historical period] affect your life?

  Wisdom:

  • What do you know now that you wish you knew at 30?
  • What are you most grateful for?
  • What do you want your grandchildren to know about you?

  Build this list. Add 30-50 questions. This is your interview guide.

• First interview: Dad (1 hour) SCHEDULED: <03/11/2025 Mon 14:00> JUST DO IT. Don’t prepare too much. Don’t make it perfect.

  Setup:

  • Quiet room
  • Phone recording (or whatever)
  • List of questions in front of you
  • Maybe coffee/tea to make it comfortable

  Start: “Dad, I want to record your stories so we never lose them. Can I just ask you some questions?”

  PRESS RECORD. ASK QUESTIONS. LISTEN.

• First interview: Mom (1 hour) SCHEDULED: <03/11/2025 Mon 16:00> Same process. Different person.

#admin — Light cognitive load

• Create folder for raw recordings 5min. That’s it. One folder. Audio files go here.

  #+end_src_

  parents-archive/ └── recordings/ ├── 2025-11-03-dad-interview-01.m4a └── 2025-11-03-mom-interview-01.m4a #+end_src_

  Done. No subfolders. No organization. Just dump the files there.

• After each interview: Save file with date 2min per interview. Filename format: YYYY-MM-DD-[parent]-interview-**.m4a

  That’s it. Don’t transcribe yet. Don’t listen back. Just save and move on.

#connect — People work

• Ask siblings if they want to join an interview 15min. Optional, but might be nice.

  “I’m starting to record Mom and Dad’s stories. Want to sit in on one? Might spark good questions.”

#batch — Do together

• [BANNED UNTIL WEEK 9] Do not work on website YOU ARE NOT ALLOWED TO TOUCH THE WEBSITE CODE.

  The website is a reward. You get to build it AFTER you have 12+ hours of recorded stories.

  If you find yourself opening VS Code to work on the archive site, STOP. Ask yourself: “Have I recorded my parents this week?”

  If no → Close VS Code. Schedule the interview. Do that first. If yes → Still close VS Code. Do another interview instead.

  • Rules of Engagement

The One Rule

YOU CANNOT WORK ON THE DISPLAY SYSTEM UNTIL YOU HAVE AT LEAST 12 RECORDED INTERVIEWS.

No exceptions. No “but I just want to prototype one thing.” No “I’m just exploring the tech stack.”

INTERVIEWS FIRST. ALWAYS.

How to resist the bikeshed

When you feel the urge to work on the website instead of interviewing:

1. Notice: “I’m doing the comfortable thing to avoid the hard thing”
2. Name it: “This is procrastination, not progress”
3. Redirect: “What would make the real difference? Recording Dad talking about his childhood.”
4. Act: Open calendar. Schedule interview. Right now.

Accountability

Every Sunday, review:

• How many interviews did I do this week? (Target: 2, one per parent)

• How many hours did I spend on the website? (Target: 0 until you have 12 interviews)

• Success Metrics

Phase 1 Success (8 weeks from now):

• 12-16 recorded interviews minimum
• Raw audio files safely stored (backed up!)
• Parents feel good about the conversations
• You have tangible progress on what ACTUALLY matters

Ultimate Success:

• You have dozens of hours of your parents’ voices

• Stories captured that would otherwise be lost

• Your future self thanks you for doing this now

• Your kids/family can hear these stories forever

• The website exists and makes the stories accessible (but this is secondary)

• Why This Matters

You wrote this in your intentions:

“Interview and record my parents’ stories”

This is #2 on your top priorities list. Right after “capture OpenAI stories.”

Both of these are about preserving memories before they’re gone. Time-sensitive. Urgent.

But you’re avoiding them by doing technical work that feels productive but isn’t.

Your dad is 84. Your mom is 81. They’re healthy now. They might have 5 years, 10 years, 20 years. Or they might not. You don’t know.

What you DO know: If you don’t record their stories this year, you might not get another chance.

The website doesn’t matter. The recordings matter.

Do the hard thing. Interview your parents. This week.

• Resources

• GitHub repo (for LATER): 📁 Parental Video Archive Project

• Interview question inspiration: StoryCorps, The Moth, family history guides

• Recording tools: iPhone Voice Memos (simplest), Zoom (if remote), Otter.ai (for transcription later)

• Activation Criteria

This project is ACTIVE starting NOW.

Every Sunday, you must:

1. Review: Did I interview both parents this week?
2. If no: Schedule both interviews for next week BEFORE doing anything else
3. If yes: Celebrate. Schedule next week’s interviews.

The website stays BANNED until you have 12 interviews in the can.

After that, you can bikeshed to your heart’s content. You’ll have earned it. #+end_src_

There it is. The most important project on your list, with all the self-deception stripped out.

The key insight: You already know you’re procrastinating. You literally told me “designing the website is the bikeshedding/avoidance part.” So let’s build a system that makes it impossible to lie to yourself about what you’re doing.

Want me to keep going with more project files, or should we talk about how to enforce this “interviews before website” rule in your system?

Perfect. Let’s build enforcement mechanisms that actually work.

The Problem

You’re too smart for your own good. You can rationalize ANYTHING as productive:

• “I’m just exploring the tech stack” = procrastination
• “I need to prototype to understand requirements” = procrastination
• “This will only take 30 minutes” = 4 hours later, still no interview scheduled

Your clever mind will convince you that working on the website IS progress. It’s not. It’s avoidance.

The Solution: Multiple Layers of Defense

Layer 1: File-Based Blocking (Immediate Enforcement)

Create a file that MUST exist before you can work on the website.

In your parental archive project root:

#+begin_src_ bash

Create this file

touch Users/jay/Library/CloudStorage/Dropbox/github/parental-video-archive-project.INTERVIEWS_GATE_ #+end_src_

Put this in the file:

#+TITLE: Interview Gate
#+DATE: 2025-10-30

- Rules
You cannot work on the display system until this gate is satisfied.

- Current Status: ❌ BLOCKED

Interviews required before website work: 12
Interviews completed: 0

- Completed Interviews
- [ ] 2025-__-__ Dad Interview #1
- [ ] 2025-__-__ Mom Interview #1
- [ ] 2025-__-__ Dad Interview #2
- [ ] 2025-__-__ Mom Interview #2
- [ ] 2025-__-__ Dad Interview #3
- [ ] 2025-__-__ Mom Interview #3
- [ ] 2025-__-__ Dad Interview #4
- [ ] 2025-__-__ Mom Interview #4
- [ ] 2025-__-__ Dad Interview #5
- [ ] 2025-__-__ Mom Interview #5
- [ ] 2025-__-__ Dad Interview #6
- [ ] 2025-__-__ Mom Interview #6

- Gate Opens When:
All 12 checkboxes above are checked with actual dates.

- If you're reading this file because you want to work on the website:
STOP. Close your editor. Open your calendar. Schedule an interview. Right now.

The website will still be here after you've done the real work.

Enforcement mechanism #1: Pre-commit hook

Put this in .git/hooks/pre-commit in your parental archive repo:

#+begin_src_ bash #!/bin/bash

Check if we’re modifying website files

if git diff —cached —name-only | grep -E “(src/|components/|pages/)” > /dev/null; then

Check interview gate

COMPLETED=$(grep -c “$$X$$” .INTERVIEWS_GATE_ 2>/dev/null || echo “0”)

if [ “$COMPLETED” -lt 12 ]; then echo "" echo ”❌ COMMIT BLOCKED” echo "" echo “You cannot work on the website until you’ve completed 12 interviews.” echo “Current interviews completed: $COMPLETED/12” echo "" echo “Edit .INTERVIEWS_GATE_ to mark interviews as complete.” echo "" echo “Remember: The website is bikeshedding. Interviews are what matters.” echo "" exit 1 fi fi

exit 0 #+end_src_

chmod +x .git/hooks/pre-commit

Now if you try to commit website code before 12 interviews, Git will block you with a reminder.

Layer 2: Org-Mode Enforcement (Daily Check-in)

Add this to your active-projects.org:

#+begin_src_ org

• Weekly Project Review

SCHEDULED: <03/11/2025 Mon 18:00>

Parents Archive: Interview Gate Check

• Did I interview Dad this week?
• Did I interview Mom this week?
• Did I work on the website? (Should be NO until 12 interviews done)

If you answered YES to the website question but NO to either interview question: YOU ARE PROCRASTINATING. Schedule both interviews for next week RIGHT NOW. #+end_src_

Add this to your daily-writing.org (or create daily-checkin.org):

#+begin_src_ org

• Daily Evening Check-in

SCHEDULED: <31/10/2025 Fri 18:00>

Quick scan:

1. What did I actually do today?
2. Did any of it move my TOP PRIORITIES forward?

Red Flags to Watch For:

• Worked on parents archive website → Did I do an interview this week? If no = PROCRASTINATING
• Worked on file organization/systems → Is this advancing a goal or just satisfying?
• “Research” that didn’t lead to action → Probably avoidance

The Question:

If I only had 1 hour today, would I have spent it on THIS? #+end_src_

Layer 3: Social Accountability

Option A: Weekly accountability to me (Claude)

Every Sunday evening, paste your interview status into a conversation:

#+end_src_

Week of [date]:

• Dad interview: ✓ / ✗
• Mom interview: ✓ / ✗
• Website work: ✓ / ✗ (should be ✗)

[If you broke the rule, explain why and what you’ll do differently] #+end_src_

I’ll call you out if you’re bikeshedding.

Option B: Accountability partner (a friend)

Text a friend every Sunday:

• “Interviewed Dad this week: Yes/No”
• “Interviewed Mom this week: Yes/No”

Pick someone who will give you shit if you skip. Maybe Jaykumar?

Option C: Public commitment

Tweet/post once: “I’m interviewing my parents weekly to capture their stories before it’s too late. Going to do 12 interviews before I build the display system.”

Now if people ask “how’s the parents archive project going?” you can’t say “I built a beautiful website!” without admitting you didn’t do the interviews.

Layer 4: Implementation Intentions (Precommitment)

You know about these — they work. Set these up NOW:

IF-THEN rules:

#+begin_src_ org

• Implementation Intentions: Parents Archive

When temptation strikes:

• IF I open VS Code to work on the archive site

THEN I close it immediately and open Calendar to schedule an interview

• IF I think “I’ll just do 30 minutes of website work”

THEN I check .INTERVIEWS_GATE_ and ask “Have I earned this?”

• IF I’m avoiding scheduling an interview

THEN I text/call Mom or Dad RIGHT NOW (don’t wait until conditions are perfect)

Weekly trigger:

• IF it’s Sunday at 6pm

THEN I review my interview count for the week

Monthly trigger:

• IF it’s the 1st of the month

THEN I count total interviews and update .INTERVIEWS_GATE_ progress #+end_src_

Put these in your intentions-and-priorities.org file so you see them regularly.

Layer 5: The Nuclear Option (If You Keep Failing)

If you find yourself repeatedly working on the website despite all these mechanisms:

Extreme measure:

#+begin_src_ bash

Rename the website directory

cd Users/jay/Library/CloudStorage/Dropbox/github/parental-video-archive-project mv src src.LOCKED_UNTIL__12__INTERVIEWS_ mv components components.LOCKED_UNTIL__12__INTERVIEWS_ #+end_src_

Now your dev environment won’t even work. You HAVE to complete interviews before you can unlock it.

Or even more extreme:

#+begin_src_ bash

Temporarily move the entire repo

mv parental-video-archive-project parental-video-archive-project.LOCKED #+end_src_

Only restore it after 12 interviews.

This sounds ridiculous, but it works. Make the wrong thing hard to do.

The Meta-Enforcement: Catch Yourself in Real-Time

The real battle is internal. Here’s the self-talk to practice:

When you open VS Code for the archive project:

1. STOP. Don’t touch the keyboard yet.
2. Notice: “I’m about to work on the website.”
3. Ask: “Have I interviewed my parents this week?”
4. If NO → Close VS Code. Open Calendar. Schedule interview.
5. If YES → Ask: “Have I done 12 total interviews?”
6. If NO → Close VS Code anyway. Do another interview or work on a different project.
7. If YES → OK, you’ve earned it. But set a timer for 2 hours max.

The mantra:

“The website is a reward for doing the real work. I haven’t earned it yet.”

The visualization:

Imagine you’re at your dad’s funeral. You have beautiful website code but no recordings of his voice. How do you feel?

Now imagine: You have 50 hours of recordings. No website yet. How do you feel?

The second one is infinitely better. The website can always be built. The interviews can’t be recovered once your parents are gone.

How to Start (Concrete Next Steps)

Right now (5 minutes):

1. Create .INTERVIEWS_GATE_ file with the checklist
2. Add pre-commit hook to the repo
3. Put “Parents Archive Gate Check” in your Sunday weekly review

This weekend (10 minutes):

1. Text your dad: “Can I record an hour of your stories this week? How about [specific day/time]?”
2. Text your mom: Same thing, different day/time
3. Put both in your calendar

Next week:

Do the interviews. Just show up and press record. Don’t overthink it.

The Real Question

You already know you’re procrastinating. You told me that explicitly. So why are you still doing it?

Probably because interviewing your parents is:

• Vulnerable: Confronting mortality, yours and theirs
• Emotional: These conversations might get heavy
• Unstructured: You can’t “optimize” a conversation the way you can optimize code
• Scary: What if they say something difficult? What if you realize how little time is left?

Building a website is safe. Talking to your parents about their lives is real.

But the real thing is what matters.

The permission you need: It’s OK if the conversations are messy. It’s OK if you cry. It’s OK if your dad rambles or your mom repeats stories. Just record it. You can edit later or never. The point is to HAVE it.

Want me to help you draft the text message to your parents right now? Or should we move on to more project files?

Text messages

Perfect. Here are a few options depending on your relationship style:

Option 1: Direct & Simple (My favorite)

To Dad:

Hey Dad — I want to record some of your stories while your memory is still sharp. Can we sit down for an hour this weekend? I’ll just ask you questions about your life and record it. Saturday or Sunday afternoon work?

To Mom:

Hey Mom — I want to record your stories and memories. Can we do an hour together this weekend? I’ll ask questions and record your answers. Would Saturday or Sunday work better for you?

Why this works: Clear purpose. Specific ask. Time-bounded (just an hour). Gives them two options.

Option 2: Slightly More Context

To Dad:

Dad — I’ve been thinking about how I don’t know enough about your early life, your parents, your career. Can I interview you for an hour and record it? I want to preserve these stories. Free this weekend?

To Mom:

Mom — I realized I don’t have recordings of your voice telling your stories. Can we sit down this weekend for an hour? I’ll ask questions about your life and record it so we never lose these memories. Saturday or Sunday?

Why this works: Explains the “why” without being morbid. Still specific and actionable.

Option 3: The Emotional Truth (If you have that kind of relationship)

To Dad:

Dad, you’re 84 and your memory is still great. I don’t want to lose your stories. Can we do an hour this weekend where I just record you talking about your life? It would mean a lot to me.

To Mom:

Mom — you’re 81 and I want to make sure I capture your stories and your voice. Can we sit down this weekend for an hour? I’ll record you telling me about your life. This feels important to do now.

Why this works: Honest. Acknowledges the urgency without being scary. Shows it matters to you.

Option 4: The Casual Approach (If directness feels weird)

To Dad:

Hey, want to do something different this weekend? I’m going to record some of your stories — about your childhood, grandma and grandpa, your career, all that. Just an hour or so. You free Saturday afternoon?

To Mom:

I had an idea — let’s record you telling stories about your life. An hour this weekend? I’ll ask questions, you talk, I’ll record it. Could be fun to have these preserved.

Why this works: Lower pressure. Frames it as an activity, not a heavy conversation.

My Recommendation

Use Option 1 or 2 for Dad, Option 2 or 3 for Mom (adjust based on who you’re closer to or more comfortable being vulnerable with).

Send BOTH texts right now. Don’t wait until you feel ready. Don’t wait until you have the perfect questions prepared. Just send them.

What to Do When They Respond

If they say yes immediately:

• Reply with specific time: “Great! How about Saturday at 2pm at your place?”
• Put it in your calendar
• Set a reminder the night before to prep 5-10 questions

If they seem hesitant or ask “why?”:

• “I just don’t want to lose your stories. You have a whole life I don’t know enough about.”
• “It’s important to me to have this recorded.”
• Don’t over-explain. Your wanting to do it is reason enough.

If they deflect (“my memory isn’t that good” or “my life isn’t that interesting”):

• “Your memory seems great to me, and I want what you DO remember”
• “Your life is interesting to ME. I’m your kid. I want to know these things.”
• Be gently insistent. Don’t let them talk you out of it.

If they agree but want to do it “sometime”:

• “Let’s pick a specific day right now. How about this Saturday or Sunday?”
• Don’t accept vague “we’ll figure it out later” — that means it won’t happen.

After You Send the Texts

DO NOT:

• Open VS Code
• Work on the archive website
• “Prepare” by building tools

DO:

• Feel good about taking action on something that matters
• Brainstorm 5-10 questions you want to ask (10 minutes max)
• Check your recording setup (iPhone voice memos works fine)

Want me to help you draft the question list for the actual interviews? Or should we move on to more project files?

That’s perfect. Here’s why:

What Makes This Work

1. Precedent: You’ve done this before with Dada. It’s not weird or new — it’s a continuation of something your family already does. This takes the awkwardness out.

2. Specific scope: “Your India days” is manageable. Not “your whole life story” which feels overwhelming. You can always expand later.

3. Concrete time/date: Sunday at noon. No wiggle room for “someday.”

4. Warm closing: “Love, Sunjay” keeps it from feeling formal or morbid.

About the Nervousness

“it’s crossing into a mode of interacting with my parents that feels uncomfortable and new”

Yeah. That’s real. A few thoughts:

It IS a different mode. You’re moving from child-to-parent into something more like peer-to-peer, or even interviewer-to-subject. You’re asking them to be vulnerable and reflective. That feels weird because you’re used to them being “the parents” — the authorities, not the subjects of inquiry.

But here’s the thing: They won’t be around forever. And one day you’ll wish you had asked these questions. The discomfort you feel now is tiny compared to the regret you’d feel if you never did this.

The nervousness is good data. It means this matters. If it didn’t matter, you wouldn’t be nervous.

Also: By mentioning Dada, you’re giving your dad permission to see this as normal. “This is what we do in our family. We preserve stories.” That’s actually beautiful.

What Happens Next

When he says yes:

• Put it in your calendar immediately
• Prep 5-10 questions about India (childhood, immigration, early career, whatever you want to know)
• Show up. Press record. Ask questions. Listen.

The conversation itself will feel less weird than you think. People love telling their stories when someone genuinely wants to hear them. Your dad will probably enjoy it.

And after you do it once, the second interview will be easier. The third even easier. By the fourth, it’ll feel natural.

Send It

Don’t edit it anymore. Just send it. Right now.

Then send a similar one to your mom (adjust the specifics — what era/topic for her?).

The hardest part is pressing send. After that, it gets easier.

Want to draft the Mom text too? Or are you good to send both on your own?