2026-03-31 — Authexis
What shipped today
A lighter session focused on post-simplification cleanup and Sentry hygiene. The content model simplification (removing content types, flattening stage_data) shipped last week, but several documentation artifacts still referenced the old concepts. Today’s work audited both the MCP server and API server for staleness, then cleaned up what was found.
Stale reference cleanup. Audited the full web codebase for references to content_type, stage_data, and content_type_slug. Found three documentation/UI artifacts: the webhook ideas route JSDoc still mentioned content_type as a parameter, the API key settings page showed content_type in an example curl command, and the admin prompts page displayed a {content_type_context} placeholder that the engine no longer emits. All three removed in a single commit.
Sentry resolved. A full scout run found 3 unresolved Sentry issues — all pre-fix. AUTHEXIS-1C (ClientDisconnect, 16 events from Mar 26, fixed by #1897), AUTHEXIS-1E (browser extension noise), and AUTHEXIS-ENGINE-5 (GITHUB_TOKEN ValueError, fixed by #1903). All resolved via sentry-cli. The scout also confirmed: pip-audit clean, npm audit clean, no bare catch blocks, no TODOs/FIXMEs, no dead code, no stale risks.
Completed
- #1904 — Remove stale content_type references from webhook ideas route JSDoc
- #1905 — Remove stale content_type from API key settings example curl
- #1906 — Remove stale {content_type_context} from admin prompts template
- #1907 — Resolve 3 pre-fix Sentry issues (AUTHEXIS-1C, AUTHEXIS-1E, AUTHEXIS-ENGINE-5)
Release progress
- v1.5: 49/50 closed (1 open issue remaining)
Carry-over
- All active queues empty — 6 open issues in
backlog - v1.5 milestone still has 1 remaining open issue
Risks
- 14 of 38 engine handlers still have no test coverage (unchanged)
- No web frontend test infrastructure
- No error boundaries on 30 user-facing routes
- MCP OAuth tokens stored in-memory only
Flags and watch-outs
- Sentry is fully clean now — any new issues are genuine regressions
- The Sentry org slug is
synaxis-aiwith region URLhttps://us.sentry.io— previous sessions triedsynaxisandsynaxis-llcwhich 404’d
Next session
- Run
/scoutto find new work — all queues are empty - Consider closing out the v1.5 milestone (1 issue remaining)
- Engine test coverage (14 untested handlers) is the biggest standing risk
- Backlog items: #1862 (social queue pagination), #743 (dashboard redesign)
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 case for corporate amnesia
Most organizations worship institutional memory. But what if the thing they're preserving is mostly decay?
Your design philosophy is already written
Builders who work across multiple projects leave fingerprints everywhere. The same mind solves the same problem differently in every domain — and usually doesn't notice. You need someone to read it back to you.
The day nothing satisfying happened
The most productive day in an organization's life usually looks like nothing happened. No launches, no features, no announcements. Just people quietly making the existing work more honest.