create-ailk 0.1.0

package/templates/content/en/TermsPage/terms.schema.json

@@ -0,0 +1,99 @@
+{
+  "@context": "https://schema.org",
+  "@graph": [
+    {
+      "@type": "Product",
+      "additionalType": "https://schema.org/SoftwareApplication",
+      "@id": "https://ailaunchkit.ai/#product",
+      "name": "AI Launch Kit",
+      "alternateName": [
+        "AI Launch Kit by Working Theory",
+        "AILK by Working Theory",
+        "AILK",
+        "@ailaunchkit",
+        "@ailk",
+        "@working-theory",
+        "ai-launch-kit"
+      ],
+      "url": "https://ailaunchkit.ai",
+      "description": "AI Launch Kit is the open-source website foundation for the agent-first internet — Apache 2.0, agent-ready, AEO-scored, deployable in days.",
+      "sameAs": [
+        "https://github.com/working-theory-labs/ai-launch-kit",
+        "https://x.com/ailaunchkit",
+        "https://www.npmjs.com/org/ailk",
+        "https://youtube.com/@working-theory",
+        "https://linkedin.com/company/working-theory"
+      ],
+      "foundingDate": "2026",
+      "category": "Open-source website foundation",
+      "applicationCategory": "DeveloperApplication",
+      "operatingSystem": "Cross-platform (Node.js)",
+      "license": "https://www.apache.org/licenses/LICENSE-2.0",
+      "codeRepository": "https://github.com/working-theory-labs/ai-launch-kit",
+      "manufacturer": {
+        "@type": "Organization",
+        "@id": "https://ailaunchkit.ai/#organization",
+        "name": "SalesSmyth LLC"
+      },
+      "brand": {
+        "@type": "Brand",
+        "name": "Working Theory",
+        "url": "https://workingtheory.ai"
+      },
+      "creator": {
+        "@id": "https://samhenry.org/#person"
+      },
+      "offers": [
+        {
+          "@type": "Offer",
+          "name": "Free (OSS)",
+          "price": "0",
+          "priceCurrency": "USD"
+        },
+        {
+          "@type": "Offer",
+          "name": "Pro",
+          "price": "249",
+          "priceCurrency": "USD",
+          "priceSpecification": {
+            "@type": "UnitPriceSpecification",
+            "price": "249",
+            "priceCurrency": "USD",
+            "unitText": "per user per year"
+          }
+        },
+        {
+          "@type": "Offer",
+          "name": "Pro Plus",
+          "price": "449",
+          "priceCurrency": "USD",
+          "priceSpecification": {
+            "@type": "UnitPriceSpecification",
+            "price": "449",
+            "priceCurrency": "USD",
+            "unitText": "per user per month"
+          }
+        },
+        {
+          "@type": "Offer",
+          "name": "Launch Service",
+          "price": "2495",
+          "priceCurrency": "USD"
+        }
+      ]
+    },
+    {
+      "@type": "WebPage",
+      "@id": "https://ailaunchkit.ai/terms#webpage",
+      "url": "https://ailaunchkit.ai/terms",
+      "name": "Terms of Service",
+      "description": "The terms governing use of ailaunchkit.ai and the AI Launch Kit paid offerings — Pro, Pro Plus, and Launch Service — operated by SalesSmyth LLC.",
+      "isPartOf": {
+        "@id": "https://ailaunchkit.ai/#product"
+      },
+      "about": {
+        "@id": "https://ailaunchkit.ai/#organization"
+      }
+    }
+  ]
+}

package/templates/content/en/TestimonialsList/testimonials.mdx

@@ -0,0 +1,44 @@
+---
+type: TestimonialsList
+slug: testimonials
+title: Testimonials
+description: What teams building with AI Launch Kit have to say about their experience.
+schema:
+  mainEntity:
+    "@type": ItemList
+    name: AI Launch Kit Testimonials
+    description: Testimonials from teams using AI Launch Kit.
+    itemListElement:
+      - "@type": ListItem
+        position: 1
+        item:
+          "@type": Review
+          reviewBody: >
+            AI Launch Kit cut our time-to-structured-content from weeks to hours.
+            The schema builders and AEO scoring gave us immediate, measurable wins.
+          author:
+            "@type": Person
+            name: Alex Kim
+            jobTitle: Lead Engineer
+      - "@type": ListItem
+        position: 2
+        item:
+          "@type": Review
+          reviewBody: >
+            The section catalog pattern let our team build and iterate on pages
+            without touching layout code. A genuine force-multiplier for small teams.
+          author:
+            "@type": Person
+            name: Morgan Lee
+            jobTitle: Head of Product
+---
+
+# Testimonials
+
+What teams building with AI Launch Kit have to say.
+
+> "AI Launch Kit cut our time-to-structured-content from weeks to hours."
+> — Alex Kim, Lead Engineer
+
+> "The section catalog pattern let our team build and iterate on pages without touching layout code."
+> — Morgan Lee, Head of Product

