2026-04-02 — Methodology completion, engine client routing, Authexis engagement begins
What shipped today
The methodology is now complete. Three gaps identified by yesterday’s scout — blog posts deliverable, questionnaire guide, and repositioning playbook — were filled with full guides and templates. The first T3 atom (website deploy) shipped, meaning Synaxis can now produce execution-layer deliverables, not just documents. The repo went from “mostly methodology” to “complete methodology” in one session: 14 deliverable types with guides, 3 playbooks, and the full skill/persona/reviewer infrastructure.
The engine got smarter about clients. The inbound email webhook now auto-routes emails to the right client by matching sender domains against the Clients database in Notion. When someone from @eclectis.io emails [email protected], the comms log entry automatically links to the Eclectis client page. The Notion workspace was restructured too — Decision Log and Activity Log both got Client, Deliverable, and Engagement relation columns so all operational databases are cross-client.
The Authexis test engagement launched. Two deliverables shipped for Authexis (Synaxis’s first non-Eclectis client): the onboarding questionnaire (populated from authexis PRODUCT.md) and a full competitive analysis with real web research — Jasper pricing, G2 reviews, freelancer rate surveys, Buffer/Hootsuite comparisons. Key finding: Jasper is vacating the solo-consultant space by moving upmarket to enterprise, leaving a gap Authexis can fill at $99/mo. These were later removed from git (client work belongs in Notion, not the repo) but the methodology execution was validated end-to-end.
Repo hygiene cleared 721 lines of dead weight. Stale session summary, orphaned research drafts, an implemented-and-forgotten reviewer spec, and an outdated architecture SVG were removed. Two client-relevant files (blog ideas, product opportunity) were moved to clients/eclectis/ where they belong. Dead Dockerfile and railway.toml that referenced the deleted server.py were cleaned up.
Completed
- #39 Stale docs after engine pivot
- #40 Dead deployment infra (Dockerfile + railway.toml)
- #41 Missing methodology: blog posts, questionnaire guide, repositioning playbook
- #43 Repo hygiene: session summary, orphaned context files
- #44 Build T3 atoms (decomposed into #47, #48, #49)
- #48 T3 atom: website deploy
- #46 End-to-end engagement with Authexis (decomposed into #50-#53)
- #50 Authexis onboarding questionnaire
- #51 Authexis competitive analysis
- #45 Curated briefing playbook (→ needs-clarification, business model undefined)
- #38 fix CI (wrong repo — scholexis issue filed against synaxis-ai)
- #54 VolumeAlert.triggered (Vercel webhook noise)
Carry-over
- #52 Authexis positioning brief — depends on questionnaire + competitive analysis (both done). Ready for next agency-loop tick.
- #53 Authexis voice doc + social series + landing page — depends on #52 positioning brief.
- #42 Engine plumbing blockers — needs-clarification. Half is already shipped (inbound email, Notion logging). Remaining: outbound email, Notion reads, Slack posting. Needs architectural decision on whether Notion reads replace repo-based client context.
- #37 Subtasks per deliverable — needs-clarification. One-line body, no context.
- #26 Slack apps for personas — blocked on manual Slack app creation.
- #45 Curated briefing playbook — needs business model decisions (pricing, delivery format, white-label scope).
Risks
- Client deliverables in git vs Notion. Paul decided mid-session that client work belongs in Notion, not the repo. The Authexis questionnaire and competitive analysis were committed, pushed, then removed in a follow-up commit. The methodology and guides stay in git; deliverable output goes to Notion. This split needs to be documented in DECISIONS.md.
- Engine deployment stale. The Railway-deployed engine still runs the pre-client-routing version of server.py. The commit with
lookup_client_by_domain()was pushed to GitHub but Railway may not have redeployed. Need to verify.
Next session
- Authexis positioning brief (#52) — next in the engagement chain. Load strategist skill, use questionnaire + competitive analysis as inputs.
- Verify Railway deployment — confirm the client-routing code is live on
engine.synaxis.ai. - Document the git/Notion split — add to DECISIONS.md: methodology in git, client deliverables in Notion, never mix them.
- Test inbound email again — Paul sent a test email earlier that didn’t show up. Might be a Brevo MX propagation delay or a Railway deployment issue.
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.
Delegation without comprehension is just prayer
The organizations that survive won't be the ones that automated the most. They'll be the ones that figured out what to stop delegating.
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.