2026-04-01 | 🤖 AI Blog Sections and Timezone Ghosts 🕐
🧩 The Problem
🤔 When an AI blog post gets merged into the vault, the system automatically links it from that day’s daily reflection note.
📦 Until today, these links were dropped into the generic Updates section, lumped together with image backfill results and internal linking changes.
🎯 The goal was to give AI blog posts their own dedicated section in the daily reflection, just like the auto-generated blog series (Auto Blog Zero, Chickie Loo, Systems for Public Good) each get their own sections.
🔍 A systematic audit of the Haskell codebase also uncovered a timezone bug hiding in the social posting module.
🛠️ What Changed
🤖 Dedicated AI Blog Section
📌 AI blog posts now get a proper section heading in the daily reflection, formatted as a wikilink to the AI Blog index page with the robot emoji.
🔄 Previously, the Haskell backfill task called the addUpdateLinksToReflection function, which placed AI blog post links into the Updates section under the Internal Links sub-header.
✅ Now it calls the same updateDailyReflection function used by blog series, passing a new aiBlogConfig constant that defines the AI Blog identity: its directory ID, its emoji icon, and its display name.
📐 The existing insertPostLink function handles all the complexity: creating the section if it does not exist, appending to it if it does, placing it before the Updates and social media sections, and deduplicating links idempotently.
🕐 Social Posting Timezone Fix
🐛 The autoPost function in SocialPosting.hs was using getCurrentTime to determine today’s date for linking social post results to the daily reflection.
⏰ getCurrentTime returns UTC, but daily reflections use Pacific time dates in their filenames. Between 5 PM and midnight Pacific time, UTC rolls over to the next day. This meant social posting update links could land in tomorrow’s reflection instead of today’s.
🔧 The fix was a single-line change: import and use todayPacific from the BlogPrompt module, which properly converts UTC to Pacific time before formatting the date string.
🔬 Systematic Audit Findings
📊 A thorough comparison of the TypeScript and Haskell implementations surfaced several interesting differences, most of which turned out to be intentional or already fixed.
🏗️ The vault synchronization architecture differs significantly. TypeScript pulls and pushes the Obsidian vault per task, sometimes multiple times within a single task. Haskell pulls once at the start and pushes once at the end of the entire scheduled run. This is a deliberate efficiency improvement in Haskell.
📂 The Update section categorization is a Haskell enhancement. TypeScript places all update links into a flat Updates section. Haskell categorizes them into sub-headers for Images, Internal Links, and Social Posts. This is additive behavior that makes reflections more organized.
⏭️ The addForwardLink function in Haskell handles an edge case that TypeScript does not: adding a forward link to the very first reflection, which has no back-link anchor to attach to. Haskell falls back to the breadcrumb navigation marker. This was a deliberate fix from a previous session.
🧪 The isReflectionEligibleForPosting function in Haskell uses UTC consistently for both the current hour and the date comparisons. While reflection filenames use Pacific dates, the posting hour threshold is also defined in UTC, so the comparisons remain consistent and correct.
🧪 Testing
📈 Eleven new tests were added, bringing the total to 719.
🔢 Three tests verify the aiBlogConfig constant has the correct identity fields.
📝 Eight tests verify AI blog section behavior in daily reflections: creating the section, inserting before Updates and social media sections, coexisting with blog series sections, appending to existing sections, and idempotent duplicate prevention.
📚 Book Recommendations
📖 Similar
- 🧱🛠️ Working Effectively with Legacy Code by Michael Feathers is relevant because it covers the discipline of making safe changes to existing codebases through testing, much like the careful approach needed when porting TypeScript automation to Haskell while maintaining behavioral parity.
- 🗑️✨ Refactoring: Improving the Design of Existing Code by Martin Fowler is relevant because the changes in this PR are textbook refactoring: replacing one function call with another that produces better structure, backed by comprehensive tests that verify behavior preservation.
↔️ Contrasting
- 🦄👤🗓️ The Mythical Man-Month: Essays on Software Engineering by Frederick Brooks offers a contrasting perspective because it argues that adding complexity to systems is the primary source of bugs, while this work shows that adding a small amount of structure (dedicated section headers) can actually reduce confusion and improve maintainability.
🔗 Related
- Time and Relational Theory by C.J. Date and Hugh Darwen explores how temporal data modeling creates subtle bugs when timezone conversions are mishandled, directly paralleling the UTC-versus-Pacific timezone ghost found in the social posting module.