package/templates/content/en/UseCasesList/use-cases.mdx

@@ -0,0 +1,30 @@
+---
+type: UseCasesList
+slug: use-cases
+title: Use Cases
+description: How teams use AI Launch Kit in production — from agent-first SaaS to AEO-optimized content sites.
+---
+
+# Use Cases
+
+AI Launch Kit is a template, not a product category. These use cases describe how teams have adapted it to their specific situations.
+
+## Agent-first SaaS
+
+Teams building SaaS products where AI agents are first-class users of the API. The MCP server scaffolding in `apps/mcp` gives agents typed tool access to the same data as human users, enforced by the same boundary rules.
+
+## AEO-Optimized Marketing Sites
+
+Marketing and content teams who want their pages to surface in AI search results. AILK's `@working-theory/schema` layer covers 60 schema.org page types. Every page emits valid JSON-LD from frontmatter — no per-page configuration required.
+
+## Internal Tooling with Agent Access
+
+Small engineering teams building internal tools that need both a human-facing UI and agent-accessible APIs. The architecture boundary rules prevent the two surfaces from coupling, so the agent API can evolve independently.
+
+## API Platforms with Structured Outputs
+
+Teams building APIs that need to return data in formats compatible with downstream LLM tooling. The `@working-theory/validation` package provides Zod schemas that double as both request validators and structured-output contracts for agent consumers.
+
+## Getting started
+
+Clone the repository, set the environment variables in `.env.example`, and run `pnpm dev`. The four apps start together. Use the case that fits your situation as a starting point and strip what you don't need.

package/templates/content/en/Whitepaper/ax-first-product-development.mdx

@@ -0,0 +1,27 @@
+---
+type: Whitepaper
+slug: ax-first-product-development
+title: AX-First Product Development
+description: Why treating the API and MCP server as first-class surfaces — not the web app — produces more durable products in the agent era.
+publishedAt: "2026-04-15"
+---
+
+# AX-First Product Development
+
+The conventional web product has a single canonical surface: the browser. An AX-first product has three: the browser, the API, and the MCP server. This paper explains why the shift matters and how AI Launch Kit bakes the pattern in from day one.
+
+## The problem with web-first
+
+Web-first products accumulate UI debt that makes agent integration painful. Data is locked behind HTML rather than behind stable API contracts. Business logic lives in React components rather than route handlers. When an agent needs to act on behalf of a user, it has to scrape or emulate a browser — which is fragile.
+
+## The AX-first principle
+
+AX-first means the API and MCP tool surface are designed before the web UI, not after. The web app becomes the human edge — a presentation layer for capabilities that also exist in machine-readable form.
+
+## How AILK implements it
+
+AILK ships three peer apps behind a shared `packages/` layer. `apps/api` exposes Fastify routes validated by Zod. `apps/mcp` exposes the same capabilities as MCP tools. `apps/web` calls `apps/api` via `@working-theory/api-client` — it never touches the database directly. The architecture boundary linter fails CI if any app crosses these lines.
+
+## The payoff
+
+Teams that start AX-first can add AI features as natural extensions of existing capabilities, not as retrofits. Agent tools are the same code as API routes. Structured data is the same code as API responses.

package/templates/content/en/Whitepaper/open-core-commercial-strategy.mdx

