Work log: Polymathic — March 5, 2026
What shipped today
Email signature overhaul (GH-48)
Fixed the email signature “Latest:” line picking up a cross-project synthesis instead of a real blog post. The root cause was that the sig template filtered by content_type exclusions but syntheses had no content_type at all, so they slipped through. Two fixes: the template now filters by Section "posts" first (defense in depth), and all 13 synthesis files got content_type: synthesis added to their frontmatter. Two older syntheses (2026-02-28 and 2026-03-01) were missing frontmatter entirely — those got proper YAML blocks added.
Also built the new Authexis email signature variant. It mirrors the Synaxis sig but adds a “Creator of Authexis” line linking to authexis.app with UTM tracking, and uses [email protected] as the contact email. The template’s extra_line parameter now supports HTML via safeHTML to enable the linked text.
Updated the Synaxis tagline across both sigs from “Strategy and implementation for AI, automation, and data” to “AI for execution. Humans for judgment.”
Filed paulos#181 so the /sum-up skill includes content_type: synthesis in generated frontmatter going forward.
Social media cadence recommendation
Researched optimal LinkedIn posting frequency and reviewed the Authexis social slot configuration. Recommended schedule: LinkedIn 3x/week (Tuesday 11:00, Wednesday 8:00, Friday 10:00), Bluesky 3x/week (Monday 8:30, Wednesday 14:30, Saturday 15:30), Mastodon 3x/week (Monday 13:00, Thursday 13:00, Saturday 16:00). No platform doubles on any day. User to apply in Authexis manually.
Completed
- #48 — Rebuild sigs after template update
Release progress
- March 2026: 7/7 closed — all issues complete
- April 2026: 0/1 closed (GH-8: syndication, parked)
Carry-over
- Stale worktrees (
agent-a467dc04,agent-ac8f8dca) still in.claude/worktrees/— cleanup deferred again - Social slot changes need to be applied in Authexis (user will do manually)
- paulos#181 (synthesis content_type in
/sum-up) — open in paulos repo
Risks
- None
Flags and watch-outs
- Apple Podcasts artwork — still haven’t confirmed cream version propagated (flagged since March 3)
- Edition 12 newsletter stats — still unchecked in Brevo
- CF Pages build time — still unverified whether
resources/_gen/commit helped
Next session
- Verify Apple Podcasts artwork (cream vs black) — this has been carrying for 3 days
- Check edition 12 newsletter stats in Brevo
- Check CF Pages build time on recent deploys
- Clean up stale worktrees
- Consider closing March 2026 milestone (7/7 complete)
Why customer tools are organized wrong
This article reveals a fundamental flaw in how customer support tools are designed—organizing by interaction type instead of by customer—and explains why this fragmentation wastes time and obscures the full picture you need to help users effectively.
Infrastructure shapes thought
The tools you build determine what kinds of thinking become possible. On infrastructure, friction, and building deliberately for thought rather than just throughput.
Server-side dashboard architecture: Why moving data fetching off the browser changes everything
How choosing server-side rendering solved security, CORS, and credential management problems I didn't know I had.
The work of being available now
A book on AI, judgment, and staying human at work.
The practice of work in progress
Practical essays on how work actually gets done.
The smartest code you'll ever delete
The most dangerous kind of waste isn't the thing that doesn't work. It's the thing that works beautifully and shouldn't exist.
The first real user breaks everything
Your product works until someone actually uses it. The gap between 'works in dev' and 'works for a person' is where most systems fail — and most organizations avoid looking.
The loop nobody bothers to close
Most systems observe. Almost none learn. The difference is a feedback loop — and the boring cleanup work that makes it possible.