The week the architecture ran

First Worker shipped

Implementation 55 — the calendar sweep Cloudflare Worker — shipped end-to-end on 25 April. Worker reads Jamie's Google Calendar, writes to a Notion Calendar Events database, an R-rule (R3) reads the database and writes Coming Up + On the radar to the Home page. First end-to-end automation in production. Daily 00:00 NZST cron plus a manual /sync endpoint for testing.

The architecture had been settled before code: source-mirror pattern (Concept 35), thin Worker as pipe, classification in the consumer R-rule. Implementation 55 was straight execution against a settled spec. Zero architectural debate during the build.

Architecture settled before code makes the build mechanical. That's the goal.

Privacy as absence

Concept 30 — Privacy as Absence — reframed the privacy story. Privacy in the consumer-AI market is operational restraint on data the vendor holds. In the Neuro Agent it is architectural absence: there is no Neuro Support backend, no internal team, no admin console, nothing to leak through because nothing is there to leak.

The three-absence test: no operator backend, no operator team, no operator admin surface. Each absence is structural — a property of the architecture, not a setting. The frame paired with Heuristic 22 (single-operator-as-structural-property) and Heuristic 04 (operator doesn't own the data plane). Three layers, same argument: privacy lives in what isn't there.

The strongest privacy commitment is the one you don't have to write.

Block-track architecture

Concept 32 set the active pricing structure: Neuro Agent at $1,499 one-off install, Neuro Support in 2-month blocks at $1,499 per block, Pro and Max tiers within each block. The architecture would carry the next two weeks before the Concept 43 rewrite collapsed it into a different shape (install + monthly Operational + premium Max + Support Sessions).

Concept 31 named what the blocks were for — co-working. The Agent isn't a chatbot; it's a co-working partner. The client works alongside Claude toward their own ends. Sessions inside a block were the dual-system calibration moments where the human and the AI system both got tuned in the same conversation.

Pricing carries the architecture. When the architecture changes, the pricing changes. Don't pin the architecture to the pricing.

Notion Capture shipped

Implementation 66 — the Notion Capture iOS Shortcut — shipped on 21 April. Three-action Shortcut: dictate, build a JSON body, POST direct to the Notion Updates API. 200 OK confirmed. Action Button bound to capture; voice-to-Notion in under two seconds; nothing to think about at the moment of capture.

This was the operational realisation of Principle 1. Nothing lives in your head: the path from thought to externalised must be short enough that even the worst-day version of the operator can use it. One press of a hardware button. Speak. Done.

Capture friction is the limit on Principle 1. Hardware-button voice capture is where that limit currently sits.

What's next

Week 6 brought the architectural pivot — the post-MCP, Notion-native target architecture (Hybrid Member Model). Clients as paid Members of Jamie's workspace, in private teamspaces. The security posture was set; the support-network shared space was named; the Notion-native deployment validation pass closed.

Architecture in production. Pivot incoming.