@@ -0,0 +1,27 @@
+---
+type: Whitepaper
+slug: open-core-commercial-strategy
+title: Open-Core Commercial Strategy for Developer Tools
+description: How open-core licensing enables sustainable developer-tool businesses — the model AILK uses and why it works for agent-era infrastructure.
+publishedAt: "2026-04-29"
+---
+
+# Open-Core Commercial Strategy for Developer Tools
+
+The open-core model — a free OSS core with paid extensions — has produced some of the most durable developer-tool businesses of the last decade. This paper explains why it works and how AILK applies it.
+
+## Why open-core for developer tools
+
+Developers evaluate tools before they pay for them. A free OSS tier removes the evaluation barrier and builds genuine trust — you can't fake a working codebase. The paid tier captures value from the users who build significant businesses on top of the free core.
+
+## The AILK tier structure
+
+AILK ships a `packages/` layer under the MIT license. The core schema builders, content adapter, and AEO scorer are OSS. Paid extensions — advanced scoring rules, the Pro CMS adapter, multi-tenant infrastructure — ship separately under a commercial license.
+
+## The commoditization line
+
+AILK draws the OSS/paid boundary at the point where the open-source alternative is free anyway (schema.org JSON-LD generation) and the commercial alternative is expensive (a custom structured-data pipeline). OSS below the line; commercial above it.
+
+## Why this works for agent-era infrastructure
+
+Agent-era infrastructure is early enough that developers are still learning the patterns. OSS is the fastest path to pattern adoption; commercial tiers capture value from teams running those patterns in production at scale.

package/templates/content/en/Whitepaper/structured-data-for-answer-engines.mdx

@@ -0,0 +1,31 @@
+---
+type: Whitepaper
+slug: structured-data-for-answer-engines
+title: Structured Data for Answer Engines
+description: How schema.org JSON-LD markup improves citation rates in AI-generated answers — the Layer 1 citation-readiness model explained.
+publishedAt: "2026-04-22"
+---
+
+# Structured Data for Answer Engines
+
+Answer engines — AI systems that generate responses by synthesizing information across sources — prefer pages that declare their meaning explicitly. Schema.org JSON-LD is the most widely understood mechanism for doing so.
+
+## Why structured data matters for AEO
+
+When an answer engine encounters two pages covering the same topic, the page with valid structured data has a structural advantage. The engine can confirm the page's claimed authority (`Organization`, `author`, `datePublished`) without natural-language inference.
+
+## The Layer 1 model
+
+AILK's AEO scorer defines Layer 1 as a set of deterministic, field-level checks. A page passes Layer 1 when it satisfies all of:
+
+- `@type` is a recognized schema.org type
+- `name` or `headline` is present and non-empty
+- `description` is present and non-empty
+- `inLanguage` is set to the page locale
+- `url` is an absolute URL
+
+These checks are structural — they require no network access and produce identical results on every run.
+
+## Implementation in AILK
+
+Every page type in `@working-theory/schema` emits a JSON-LD object that satisfies Layer 1. The `pageToJsonLd` bridge in `apps/web` wires MDX frontmatter to the right builder automatically. Teams using AILK get Layer 1 compliance out of the box.

package/templates/content/en-XA/AboutPage/about.mdx

@@ -0,0 +1,8 @@
+---
+type: AboutPage
+slug: about
+title: "[!!! Ŵĥó búíĺţ ÁÍĹK, áñð ŵĥý ŵé ŕúñ óñ íţ →→ →→ →→ →→ →→ →→ →→ !!!]"
+description: Pseudolocale smoke-gate placeholder — en-XA content mirrors en with pseudolocalization applied.
+---
+
+<!-- en-XA pseudolocale content. The page renders from frontmatter title; sections are intentionally omitted for the smoke gate. -->

package/templates/content/en-XA/FAQPage/faq.mdx

@@ -0,0 +1,8 @@
+---
+type: FAQPage
+slug: faq
+title: "[!!! Fŕéqúéñţĺý áškéð qúéšţíóñš ábóúţ ÁÍ Ĺáúñçĥ Kíţ →→ →→ →→ →→ →→ →→ →→ →→ →→ !!!]"
+description: Pseudolocale smoke-gate placeholder — en-XA content mirrors en with pseudolocalization applied.
+---
+
+<!-- en-XA pseudolocale content. The page renders from frontmatter title; sections are intentionally omitted for the smoke gate. -->

package/templates/content/en-XA/HomePage/home.mdx

@@ -0,0 +1,8 @@
+---
+type: HomePage
+slug: home
+title: "[!!! ÁÍ Ĺáúñçĥ Kíţ — ţĥé ópéñ-šóúŕçé ŵébšíţé fóúñðáţíóñ fóŕ ţĥé áĝéñţ-fíŕšţ íñţéŕñéţ →→ →→ →→ →→ →→ →→ →→ →→ →→ →→ →→ →→ →→ →→ →→ →→ !!!]"
+description: Pseudolocale smoke-gate placeholder — en-XA content mirrors en with pseudolocalization applied.
+---
+
+<!-- en-XA pseudolocale content. The page renders from frontmatter title; sections are intentionally omitted for the smoke gate. -->

package/templates/content/es/_site.mdx

