The week the principles took shape

Concepts cascade

In the week after the founding, nineteen named Concepts went down. The conceptions of Day 1 — systems not willpower, transcript-first, two-door model, energy as a first-class property — became canonical pages with frontmatter, sources, and cross-references. By the end of the week, Concepts 01 through 19 existed in writing, plus Implementation pages 26 through 39 documenting the technical scaffolding that would carry them.

The wiki's working pace was extraordinary in retrospect. Most of these concepts have survived months of pivots. Pricing below the IF threshold (Concept 11), progressive disclosure (Concept 14), no-guilt design (Concept 17) — these are still load-bearing. The conceptual frame this week stayed.

Concepts that don't outlive the week they were filed don't deserve the file. These did.

The guest model

Concept 07 named the architectural posture that everything since has been built on: client-owned Notion workspace, Jamie as guest, MCP via integration tokens. Implementation 26 documented the technical realisation — local MCP servers, per-client tokens, config structure, scaling limits.

The implication mattered more than the mechanism. Jamie would never own the data plane. Each client's workspace would live on the client's own Notion account. Jamie's access would be guest access — granted by the client, revocable by the client, scoped to what the client invited him into. Privacy was a property of the architecture, not a setting.

The architecture has evolved (the Hybrid Member Model now provides a different topology) but the principle — the operator never owns the data plane — became Heuristic 04 a few weeks later.

The architecture that can't fail is the architecture that doesn't own the failure surface.

The Seven Principles

Concepts 01 through 13 were the founding sketches. The Seven Principles emerged from them as the canonical operating set:

• Nothing lives in your head.
• Structure without effort.
• The system speaks first.
• One decision at a time.
• The person owns the system.
• Lived experience is the design spec.
• Tools are replaceable. Principles aren't.

The Protocol lives in CLAUDE.md, not as a separate Concept page — schema-layer, not wiki content. Every design decision gets held against all seven. If a feature violates a principle, it's not the Protocol.

The framing has held. Months later, the heuristics-audit gate (added in May) is the runtime enforcement of "Protocol that doesn't run is Protocol that doesn't work" — a sub-pattern of Principle 7 itself.

Principles you can list aren't a manifesto. Principles you can break against are.

The intake flywheel

Concept 06 — the Intake Flywheel — named the loop the product sits inside. The intake simultaneously records, structures the workspace, and demonstrates the product. One conversation produces three artefacts: a recording for archive, a configured workspace for the client to walk away with, and a demo of how the system works.

The intake was a service mechanic and a marketing mechanic in the same hour. That made the install — and the install conversation — load-bearing in a way most onboarding flows aren't. The Strategy Session retired in May 2026; its onboarding function was absorbed into the install interview. The flywheel survived the rename.

One hour, three artefacts. That's a service that pays its keep at the moment it ships.

What's next

Week 3 brought the wiki itself into focus. Karpathy's LLM Wiki pattern was filed as the architectural reference. Cross-disability evidence arrived. The MVP gates were set. Blog posts began.

Nineteen concepts in. The conceptual library would keep growing — and pruning.