Thoughts
[Notion Sync] Tattoo Project: "Noah Daugherty Falcon Sleeve" — Client: Noah Daugherty. Status: Ongoing. Definition: Bird of prey, similar to crane sleeve I did. Next Task Date: 2026-04-22. Created: 2026-01-05. Pillar: TATTOO. Has intake submission, resources, and linked notes. Source: Notion Projects database.
Claude.ai memory export: davetedder.com Post-Launch Follow-Up items Pending: intake routing to Notion/Airtable, conditional logic for project size flagging, quiet non-marketing autoresponder, single MailerLite onboarding email, site-wide email standardization.
Claude.ai memory export: Active Project — Claude Code cross-device workflow Configured between laptop and always-on Mac mini, using iCloud-synced project folders, Cowork/dispatch, and HANDOFF.md files for session continuity.
Open Brain Session 9 retro: Massive build session. Went from 4 MCP tools to 16 in one session. Built all three extensions (Client Context, Content Pipeline, Business Operations) plus cross-extension intelligence (full_context tool + digest v2). Built and deployed Next.js dashboard to Railway (6 pages, dark theme, password auth). Key learnings: (1) Next.js Supabase client must use lazy init, not module-scope, or Railway builds fail without env vars. (2) Railway CLI is more reliable than Railway MCP for project creation. (3) sed find-replace misses multiline method chains, always check end-of-line patterns separately. (4) Supabase free tier Realtime quota spike was from Dashboard Table Editor tabs, not application code. (5) brain-digest extension context is wrapped in try/catch so empty extension tables never block delivery. Session touched 4 migrations, 12 new tools, 1 full web app, 1 digest upgrade.
Session: Compared Nate Jones' project structure and agent management framework (from his video, Substack article, and PromptKit) against my existing Claude Code rules system. Key findings: My multi-session handoff system, tracker rotation/archiving, and modular rules structure are more mature than what Nate describes. His "scaffold documents" concept is essentially what I already built with PROJECT-TRACKER.md and the handoff prompts. Biggest gap identified: My tracker is a log, not a snapshot system. It records what happened but doesn't create recoverable states. Nate's key insight is that the tracker and git commits serve different purposes. The tracker is project memory; git commits are the undo button. You need both. Changes implemented (2026-03-16): 1. Added git save point protocol to ~/.claude/rules/tracking-and-verification.md. After each task passes verification, agents must now create a git commit before starting the next task. Includes a non-git escape hatch for WordPress/Notion-only work. 2. Added Prohibited Actions template to the PROJECT-TRACKER.md template. Every new project now gets prompted to define guardrails at setup (production data, WordPress, infrastructure). "Never commit secrets or API keys" is always included. 3. Added blast radius risk flagging to todo items (low/medium/high). Medium and high risk tasks require confirmation before executing. 4. Created new ~/.claude/rules/security-baseline.md (~29 lines) covering Supabase (RLS, service_role key, input validation, no PII logging) and Railway (env vars, health checks, private networking, pinned images) guardrails. All changes are in ~/.claude/rules/ and will be loaded automatically in every future Claude Code session. Existing projects will pick up the new behaviors naturally since agents read the rules files at session start.
Add task to project Atlanta invitational: research different insurance options
New project, Atlanta Invitational. Work pillar. Add task research possible hotels. Add task, research pipe and drape
The relationship between Dave's Second Brain and Open Brain: Second Brain is the structured project manager (Slack to Notion, handles tasks/projects/clients/payments). Open Brain is the semantic memory layer underneath it (Supabase pgvector, fuzzy long-term memory). Dave built Open Brain because he was self-censoring his Slack captures, not wanting to clutter Notion with half-baked ideas and fleeting observations. Open Brain catches everything Second Brain doesn't, and any AI agent can search and write to it across platforms and sessions.
As of March 2026, Dave Tedder uses Notion Business for project management, CRM, and knowledge base. His workspace follows a PARA-influenced structure with Eisenhower matrix prioritization. Key page: TATTOO HQ. Known issue: the workspace contains several generations of the same database schema from iterative builds, so always confirm which database set is active before making changes.
Dave Tedder uses an ROI-first decision framework for every project and tool decision: (1) Will it make money? (2) Will it save time? (3) What's the implementation cost? (4) What's the payoff timeline? He expects concrete estimates, not vague language. His priority triage: "Do now" if it makes money this week or saves 1+ hours immediately, "Schedule" if clear ROI but needs setup, "Delegate/automate" if repetitive or low-skill, "Kill it" if no clear ROI or maintenance exceeds benefit.