@@ -0,0 +1,30 @@
+---
+version: "1"
+siteName: AI Launch Kit
+baseUrl: https://ailaunchkit.ai
+defaultLocale: es
+siteIdentity:
+  kind: Organization
+  name: AI Launch Kit
+  url: https://ailaunchkit.ai
+  logo: https://ailaunchkit.ai/opengraph-image.png
+  description: >
+    AI Launch Kit es la base de sitio web open-source para la internet
+    centrada en agentes. Apache 2.0, listo para agentes, con puntuación AEO,
+    desplegable en días.
+  sameAs:
+    - https://github.com/tailwind-ai/ai-launch-kit
+  foundingDate: "2024"
+  founderName: Sam Henry
+analytics:
+  vercelAnalytics: true
+---
+
+<!--
+Locale-specific site configuration for the 'es' (Spanish) locale.
+Theme fonts for this locale are declared in app/[locale]/layout.tsx
+under the LOCALE_FONTS registry (locale key: "es" → Lato).
+
+Per-route font scoping: Spanish pages ship Lato (Latin coverage).
+Japanese font (Noto Sans JP) is NOT registered on Spanish pages.
+-->

package/templates/content/fr/_site.mdx

@@ -0,0 +1,30 @@
+---
+version: "1"
+siteName: AI Launch Kit
+baseUrl: https://ailaunchkit.ai
+defaultLocale: fr
+siteIdentity:
+  kind: Organization
+  name: AI Launch Kit
+  url: https://ailaunchkit.ai
+  logo: https://ailaunchkit.ai/opengraph-image.png
+  description: >
+    AI Launch Kit est la fondation de site web open-source pour l'internet
+    centré sur les agents. Apache 2.0, prêt pour les agents, noté AEO,
+    déployable en quelques jours.
+  sameAs:
+    - https://github.com/tailwind-ai/ai-launch-kit
+  foundingDate: "2024"
+  founderName: Sam Henry
+analytics:
+  vercelAnalytics: true
+---
+
+<!--
+Locale-specific site configuration for the 'fr' (French) locale.
+Theme fonts for this locale are declared in app/[locale]/layout.tsx
+under the LOCALE_FONTS registry (locale key: "fr" → Source Sans 3).
+
+Per-route font scoping: French pages ship Source Sans 3 (Latin-ext coverage).
+Japanese font (Noto Sans JP) is NOT registered on French pages.
+-->

package/templates/content/ja/_site.mdx

@@ -0,0 +1,30 @@
+---
+version: "1"
+siteName: AI Launch Kit
+baseUrl: https://ailaunchkit.ai
+defaultLocale: ja
+siteIdentity:
+  kind: Organization
+  name: AI Launch Kit
+  url: https://ailaunchkit.ai
+  logo: https://ailaunchkit.ai/opengraph-image.png
+  description: >
+    AI Launch Kitはエージェントファーストのインターネット向けオープンソースウェブサイト基盤です。
+    Apache 2.0、エージェント対応、AEOスコア付き、数日でデプロイ可能。
+  sameAs:
+    - https://github.com/tailwind-ai/ai-launch-kit
+  foundingDate: "2024"
+  founderName: Sam Henry
+analytics:
+  vercelAnalytics: true
+---
+
+<!--
+Locale-specific site configuration for the 'ja' (Japanese) locale.
+Theme fonts for this locale are declared in app/[locale]/layout.tsx
+under the LOCALE_FONTS registry (locale key: "ja" → Noto Sans JP).
+
+Per-route font scoping: Japanese pages ship Noto Sans JP (JP + Latin coverage).
+Escalation per spec §5.3: if Noto Sans JP causes LCP regression on /ja routes,
+stop and escalate — subsetting strategy / CDN config required.
+-->

package/templates/content/pt-BR/AboutPage/about.mdx

@@ -0,0 +1,8 @@
+---
+type: AboutPage
+slug: about
+title: Quem construiu o AILK e por que o usamos
+description: AI Launch Kit é a fundação open-source para sites da internet orientada a agentes. Um produto Working Theory, liderado por Sam Henry, usado em três marcas.
+---
+
+<!-- Corpo MDX preservado para adaptadores de conteúdo que o utilizam, mas a página renderiza a partir das seções do frontmatter. -->

package/templates/content/pt-BR/FAQPage/faq.mdx

