create-ailk 0.3.0 → 0.4.0

package/dist/surfaces.js

@@ -164,6 +164,19 @@ export const GATEABLE_SURFACES = [
         routes: [`${ROUTE_ROOT}/partners`],
         content: ["content/<locale>/PartnersList", "content/<locale>/Partner"],
     },
+    {
+        // Module-LESS by construction (#5479 D16): no MODULE_SURFACES value names
+        // it, so a site template may enable it by roster alone. Same for
+        // `privacy` and `terms` below.
+        id: "pricing",
+        routes: [`${ROUTE_ROOT}/pricing`],
+        content: ["content/<locale>/Pricing"],
+    },
+    {
+        id: "privacy",
+        routes: [`${ROUTE_ROOT}/privacy`],
+        content: ["content/<locale>/PrivacyPage"],
+    },
     {
         id: "products",
         routes: [`${ROUTE_ROOT}/products`],
@@ -208,6 +221,11 @@ export const GATEABLE_SURFACES = [
         routes: [`${ROUTE_ROOT}/tech-articles`],
         content: ["content/<locale>/TechArticle"],
     },
+    {
+        id: "terms",
+        routes: [`${ROUTE_ROOT}/terms`],
+        content: ["content/<locale>/TermsPage"],
+    },
     {
         id: "testimonials",
         routes: [`${ROUTE_ROOT}/testimonials`],
@@ -247,6 +265,12 @@ export const MODULE_SURFACES = {
     marketing: [],
     "docs-blog": ["docs", "blog"],
     "multi-tenant": [],
+    // `workspace` contributes zero gateable surfaces (#5371 D4): every route it
+    // owns lives in the `(authed)` segment, never in the public marketing route
+    // tree a template's roster composes — the same reason `multi-tenant` above
+    // carries an empty list. The entry itself is still required: surface-gating's
+    // vocabulary assertion covers exactly the recognized module set.
+    workspace: [],
     scheduling: ["schedule"],
     "signal-collectors": ["flows"],
     commerce: [],
@@ -409,6 +433,11 @@ export const ROUTE_SINCE = {
     "launch-service": "0.0.0",
     partners: "0.0.0",
     "partners/[slug]": "0.0.0",
+    // #5479 — three genuinely new route directories, so they attach at today's
+    // fixed-group version rather than the "predates the manifest" 0.0.0 above,
+    // the same rule #5048 ("projects/apply") and #5014 ("(authed)") applied.
+    pricing: "0.22.0",
+    privacy: "0.22.0",
     products: "0.0.0",
     "products/[slug]": "0.0.0",
     projects: "0.0.0",
@@ -428,6 +457,7 @@ export const ROUTE_SINCE = {
     "software/[slug]": "0.0.0",
     "tech-articles": "0.0.0",
     "tech-articles/[slug]": "0.0.0",
+    terms: "0.22.0",
     testimonials: "0.0.0",
     "thanks/[slug]": "0.14.0",
     "use-cases": "0.0.0",
@@ -444,6 +474,12 @@ export const ROUTE_SINCE = {
     // choice #5048's "projects/apply" entry already made for the same reason.
     "(authed)": "0.18.0",
     "(authed)/account": "0.18.0",
+    // #5371 — the workspace module's three settings routes. Genuinely new route
+    // directories, so they attach at today's fixed-group version rather than the
+    // "predates the manifest" 0.0.0 above, the same rule #5479 and #5048 applied.
+    "(authed)/workspace": "0.22.1",
+    "(authed)/workspace/site": "0.22.1",
+    "(authed)/workspace/team": "0.22.1",
     "(authed)/waitlist": "0.18.0",
     "(authed)/waitlist/[experimentId]": "0.18.0",
     "(authed)/waitlist/[experimentId]/signups/[leadId]": "0.18.0",
@@ -490,6 +526,9 @@ export const ROUTE_DEPENDENCIES = {
         `${ROUTE_ROOT}/(authed)/waitlist/components/ForbiddenState.tsx`,
         `${ROUTE_ROOT}/(authed)/waitlist/format.ts`,
     ],
+    "(authed)/workspace": ["apps/web/lib/server-api.ts"],
+    "(authed)/workspace/site": ["apps/web/lib/server-api.ts"],
+    "(authed)/workspace/team": ["apps/web/lib/server-api.ts"],
     "(authed)/waitlist": ["apps/web/lib/server-api.ts"],
 };
 /**
@@ -504,6 +543,9 @@ export const ROUTE_DEPENDENCIES = {
 export const ROUTE_MESSAGE_NAMESPACES = {
     "sign-in": ["signIn"],
     "(authed)/account": ["account"],
+    "(authed)/workspace": ["workspace"],
+    "(authed)/workspace/site": ["workspace"],
+    "(authed)/workspace/team": ["workspace"],
     "(authed)/waitlist": ["waitlistDashboard.gate"],
 };
 /** Template-relative path of the generated site-nav registry. */

package/dist/template-manifest.d.ts

@@ -0,0 +1,92 @@
+import { type PageRosterRow } from "./module-architecture.js";
+import type { ModuleName } from "./parse-args.js";
+/**
+ * One site template: its fixed module list and the page rows it brings itself.
+ *
+ * THERE IS NO `tier`, `level` OR `price` MEMBER, and there never is one
+ * (parent § D4). Delivery tier is DERIVED from `requires` — by the client via
+ * `templateDelivery` below, and by the issuer via `TIER_SPECS` (#5480) — so
+ * declaring it here would be a second authority for a fact the module list
+ * already settles. The type, not a convention, is what makes adding one a
+ * compile error: a convention is a thing someone must remember.
+ *
+ * There is likewise no optional-module member (parent § D12). A template's
+ * level must be readable from ONE fixed list; a soft list would make the same
+ * template Free or Pro depending on the key.
+ */
+export interface TemplateManifest {
+    /** Template name. Equals this manifest's `TEMPLATE_MANIFESTS` key. */
+    name: string;
+    /**
+     * The modules whose PAGES this template's roster uses (parent § D15) — not
+     * the modules its level bundles. Typed against `ModuleName`, so an
+     * unrecognized name fails type-check rather than a runtime validation.
+     */
+    requires: readonly ModuleName[];
+    /** Base rows, before any module's contribution is merged. */
+    roster: readonly PageRosterRow[];
+    /** Bundle-relative source → scaffold-relative destination. */
+    installMap?: Record<string, string>;
+}
+/** Thrown on an undeclared template name or a route claimed twice. Mirrors `SurfaceError`'s shape. */
+export declare class TemplateError extends Error {
+    constructor(message: string);
+}
+/**
+ * The three settled templates and their fixed `requires` lists — settled by
+ * Sam, 2026-09-14 (parent § D12). The plain name is the Pro one: it is the
+ * flagship and the demo.
+ *
+ * `workspace` appears in none of them. It is a Pro module, but an authed app
+ * surface contributing no PUBLIC page to a marketing site, and `requires`
+ * names what the roster uses (parent § D15). A Pro key unlocks it regardless
+ * of any template. `ModuleName` could not express it in any case —
+ * `RECOGNIZED_MODULES` is the six names and `workspace` is not among them.
+ *
+ * `commerce` is likewise in none of them: it is a per-site add-on available at
+ * any level, so a template for it would contradict the offering model and
+ * multiply the set combinatorially (parent § D13). It still contributes rows
+ * to whichever template takes it, through `mergeRoster` below.
+ */
+export declare const TEMPLATE_MANIFESTS: Record<string, TemplateManifest>;
+/** Look up a declared template. @throws TemplateError on an undeclared name. */
+export declare function resolveTemplate(name: string): TemplateManifest;
+/**
+ * Compose a template's roster: its base rows, then each taken module's
+ * contributed rows in `normalizeModules` order (parent § D7).
+ *
+ * `normalizeModules` is REUSED rather than re-sorted here. It already returns
+ * the unique set ordered by `RECOGNIZED_MODULES`, and `scaffold()` already
+ * calls it — a second sort at this call site would be a second ordering
+ * authority that could drift from the one `deriveArchitecture` depends on.
+ * That also makes the merge a pure function of the module SET: the same set in
+ * any argument order returns identical rows.
+ *
+ * The merge is pure and writes nothing. Staging a contributed row's seed
+ * content is the bundle producer's job (`build-module-bundles.mjs`, #5481);
+ * doing it here would put a filesystem dependency in a function three sibling
+ * units import for its return value.
+ *
+ * @param modules the modules this scaffold takes. A template's `requires` are
+ *   taken by definition — a required module whose bundle cannot be had refuses
+ *   the install outright (parent § D17, #5481) rather than merging short.
+ * @throws TemplateError when two sources claim one route (parent § D8). Both
+ *   the base roster and every contribution are compile-time known, so the
+ *   collision is caught by a test before a bundle exists — never resolved at
+ *   runtime by a base-wins or module-wins precedence rule, either of which
+ *   silently produces a site missing a page someone declared.
+ */
+export declare function mergeRoster(manifest: TemplateManifest, modules: readonly string[]): PageRosterRow[];
+/**
+ * Whether a template installs on the keyless path or needs a verified
+ * `AILK_LICENSE_KEY` — derived from `requires`, never declared (parent § D3).
+ *
+ * The derivation goes through the existing `classifyModules` rather than a
+ * second list of paid names, which would drift. This is deliberately the
+ * CLIENT half of a two-derivation split: the issuer derives the commercial
+ * LEVEL from the same `requires` via `TIER_SPECS` (#5480). One shared
+ * derivation would force this package to import
+ * `@working-theory/license-manifest` — a `restricted` package — breaking
+ * `pnpm install` for every Free consumer, not merely gating the paid path.
+ */
+export declare function templateDelivery(manifest: TemplateManifest): "free" | "paid";

package/dist/template-manifest.js

@@ -0,0 +1,168 @@
+/**
+ * Site-template registry, and the roster merge that composes a template with
+ * the modules it takes (spec 5478, unit A of the site-templates mechanism;
+ * design record docs/specs/5462-site-templates-module-bundles-spec.md).
+ *
+ * A site template is DATA AND CONTENT, NOT CODE: a page roster, seed content
+ * and config — never a `page.tsx` (parent § D16). This file declares what a
+ * template IS. It declares no delivery channel, reads no licence, and touches
+ * no disk: the `--template` flag, the bundle fetch and the landing order are
+ * #5481's, and `GET /v1/templates/:name/:version` is #5480's.
+ *
+ * A CODE registry, not per-template JSON (parent § D2): in TypeScript,
+ * `requires` is checked against `RECOGNIZED_MODULES` at compile time, and this
+ * package already twice records that a fixed template FILE is the drift a
+ * registry removes.
+ */
+import { classifyModules } from "./lib/module-tier.js";
+import { MODULE_SLICES, normalizeModules, } from "./module-architecture.js";
+/** Thrown on an undeclared template name or a route claimed twice. Mirrors `SurfaceError`'s shape. */
+export class TemplateError extends Error {
+    constructor(message) {
+        super(message);
+        this.name = "TemplateError";
+    }
+}
+/**
+ * `/pricing`, `/privacy` and `/terms` — the three module-less rows every
+ * declared template brings itself.
+ *
+ * Module-less by construction (parent § D16): no module owns these surfaces,
+ * their route files live in `apps/web` and are snapshotted into the starter
+ * like every other route, and a template enables them by NAMING them in its
+ * roster. Registering the three as `GATEABLE_SURFACES` entries is #5479's; the
+ * rows are declared here because the roster is what a template is.
+ */
+const TEMPLATE_BASE_ROSTER = [
+    { route: "/pricing", content: ["content/en/Pricing/pricing.mdx"] },
+    { route: "/privacy", content: ["content/en/PrivacyPage/privacy.mdx"] },
+    { route: "/terms", content: ["content/en/TermsPage/terms.mdx"] },
+];
+/**
+ * The three settled templates and their fixed `requires` lists — settled by
+ * Sam, 2026-09-14 (parent § D12). The plain name is the Pro one: it is the
+ * flagship and the demo.
+ *
+ * `workspace` appears in none of them. It is a Pro module, but an authed app
+ * surface contributing no PUBLIC page to a marketing site, and `requires`
+ * names what the roster uses (parent § D15). A Pro key unlocks it regardless
+ * of any template. `ModuleName` could not express it in any case —
+ * `RECOGNIZED_MODULES` is the six names and `workspace` is not among them.
+ *
+ * `commerce` is likewise in none of them: it is a per-site add-on available at
+ * any level, so a template for it would contradict the offering model and
+ * multiply the set combinatorially (parent § D13). It still contributes rows
+ * to whichever template takes it, through `mergeRoster` below.
+ */
+export const TEMPLATE_MANIFESTS = {
+    /**
+     * The Free template, and the mechanism's own proof (parent § D11): it
+     * requires only `marketing`, so the keyless merge path is exercised by a
+     * template we ship anyway rather than by a throwaway fixture.
+     */
+    "marketing-site-free": {
+        name: "marketing-site-free",
+        requires: ["marketing"],
+        roster: TEMPLATE_BASE_ROSTER,
+    },
+    /**
+     * The Pro flagship. Its module list is OFFERINGS § 4 offering 3's tiers line
+     * — "docs, scheduling and flows modules" — where "flows" is
+     * `signal-collectors` (`MODULE_SURFACES` maps it to `["flows"]`).
+     */
+    "marketing-site": {
+        name: "marketing-site",
+        requires: ["marketing", "docs-blog", "scheduling", "signal-collectors"],
+        roster: TEMPLATE_BASE_ROSTER,
+    },
+    /**
+     * Pro Plus — the Pro list plus `multi-tenant`, which is correctly in the
+     * list because it DOES contribute pages (the org and workspace surfaces).
+     * Its `pageContributions` is nonetheless unset today, deferred to its own
+     * instance, so this template's merged roster carries the same contributed
+     * rows as `marketing-site`'s and no more. That is a module which has
+     * declared no rows yet — visible in the diff — not a merge that dropped
+     * declared rows.
+     */
+    "saas-product": {
+        name: "saas-product",
+        requires: [
+            "marketing",
+            "docs-blog",
+            "scheduling",
+            "signal-collectors",
+            "multi-tenant",
+        ],
+        roster: TEMPLATE_BASE_ROSTER,
+    },
+};
+/** Look up a declared template. @throws TemplateError on an undeclared name. */
+export function resolveTemplate(name) {
+    const manifest = TEMPLATE_MANIFESTS[name];
+    if (!manifest) {
+        throw new TemplateError(`unknown template "${name}". Declared: ${Object.keys(TEMPLATE_MANIFESTS).join(", ")}`);
+    }
+    return manifest;
+}
+/**
+ * Compose a template's roster: its base rows, then each taken module's
+ * contributed rows in `normalizeModules` order (parent § D7).
+ *
+ * `normalizeModules` is REUSED rather than re-sorted here. It already returns
+ * the unique set ordered by `RECOGNIZED_MODULES`, and `scaffold()` already
+ * calls it — a second sort at this call site would be a second ordering
+ * authority that could drift from the one `deriveArchitecture` depends on.
+ * That also makes the merge a pure function of the module SET: the same set in
+ * any argument order returns identical rows.
+ *
+ * The merge is pure and writes nothing. Staging a contributed row's seed
+ * content is the bundle producer's job (`build-module-bundles.mjs`, #5481);
+ * doing it here would put a filesystem dependency in a function three sibling
+ * units import for its return value.
+ *
+ * @param modules the modules this scaffold takes. A template's `requires` are
+ *   taken by definition — a required module whose bundle cannot be had refuses
+ *   the install outright (parent § D17, #5481) rather than merging short.
+ * @throws TemplateError when two sources claim one route (parent § D8). Both
+ *   the base roster and every contribution are compile-time known, so the
+ *   collision is caught by a test before a bundle exists — never resolved at
+ *   runtime by a base-wins or module-wins precedence rule, either of which
+ *   silently produces a site missing a page someone declared.
+ */
+export function mergeRoster(manifest, modules) {
+    const merged = [];
+    /** route → the source that claimed it, for the collision message. */
+    const claimedBy = new Map();
+    const take = (rows, source) => {
+        for (const row of rows) {
+            const owner = claimedBy.get(row.route);
+            if (owner !== undefined) {
+                throw new TemplateError(`route "${row.route}" is claimed by both ${owner} and ${source}`);
+            }
+            claimedBy.set(row.route, source);
+            merged.push(row);
+        }
+    };
+    take(manifest.roster, `template "${manifest.name}"`);
+    for (const module of normalizeModules([...modules])) {
+        take(MODULE_SLICES[module].pageContributions ?? [], `module "${module}"`);
+    }
+    return merged;
+}
+/**
+ * Whether a template installs on the keyless path or needs a verified
+ * `AILK_LICENSE_KEY` — derived from `requires`, never declared (parent § D3).
+ *
+ * The derivation goes through the existing `classifyModules` rather than a
+ * second list of paid names, which would drift. This is deliberately the
+ * CLIENT half of a two-derivation split: the issuer derives the commercial
+ * LEVEL from the same `requires` via `TIER_SPECS` (#5480). One shared
+ * derivation would force this package to import
+ * `@working-theory/license-manifest` — a `restricted` package — breaking
+ * `pnpm install` for every Free consumer, not merely gating the paid path.
+ */
+export function templateDelivery(manifest) {
+    return classifyModules([...manifest.requires]).paid.length > 0
+        ? "paid"
+        : "free";
+}

package/dist/template-names.d.ts

@@ -0,0 +1,41 @@
+/**
+ * The `--template` flag's vocabulary, and nothing else.
+ *
+ * WHY THIS FILE EXISTS, measured rather than assumed. Spec 5481 § 3 DD1 has
+ * `parse-args.ts` validate `--template` against `TEMPLATE_MANIFESTS` through a
+ * runtime import, on the grounds that the registry's own dependency on
+ * `parse-args.ts` (for `ModuleName`) is `import type` and so erases at
+ * compile. That is true of the DIRECT edge and false of the graph:
+ * `template-manifest.ts` imports `lib/module-tier.js` and
+ * `module-architecture.js` as RUNTIME values, and BOTH of those import
+ * `RECOGNIZED_MODULES` — a runtime value — back from `parse-args.ts`.
+ * `module-tier.ts` then reads it at MODULE SCOPE to derive `PAID_MODULES`.
+ * So `parse-args.ts` importing the registry closes a runtime cycle whose
+ * first read lands in the temporal dead zone:
+ *
+ *     ReferenceError: Cannot access 'RECOGNIZED_MODULES' before initialization
+ *
+ * — reproduced against the built `dist/` while implementing this unit, not
+ * theorised. `surfaces.ts`'s header warns about exactly this relationship
+ * ("Deliberately imports nothing from `parse-args.ts`: that module imports
+ * THIS one … so a back-import would close a cycle"), and `surfaces.ts` is the
+ * precedent this file follows: the flag's vocabulary lives in a module the
+ * parser can import because it imports nothing at all.
+ *
+ * THE REGISTRY IS STILL `template-manifest.ts` (parent record D2). This file
+ * declares NAMES; that one declares what a template IS — `requires`, the
+ * roster, the `installMap`, the free-vs-paid derivation — and it stays the
+ * single place a template is defined. The two cannot drift: the names here
+ * are asserted equal to `Object.keys(TEMPLATE_MANIFESTS)` by
+ * `__tests__/template-scaffold.test.ts`, so adding a template without listing
+ * it here (or the reverse) fails the suite rather than shipping a flag that
+ * accepts a name the registry does not know.
+ *
+ * Rejected: lazifying `module-tier.ts`'s `PAID_MODULES` to break the cycle at
+ * its source. It is the correct structural fix and it is not this unit's to
+ * make — `module-tier.ts` is a READ row in spec 5481 § 4, and `PAID_MODULES`
+ * is consumed as a plain array across the package.
+ */
+/** The declared site templates, in `TEMPLATE_MANIFESTS` declaration order. */
+export declare const RECOGNIZED_TEMPLATES: readonly ["marketing-site-free", "marketing-site", "saas-product"];
+export type TemplateName = (typeof RECOGNIZED_TEMPLATES)[number];

package/dist/template-names.js

@@ -0,0 +1,44 @@
+/**
+ * The `--template` flag's vocabulary, and nothing else.
+ *
+ * WHY THIS FILE EXISTS, measured rather than assumed. Spec 5481 § 3 DD1 has
+ * `parse-args.ts` validate `--template` against `TEMPLATE_MANIFESTS` through a
+ * runtime import, on the grounds that the registry's own dependency on
+ * `parse-args.ts` (for `ModuleName`) is `import type` and so erases at
+ * compile. That is true of the DIRECT edge and false of the graph:
+ * `template-manifest.ts` imports `lib/module-tier.js` and
+ * `module-architecture.js` as RUNTIME values, and BOTH of those import
+ * `RECOGNIZED_MODULES` — a runtime value — back from `parse-args.ts`.
+ * `module-tier.ts` then reads it at MODULE SCOPE to derive `PAID_MODULES`.
+ * So `parse-args.ts` importing the registry closes a runtime cycle whose
+ * first read lands in the temporal dead zone:
+ *
+ *     ReferenceError: Cannot access 'RECOGNIZED_MODULES' before initialization
+ *
+ * — reproduced against the built `dist/` while implementing this unit, not
+ * theorised. `surfaces.ts`'s header warns about exactly this relationship
+ * ("Deliberately imports nothing from `parse-args.ts`: that module imports
+ * THIS one … so a back-import would close a cycle"), and `surfaces.ts` is the
+ * precedent this file follows: the flag's vocabulary lives in a module the
+ * parser can import because it imports nothing at all.
+ *
+ * THE REGISTRY IS STILL `template-manifest.ts` (parent record D2). This file
+ * declares NAMES; that one declares what a template IS — `requires`, the
+ * roster, the `installMap`, the free-vs-paid derivation — and it stays the
+ * single place a template is defined. The two cannot drift: the names here
+ * are asserted equal to `Object.keys(TEMPLATE_MANIFESTS)` by
+ * `__tests__/template-scaffold.test.ts`, so adding a template without listing
+ * it here (or the reverse) fails the suite rather than shipping a flag that
+ * accepts a name the registry does not know.
+ *
+ * Rejected: lazifying `module-tier.ts`'s `PAID_MODULES` to break the cycle at
+ * its source. It is the correct structural fix and it is not this unit's to
+ * make — `module-tier.ts` is a READ row in spec 5481 § 4, and `PAID_MODULES`
+ * is consumed as a plain array across the package.
+ */
+/** The declared site templates, in `TEMPLATE_MANIFESTS` declaration order. */
+export const RECOGNIZED_TEMPLATES = [
+    "marketing-site-free",
+    "marketing-site",
+    "saas-product",
+];

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "create-ailk",
-  "version": "0.3.0",
+  "version": "0.4.0",
   "description": "Scaffolder for AI Launch Kit — `pnpm create ailk@latest <dir>` produces a starter repo consuming @working-theory/* from npm (per ADR 0007).",
   "type": "module",
   "main": "./dist/index.js",
@@ -11,6 +11,7 @@
   "files": [
     "dist",
     "templates",
+    "site-templates",
     "component-catalog.md",
     "README.md",
     "LICENSE"

package/site-templates/marketing-site-free/ailk-template.json

@@ -0,0 +1,8 @@
+{
+  "name": "marketing-site-free",
+  "requires": ["marketing"],
+  "installMap": {
+    "provenance.json": ".ailk-template.json"
+  },
+  "postInstall": "Template marketing-site-free installed. Its seed content for /pricing, /privacy and /terms is in content/en/ - replace the placeholder copy before you launch."
+}

package/site-templates/marketing-site-free/content/en/Pricing/pricing.mdx

@@ -0,0 +1,103 @@
+---
+type: "Pricing"
+slug: "pricing"
+title: "Pricing"
+description: "Replace this with one sentence naming how Your Company charges — the unit, the range, and what moves the number. It is the description answer engines quote."
+sections:
+  [
+    {
+      "id": "hero",
+      "type": "hero",
+      "data":
+        {
+          "headline": "Pricing",
+          "subheadline": "Replace this with the one thing a buyer most needs to know about what they will pay.",
+        },
+    },
+    {
+      "id": "plans",
+      "type": "pricing",
+      "data":
+        {
+          "headline": "Replace these plans with your own",
+          "description": "Three placeholder plans. Rename them, set real prices, and list what each one actually includes. Delete any plan you do not offer — an empty tier is worse than one fewer.",
+          "plans":
+            [
+              {
+                "name": "Plan one",
+                "description": "Replace this with who this plan is for.",
+                "price": { "custom": "Your price" },
+                "features":
+                  [
+                    "Replace this line with something the plan includes.",
+                    "One line per included thing.",
+                    "Name the limit, not just the feature.",
+                  ],
+                "cta": { "label": "Get in touch", "href": "/contact" },
+              },
+              {
+                "name": "Plan two",
+                "description": "Replace this with who this plan is for.",
+                "price": { "custom": "Your price" },
+                "features":
+                  [
+                    "Everything in plan one.",
+                    "Replace this line with what the step up buys.",
+                    "Say the number when there is one.",
+                  ],
+                "cta": { "label": "Get in touch", "href": "/contact" },
+                "highlighted": true,
+              },
+              {
+                "name": "Plan three",
+                "description": "Replace this with who this plan is for.",
+                "price": { "custom": "Let's talk" },
+                "features":
+                  [
+                    "Everything in plan two.",
+                    "Replace this line with the work you quote per engagement.",
+                    "Scope, not adjectives.",
+                  ],
+                "cta":
+                  {
+                    "label": "Book a call",
+                    "href": "/contact",
+                    "variant": "outline",
+                  },
+              },
+            ],
+        },
+    },
+    {
+      "id": "pricing-faq",
+      "type": "faq",
+      "data":
+        {
+          "headline": "Pricing questions",
+          "items":
+            [
+              {
+                "question": "Replace this with the pricing question you are actually asked.",
+                "answer": "Answer it in the first sentence, with the number in it. A pricing answer that opens with context is the one buyers stop reading.",
+              },
+              {
+                "question": "What happens when the scope changes?",
+                "answer": "Replace this with how you handle a change in scope — who decides, how it is priced, and when the new price starts. Say it plainly here and you will not have to say it awkwardly later.",
+              },
+            ],
+        },
+    },
+    {
+      "id": "cta",
+      "type": "cta",
+      "data":
+        {
+          "headline": "Not sure which plan fits?",
+          "description": "Replace this with an invitation to the conversation you actually want to have.",
+          "primaryCta": { "label": "Get in touch", "href": "/contact" },
+        },
+    },
+  ]
+---
+
+{/* Rendered from frontmatter `sections[]`. Seed content — replace the plan names, prices and features above with your own before you launch. */}

package/site-templates/marketing-site-free/content/en/PrivacyPage/privacy.mdx

@@ -0,0 +1,79 @@
+---
+type: "PrivacyPage"
+slug: "privacy"
+title: "Privacy Policy"
+description: "Placeholder privacy policy for Your Company. Replace every section with a policy that describes what your site actually collects before you launch."
+sections:
+  [
+    {
+      "id": "privacy-document",
+      "type": "document-chassis",
+      "data":
+        {
+          "eyebrow": "PLACEHOLDER — REPLACE BEFORE LAUNCH",
+          "headline": "Privacy Policy",
+          "backHref": "/",
+          "backLabel": "Back home",
+          "navGroupLabel": "Contents",
+          "sections":
+            [
+              {
+                "id": "placeholder-notice",
+                "heading": "This is placeholder text",
+                "blocks":
+                  [
+                    {
+                      "kind": "paragraph",
+                      "text": "This page is starter content that shipped with your site. It is not a privacy policy, it makes no commitment on behalf of Your Company, and it is not legal advice. Replace every section below with a policy that describes what your site actually collects, and have someone qualified read it before you publish.",
+                    },
+                    {
+                      "kind": "paragraph",
+                      "text": "Until you do, leave this notice in place so nobody mistakes the page for a finished policy.",
+                    },
+                  ],
+              },
+              {
+                "id": "what-to-write-here",
+                "heading": "What belongs on this page",
+                "blocks":
+                  [
+                    {
+                      "kind": "paragraph",
+                      "text": "A privacy policy answers a short list of questions. Write each answer in plain language, and write it about the site you actually run — not about the site you plan to run.",
+                    },
+                    {
+                      "kind": "list",
+                      "listStyle": "number",
+                      "items":
+                        [
+                          "Who operates this site, and how to reach them.",
+                          "What the site collects — forms you publish, server logs, analytics.",
+                          "Why you collect each thing, and what you do with it.",
+                          "Which third parties process it on your behalf.",
+                          "How long you keep it, and how someone asks for a copy or a deletion.",
+                        ],
+                    },
+                  ],
+              },
+              {
+                "id": "contact",
+                "heading": "How to reach us",
+                "blocks":
+                  [
+                    {
+                      "kind": "paragraph",
+                      "text": "Replace this with the address you actually monitor — for example privacy@example.com — and say how quickly someone can expect a reply. A published address nobody watches is worse than no address.",
+                    },
+                    {
+                      "kind": "paragraph",
+                      "text": "Replace this with the date you last updated the policy, and say how you will announce future changes.",
+                    },
+                  ],
+              },
+            ],
+        },
+    },
+  ]
+---
+
+{/* Rendered from frontmatter `sections[]`. Placeholder seed content — this is not a privacy policy and not legal advice. Replace every section before you launch. */}