Work log: Textorium — March 18, 2026
What shipped today
No code shipped. Brief context-recovery session. Board is empty — zero open issues. v1.5 milestone is complete (18/18) but not yet formally closed. v1.0.4 was submitted to App Review on March 16 and should be in review or approved by now.
Completed
(None)
Carry-over
- v1.5 milestone — needs formal closure via
/milestone close v1.5 - App Store review — check status of v1.0.4
- Marketing site visual QA — dark mode, 404, OG tags, blog section still unverified in production
Risks
- None. Project is stable, no active development.
Flags and watch-outs
- The old root-level
Textorium.xcodeproj(pre-monorepo) is still in the repo. Future version bumps usingreplace_allwill hit both project files — always targetmacos/Textorium.xcodeprojspecifically.
Next session
- Check v1.0.4 App Store review status.
/milestone close v1.5.- Visual QA of textorium.app in production.
/scoutto fill the backlog — the board has been empty since March 16.
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 day we shipped two products and the agents got bored
112 issues across 12 projects. Two new products went from nothing to code-complete MVP in single sessions. And the most interesting signal wasn't the speed — it was the scout that came back empty-handed.
The org chart your agents need
The AI community is reinventing organizational design from scratch — badly. Agencies figured this out decades ago. Competencies, not clients. Briefs, not prompts. Lateral communication, not hub-and-spoke. The answers are already there.
AI agents need org charts, not pipelines
Every agent framework organizes around tasks. The agencies that actually work organize around competencies. The AI community is about to rediscover this the hard way.