@@ -0,0 +1,8 @@
+---
+type: FAQPage
+slug: faq
+title: Perguntas frequentes sobre o AI Launch Kit
+description: Perguntas comuns sobre o AI Launch Kit, agrupadas por tema. Cada resposta pode ser lida de forma independente.
+---
+
+<!-- Corpo MDX preservado para adaptadores de conteúdo que o utilizam, mas a página renderiza a partir das seções do frontmatter. -->

package/templates/content/pt-BR/HomePage/home.mdx

@@ -0,0 +1,23 @@
+---
+type: HomePage
+slug: home
+title: AI Launch Kit — a fundação open-source para sites da internet orientada a agentes
+description: O starter de sites open-source Apache 2.0 construído para busca por IA. Pronto para agentes, com pontuação AEO, implantável em dias.
+sections:
+  - id: hero-1
+    type: hero
+    data:
+      variant: centered
+      headline: AI Launch Kit — a fundação open-source para sites da internet orientada a agentes
+      subheadline: O starter de sites open-source Apache 2.0 construído para busca por IA. Pronto para agentes, com pontuação AEO, implantável em dias.
+      body: Construído pela equipe Working Theory e usado pela equipe para rodar Sam Henry, Working Theory e SalesSmyth no mesmo substrato.
+      primaryCta:
+        label: Escolha seu caminho
+        href: "#escolha-seu-caminho"
+      secondaryCta:
+        label: Star no GitHub
+        href: https://github.com/working-theory/ai-launch-kit
+        external: true
+---
+
+<!-- Corpo MDX preservado para adaptadores de conteúdo que o utilizam, mas a página renderiza a partir das seções do frontmatter. -->

package/templates/database/CHANGELOG.md

@@ -0,0 +1,5 @@
+# @working-theory/database
+
+## 0.1.2
+
+## 0.1.1

package/templates/database/README.md

@@ -0,0 +1,234 @@
+# Customer Template Database
+
+Minimal but extensible Prisma schema for customer-hosted instances.
+
+## Namespace Layout
+
+Five namespace subfolders organise database concerns. See [namespaces](../docs/database/namespaces.md) for the full boundary doc, and [ADR 0009](../docs/adr/0009-database-namespace-separation.md) for the formal decision record.
+
+- `auth/` — NextAuth, API tokens, OAuth, push tokens
+- `config/` — site settings and customer configuration
+- `content/` — content-related extensions
+- `inbox/` — messaging and notification data
+- `ops/` — operational and observability data
+
+## Overview
+
+This database stores **only auth and customer extensions**. All business data (leads, orders, analytics) lives on the Platform.
+
+| Category   | Tables                                    | Purpose                          |
+| ---------- | ----------------------------------------- | -------------------------------- |
+| NextAuth   | User, Account, Session, VerificationToken | Web dashboard login              |
+| API Auth   | ApiToken, RefreshToken                    | Mobile apps, long-lived sessions |
+| OAuth      | OAuthClient, OAuthAuthorization           | ChatGPT plugin, Slack bot, etc.  |
+| Push       | PushToken                                 | Mobile push notifications        |
+| Extensions | UserData, SiteSetting                     | Customer customizations          |
+
+**Total: 11 tables**
+
+## Why This Architecture?
+
+1. **Customer sites are nearly stateless** - No business logic in DB
+2. **All data centralized on Platform** - Leads, orders, analytics, conversions
+3. **Extensibility built-in** - Customers can add preferences/custom data
+4. **Multi-client support** - Web sessions + API tokens for mobile
+
+## Schema
+
+### NextAuth (Web Authentication)
+
+```prisma
+model User {
+  id, email, name, image, role
+  accounts, sessions, apiTokens, userData
+}
+
+model Account     { /* OAuth connections */ }
+model Session     { /* Active sessions */ }
+model VerificationToken { /* Email verification */ }
+```
+
+### API Tokens (Mobile/External Auth)
+
+```prisma
+model ApiToken {
+  userId, name, token, tokenPrefix
+  clientType  // "mobile", "api", "cli"
+  deviceInfo  // "iPhone 15 Pro"
+  scopes      // ["read:profile", "write:data"]
+  expiresAt, lastUsedAt, revokedAt
+}
+
+model RefreshToken {
+  userId, apiTokenId, token
+  expiresAt, usedAt, revokedAt
+}
+```
+
+**Usage:**
+
+```bash
+# Mobile app authenticates with token
+curl -H "Authorization: Bearer tok_abc123..." \
+  https://api.customer-site.com/api/user/profile
+
+# Refresh expired access token
+curl -X POST https://api.customer-site.com/api/auth/refresh \
+  -d '{"refresh_token": "ref_xyz789..."}'
+```
+
+### OAuth (ChatGPT, Slack, External Apps)
+
+```prisma
+model OAuthClient {
+  name, clientId, clientSecret
+  redirectUris, scopes
+  enabled, trusted
+}
+
+model OAuthAuthorization {
+  userId, clientId, scopes
+  accessToken, refreshToken
+  expiresAt, revokedAt
+}
+```
+
+**Usage:** ChatGPT plugin authenticates users via OAuth flow, stores authorization.
+
+### Push Notifications (Mobile)
+
+```prisma
+model PushToken {
+  userId, token, platform  // "ios", "android", "web"
+  deviceId, deviceName, appVersion
+  enabled, failedAt, failCount
+}
+```
+
+**Usage:**
+
+```typescript
+// Register device for push notifications
+await prisma.pushToken.upsert({
+  where: { token: fcmToken },
+  update: { updatedAt: new Date() },
+  create: {
+    userId,
+    token: fcmToken,
+    platform: "android",
+    deviceName: "Pixel 8",
+  },
+});
+```
+
+### Extensions (Customer Customizations)
+
+```prisma
+model UserData {
+  userId, key, value  // Flexible per-user storage
+}
+
+model SiteSetting {
+  key, value  // Site-wide config/cache
+}
+```
+
+**Usage:**
+
+```typescript
+// Store user preferences
+await prisma.userData.upsert({
+  where: { userId_key: { userId, key: "preferences" } },
+  update: { value: { theme: "dark", notifications: true } },
+  create: { userId, key: "preferences", value: { theme: "dark" } },
+});
+
+// Store site-wide cache
+await prisma.siteSetting.upsert({
+  where: { key: "cached_config" },
+  update: { value: platformConfig },
+  create: { key: "cached_config", value: platformConfig },
+});
+```
+
+### Prisma config (`prisma.config.ts`)
+
+Required by Prisma 7 for non-default CLI configuration. AILK uses it to:
+
+- Point the CLI at `./schema.prisma`.
+- Declare the migrate-time DB URL (`DATABASE_URL_NON_POOLED`) for `prisma migrate`. The runtime DB URL (`DATABASE_URL`) is injected into the driver adapter at PrismaClient construction in `apps/api` and `apps/web`.
+
+Forks: do not edit unless your deployment uses different env-var names. The two-env-var contract (pooled + non-pooled) is part of the AILK template; changing the names requires updating both the runtime singletons and this file.
+
+## Setup
+
+### 1. Configure Database URL
+
+```env
+DATABASE_URL="postgresql://user:password@localhost:5432/mydb"
+DATABASE_URL_NON_POOLED="postgresql://user:password@localhost:5432/mydb"
+```
+
+### 2. Generate Prisma Client
+
+```bash
+pnpm db:generate
+```
+
+### 3. Push Schema (Development)
+
+```bash
+pnpm db:push
+```
+
+### 4. Create Migration (Production)
+
+```bash
+pnpm db:migrate
+```
+
+## Available Scripts
+
+| Script             | Description                             |
+| ------------------ | --------------------------------------- |
+| `pnpm db:generate` | Generate Prisma Client                  |
+| `pnpm db:migrate`  | Create and apply migrations (dev)       |
+| `pnpm db:push`     | Push schema changes directly (dev only) |
+| `pnpm db:studio`   | Open Prisma Studio GUI                  |
+
+## What's NOT in This Schema
+
+Business data is **intentionally excluded** - it lives on the Platform:
+
+| Data      | Where    | Why                           |
+| --------- | -------- | ----------------------------- |
+| Leads     | Platform | ROI tracking, tied to content |
+| Orders    | Platform | Conversion tracking           |
+| Analytics | Platform | Aggregate dashboards          |
+| Content   | Platform | Created in Studio             |
+
+## Extending the Schema
+
+Customers can extend the schema for custom features:
+
+```prisma
+// Example: Add a SavedItem model for wishlists
+model SavedItem {
+  id        String   @id @default(cuid())
+  userId    String
+  itemType  String   // "product", "blog_post"
+  itemId    String   // Platform ID
+  savedAt   DateTime @default(now())
+
+  user User @relation(fields: [userId], references: [id], onDelete: Cascade)
+
+  @@unique([userId, itemType, itemId])
+  @@map("saved_items")
+}
+```
+
+Remember to:
+
+1. Add the relation to the `User` model
+2. Run `pnpm db:migrate`
+3. Update your backend routes