create-ailk 0.7.0 → 0.9.0

package/site-templates/minimalism-site/DESIGN.md

@@ -1,162 +0,0 @@
----
-name: Minimalism
-description: The minimalism design — the same black-on-white foundation, presented as a nine-slide scroll-snap deck home with a mark-only navigation and a centred footer.
-colors:
-  bg: "#ffffff"
-  fg: "#000000"
-  surface: "#ffffff"
-  surface-secondary: "#ffffff"
-  border: "#000000"
-  text-muted: "#333333"
-  brand: "#000000"
-  fg-on-brand: "#ffffff"
-  accent: "#000000"
-  bg-dark: "#000000"
-  fg-dark: "#ffffff"
-  border-dark: "#ffffff"
-  brand-dark: "#ffffff"
-typography:
-  display:
-    fontFamily: "system-ui, -apple-system, Segoe UI, Roboto, Helvetica Neue, sans-serif"
-    fontSize: "3.5rem"
-    fontWeight: 700
-    lineHeight: 1.1
-    letterSpacing: "normal"
-  heading-section:
-    fontFamily: "system-ui, -apple-system, Segoe UI, Roboto, Helvetica Neue, sans-serif"
-    fontSize: "3rem"
-    fontWeight: 700
-    lineHeight: 1.1
-    letterSpacing: "normal"
-  heading-item:
-    fontSize: "2rem"
-    fontWeight: 700
-    lineHeight: 1.375
-    letterSpacing: "normal"
-  body:
-    fontFamily: "system-ui, -apple-system, Segoe UI, Roboto, Helvetica Neue, sans-serif"
-    fontSize: "1.125rem"
-    fontWeight: 400
-    lineHeight: 1.5
-  eyebrow:
-    fontSize: "0.875rem"
-    fontWeight: 600
-    lineHeight: 1.4
-    letterSpacing: "0.05em"
-rounded:
-  button: "0.5rem"
-  card: "0.75rem"
-spacing:
-  section: "7rem"
-  section-mobile: "4rem"
-  card: "1.5rem"
-  grid: "1.5rem"
-  container: "1280px"
-  measure: "36rem"
----
-
-<!--
-  Source template: minimalism-site
-  Design: minimalism
-  Version: create-ailk {{CREATE_AILK_VERSION}}
-
-  This is the `minimalism` design's DESIGN.md. Its one authored source is
-  create-ailk's site-templates/designs/minimalism/DESIGN.md; every template on
-  this design ships a copy of it that differs only in the "Source template"
-  line above, and a template installed with `--template <name>` replaces the
-  base scaffold's DESIGN.md with its own. The impeccable design skill reads
-  it at the start of every design session, so an agent building a new page
-  stays on-system.
-  Edit the canonical file, never a copy — a test holds every copy to it.
-
-  The tokens above describe what the site RENDERS today. Colours come from
-  content/_site.mdx (`theme.colors`); type, radius and spacing are platform
-  defaults a site cannot override yet — see "Where this is heading" below.
--->
-
-# Minimalism
-
-## Overview
-
-The minimalism design is the standard foundation — the same black-on-white wireframe, the same type and the same components — presented as a deck. The home page is a nine-slide deck that snaps one slide per scroll, so the site reads like a presentation before it reads like a website; the rest of the site is quiet and document-like. Its character comes from structure, not a palette: it carries no theme of its own.
-
-Every page is composed from the AI Launch Kit component library (`@working-theory/ui`). Nothing is hand-built: a page is a list of registered sections, each with a bounded set of variants.
-
-## Colors
-
-### Primary
-
-**Black** (`brand` `#000000`) fills the primary button; its label is white. The secondary button is white with a black hairline and black label.
-
-### Neutral
-
-Pure white ground (`bg` `#ffffff`), pure black ink for headings (`fg` `#000000`), and near-black `#333333` for body copy — well above AA on white. **Borders are black** (`#000000`): card outlines, the rule under the navigation, the rules between sections and the rule above the footer are all 1px black lines. Cards are white, not tinted (`surface-secondary` is white too). There is no accent colour — `accent` is black.
-
-Dark mode inverts: black ground, white ink, white rules, white primary button with black label.
-
-### Named Rules
-
-- **Rules, not fills.** A container is drawn with a black hairline on the white ground. Grey fills are reserved for image placeholders.
-
-## Typography
-
-System sans throughout; no web font.
-
-### Hierarchy
-
-| Role            | Size     | Weight | Notes                                                                                 |
-| --------------- | -------- | ------ | ------------------------------------------------------------------------------------- |
-| Hero headline   | 3.5rem   | 700    | Normal tracking, line-height 1.1; 2.5rem below 1024px                                 |
-| Section heading | 3rem     | 700    | Normal tracking, line-height 1.1; 2.25rem below 1024px, always under the hero         |
-| Item heading    | 2rem     | 700    | Card, feature and step titles; 1.5rem below 1024px                                    |
-| Body            | 1.125rem | 400    | `#333333`, line-height 1.5; section copy capped at 36rem (about 70 characters a line) |
-| Section label   | 0.875rem | 600    | Uppercase, +0.05em tracking today — the small label above a section heading           |
-
-Measured from the rendered scaffold (1440px and 390px wide), not transcribed from tokens. Bold headings at normal tracking follow the foundation's pinned direction (#6493).
-
-The small label above a section heading is **kept** as part of this foundation's voice (operator-disposed 2026-09-22) and is headed toward the treatment below.
-
-## Layout
-
-Home is the `deck` layout: nine full-viewport slides with scroll-snap. The navigation is `mark-only`, the footer is `centered`, and there is no announcement banner (`layout.home: deck`, `layout.nav: mark-only`, `layout.footer: centered` — the design's own knobs, which any template on this design gets without declaring a `layout`). Every page this site carries is listed in its roster of record, `.ailk-site-manifest.json` at the site root. Shared foundation: a 1280px container, sections at 7rem (4rem below 1024px), card grids at 1.5rem, breakpoints 320 / 768 / 1024 / 1440.
-
-## Shapes
-
-Square corners everywhere (`theme.corners: square`) — buttons, cards, the auth card, image placeholders; the tokens above are the base foundation's defaults a site overrides.
-
-## Components
-
-### Buttons
-
-Primary: black fill, white label, 0.5rem corners. Secondary: transparent with a black 1px outline and black label. Both are the library `Button`.
-
-### Cards / Containers
-
-White panels with a black 1px outline, 0.75rem corners, `card` (1.5rem) padding. The one exception today: the "how it works" steps render as dark filled cards (see below).
-
-### Navigation
-
-Mark-only: the logomark alone, top left. No link row and no buttons in the header.
-
-## Where this is heading
-
-The foundation's pinned direction is the pacing of a classic wireframe marketing kit — `standardissue.webflow.io` is the reference for rhythm, type scale, spacing density and section pacing only; no image, copy or code is taken from it. The four traits this section used to list as blocked now ship as settings, so the rendered site matches the reference:
-
-| Trait                                                  | How it is set                                                                                     |
-| ------------------------------------------------------ | ------------------------------------------------------------------------------------------------- |
-| Square corners on buttons, cards and inputs            | `theme.corners: square` in `_site.mdx`                                                            |
-| Section label in sentence case, bold, no tracking      | `theme.eyebrowCase: sentence`                                                                     |
-| Solid grey image placeholders, no outline              | `theme.placeholders: fill`                                                                        |
-| Bare check and cross marks, no circle badge            | `theme.checkmarks: plain`                                                                         |
-| Plain, uncarded feature and step items                 | per section: `itemStyle: plain`, and `variant: steps` for an image beside a numbered list         |
-| A left hero whose headline wraps at half the container | `measure: narrow` on the hero (pricing); `gapBelow: tight` where a list follows the hero directly |
-| A three-up post grid on the blog index                 | `blog-list` `variant: grid` (cover · date · read time · title · excerpt · Read more)              |
-| A plans section that leads its page                    | drop the hero; the pricing section owns the `<h1>` (`ownsPageTitle`)                              |
-
-## Do's and Don'ts
-
-- **Do** keep every page built from registered sections. If a section you need does not exist, request it rather than writing one-off markup.
-- **Do** change colours in `content/_site.mdx` `theme.colors`; they reach every section.
-- **Don't** add a colour accent. The foundation's one idea is black on white; a brand pass adds colour deliberately, through the theme.
-- **Don't** replace a black rule with a shadow or a grey fill.
-- **Don't** hard-code the "heading toward" values above into a page. They arrive through the platform, or not at all.

package/site-templates/minimalism-site/TEMPLATE-MANIFEST.md

@@ -1,470 +0,0 @@
-# Template manifest — `minimalism-site`
-
-> The second Pro template (#5589) — a reports-first site whose home is a **nine-slide scroll-snap deck**, shaped after the reference captured in `docs/research/bondcap-capture/`. Structure and design are the reference; **the copy is not** — every line here is placeholder English of the same shape and length. Generated file: the regions between `<!-- generated:begin <id> -->` and `<!-- generated:end -->` are produced by `scripts/build-template-manifest.mjs --template minimalism-site` from the composed layer stack (this tree → its required modules → `_base` → the always-copied overlay), each roster row's MDX `sections[]`, and `component-catalog.json`. Everything outside the markers is written by hand.
-
-| Field                  | Value                                                                                                                                                                            |
-| ---------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| Template               | `minimalism-site`                                                                                                                                                                |
-| Level                  | Pro (derived from `requires` — `scheduling` and `signal-collectors` are paid; never declared)                                                                                    |
-| `requires`             | `[marketing, scheduling, signal-collectors]` — **no `docs-blog`**, which is what makes this a sibling of `marketing-site` rather than `marketing-site` plus a module (#5618 D2)  |
-| `extends`              | `_base` — lineage only, never level                                                                                                                                              |
-| Delivery               | licence-checked module bundle (#5441); never in the Free tarball                                                                                                                 |
-| Sample content posture | every sample report, service and flow in the demo is **public** and **placeholder**                                                                                              |
-| Reference              | `docs/research/bondcap-capture/{home.behavior.md,home.snapshot.yml,repro/}` — panel shapes and the rescued section reproduction. No reference copy and no reference asset ships. |
-
-## 1. Chrome
-
-This template's chrome is the `minimalism` design's (#6638), not a `layout` block of its own; it was the first non-default chrome (#5612). The deck is the reason: a nine-panel scroll-snap home with a revealed brand mark has no room for a nav row, an announcement bar or a four-column footer.
-
-| Piece               | Value                                                                                                                                                                                                         |
-| ------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| Nav                 | `mark-only` — **no nav items render**. The revealed brand mark plus the right-hand controls are the only header chrome. Every page a reader reaches, they reach from a slide action or the footer bottom bar. |
-| Footer              | `centered` — the slide-9 bottom bar: Privacy · Terms · FAQ, the social row, the theme toggle and the locale switcher.                                                                                         |
-| Announcement banner | off. The cookie-consent banner is unaffected — it is not an announcement.                                                                                                                                     |
-| Home                | `deck` — the locale-root route mounts `MarketingShell` with `snap="mandatory"` + `deckHero` (#5612 D3 / #5426 D7). Every other route renders normally.                                                        |
-
-### Layout knobs (#5612)
-
-The `minimalism` design's knobs (#6638) — the template declares no `layout` block of its own; `design: minimalism` supplies these through `DESIGN_LAYOUTS`, resolved with `resolveSiteChrome(layout, design)`, defaults filled. Any shape that names this design gets the same chrome.
-
-<!-- generated:begin layout -->
-
-| Knob                 | Value       |
-| -------------------- | ----------- |
-| `nav`                | `mark-only` |
-| `footer`             | `centered`  |
-| `announcementBanner` | `false`     |
-| `home`               | `deck`      |
-
-<!-- generated:end -->
-
-### Theme (locked)
-
-The template's `theme:` block as `_site.mdx` declares it — the shape knobs and the colour overlay. Generated, so a change to a locked template's look is a red `manifest:check`, not a silent drift (starter-template contract R3.5).
-
-<!-- generated:begin theme -->
-
-| Setting                  | Value      |
-| ------------------------ | ---------- |
-| `corners`                | `square`   |
-| `eyebrowCase`            | `sentence` |
-| `placeholders`           | `fill`     |
-| `checkmarks`             | `plain`    |
-| `colors.light.bg`        | `#ffffff`  |
-| `colors.light.bgMuted`   | `#ffffff`  |
-| `colors.light.surface`   | `#ffffff`  |
-| `colors.light.border`    | `#000000`  |
-| `colors.light.text`      | `#000000`  |
-| `colors.light.textMuted` | `#333333`  |
-| `colors.light.primary`   | `#000000`  |
-| `colors.light.primaryFg` | `#ffffff`  |
-| `colors.light.accent`    | `#000000`  |
-| `colors.dark.bg`         | `#000000`  |
-| `colors.dark.bgMuted`    | `#000000`  |
-| `colors.dark.surface`    | `#000000`  |
-| `colors.dark.border`     | `#ffffff`  |
-| `colors.dark.text`       | `#ffffff`  |
-| `colors.dark.textMuted`  | `#cccccc`  |
-| `colors.dark.primary`    | `#ffffff`  |
-| `colors.dark.primaryFg`  | `#000000`  |
-| `colors.dark.accent`     | `#ffffff`  |
-
-<!-- generated:end -->
-
-## 2. The home deck — nine slides
-
-`layout.home: "deck"` makes every direct section child of `home.mdx` one full-viewport snap target, in order. The mark is hidden on slide 1 (the deck-hero landing state) and revealed from slide 2 on.
-
-| #   | Slide             | Section                                                        | Ground                   | Action                                                                                                    |
-| --- | ----------------- | -------------------------------------------------------------- | ------------------------ | --------------------------------------------------------------------------------------------------------- |
-| 1   | Landing           | `hero` (`backdrop`)                                            | gradient band + backdrop | `{Primary CTA} →` → `/reports`, centered; 44px scroll cue. _No mark — but see the Nav-wiring note below._ |
-| 2   | Tagline           | `content-block` (`align: center`, `fill: viewport`)            | light                    | — (_the mark reveals here once #5697 lands_)                                                              |
-| 3   | Our community     | `logoCloud` (`actions`)                                        | light                    | `Refer someone →` → `/referral`, bottom-centered at 44px                                                  |
-| 4   | Reports headline  | `content-block` (`align: center`, `fill: viewport`)            | light                    | —                                                                                                         |
-| 5   | Special reports   | `reports-list` (`list`, `tone: on-dark`)                       | dark (`gradient-dark`)   | four dated titles → `/reports/<slug>`                                                                     |
-| 6   | Favorites         | `reports-list` (`list`, `tone: on-dark`)                       | dark (`gradient-dark`)   | year-only titles → `/reports/<slug>`                                                                      |
-| 7   | Services headline | `content-block` (`align: center`, `fill: viewport`)            | light                    | `Hire me →` → `/meet`                                                                                     |
-| 8   | Partners          | `team` (`with-large-images`, `hoverReveal`, `phoneColumns: 2`) | light                    | `About us →` → `/about`, bottom-centered at 44px                                                          |
-| 9   | Closing           | `cta` (`minimal`)                                              | light                    | `Contact me →` → `/contact`, centered                                                                     |
-
-### How the deck honours the site principle
-
-Sam's site principle for this template — _every slide's action sits at the bottom, centered, at 44px or larger; grids are 2-up on a phone_ — is held by bounded section props, never by a `className` override or hand-rolled markup in a template (`.claude/rules/frontend.md` § Chrome Composes Blocks). #5691 landed the seven the deck was missing and this tree sets all seven; the composition of every slide is unchanged from the table above.
-
-| Prop                                        | Owner                                    | Slides that set it | What it does here                                                                                                                                                                                      |
-| ------------------------------------------- | ---------------------------------------- | ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
-| `hero.backdrop`                             | `packages/ui/src/sections/Hero.tsx`      | 1                  | paints `assets/hero-backdrop.svg` (installed at `/hero-backdrop.svg`) full-bleed behind the copy. A distinct slot from `image`, which counts as a stacked reveal — so the 44px scroll cue survives it. |
-| `content-block.align`                       | `.../ContentBlock.tsx`                   | 2, 4, 7            | centers the headline cluster, the body and the CTA row, through `SectionHeader`'s own `align` prop                                                                                                     |
-| `content-block.fill`                        | `.../ContentBlock.tsx`                   | 2, 4, 7            | the copy centers in the middle of the full-viewport snap panel instead of sitting at its top                                                                                                           |
-| `logoCloud.actions`                         | `.../LogoCloud.tsx`                      | 3                  | one bottom-centered action at the 44px floor beneath the strip (the #5622 `stair-steps` footer placement)                                                                                              |
-| `team.actions`                              | `.../Team.tsx`                           | 8                  | the same row beneath the member wall                                                                                                                                                                   |
-| `'gradient-dark'` on `SectionSurfaceSchema` | `packages/validation/…/page-sections.ts` | 5, 6               | the dark ground `tone: "on-dark"` (#5562, shipped **for** this template) was always meant to sit on. `SectionFrameBand` has carried the band itself since 2026-08-29.                                  |
-| `CardGrid.phoneColumns`                     | `packages/ui/src/panels/CardGrid.tsx`    | 8                  | the six-tile wall is two-up at 390 rather than overflowing the snap panel one tile at a time                                                                                                           |
-
-Two notes on the last row. `CardGrid`'s 1-up-below-`md` ramp stays the system-wide default — the recorded #2803 fix, since an `sm` step made every phone 2-up-cramped — and `phoneColumns: 2` is the opt-in Sam disposed on 2026-09-16 for this deck and the client decks built from it; nothing else in the repo sets it. And slide 8 is the only deck slide that reaches `CardGrid` at all: slide 3's logo strip is a reflowing flex row with no column count, and `reports-list`'s `list` variant has no grid — so one knob on one slide satisfies the whole principle.
-
-### The Nav wiring — #5697, and not this template's to fix
-
-The deck's brand-mark story is the other half of `layout.home: "deck"`, and it is not wired. `apps/web/app/[locale]/layout.tsx` forwards `snap` and `deckHero` to `MarketingShell` but forwards neither `sticky` nor `deckMorph` to `Nav`, so today the lockup is pushed out of view by the first snap and the morph hooks the #5426 CSS keys off are never in the document. A template declares layout; it cannot forward a prop in an app's layout file. Filed as **#5697**, with both states photographed (`home-*` vs `home-wired-*` under `docs/design-evidence/5589/`).
-
-One thing #5697 also settles: #5589's text says slide 1 shows "no visible logo", while what #5426 D4 ships is a cross-fade — wordmark on the landing slide, mark from slide 2 on. The mark's absence from slide 1 holds either way.
-
-## 3. Pages
-
-One `page=<route>` region per roster row, generated from the seed file the composed layer stack lands for that route.
-
-`/`:
-
-<!-- generated:begin page=/ -->
-
-| #   | Section                                                            | Component      | Copy (first line)                                                      |
-| --- | ------------------------------------------------------------------ | -------------- | ---------------------------------------------------------------------- |
-| 1   | `hero` (centered · surface=gradient-brand · fill=viewport · 1 CTA) | `Hero`         | Your Company                                                           |
-| 2   | `content-block` (narrow · align=center · fill=viewport)            | `ContentBlock` | A working partnership with the teams building {what your market needs… |
-| 3   | `logoCloud` (layout=grid · logos ×3 · 1 CTA)                       | `LogoCloud`    | Our community                                                          |
-| 4   | `content-block` (narrow · align=center · fill=viewport)            | `ContentBlock` | Research on {your field}, and on where the next decade of it is going  |
-| 5   | `reports-list` (list · surface=gradient-dark · tone=on-dark)       | `ReportsList`  | Special reports                                                        |
-| 6   | `reports-list` (list · surface=gradient-dark · tone=on-dark)       | `ReportsList`  | Favorites                                                              |
-| 7   | `content-block` (narrow · align=center · fill=viewport · 1 CTA)    | `ContentBlock` | Trusted work for the people who carry {the outcome you deliver}        |
-| 8   | `team` (with-large-images · members ×6 · 1 CTA)                    | `Team`         | Partners                                                               |
-| 9   | `cta` (minimal · 1 CTA)                                            | `CTA`          | Your Company                                                           |
-
-<!-- generated:end -->
-
-`/reports`:
-
-<!-- generated:begin page=/reports -->
-
-| #   | Section                               | Component     | Copy (first line)                           |
-| --- | ------------------------------------- | ------------- | ------------------------------------------- |
-| 1   | `hero` (centered · eyebrow "Reports") | `Hero`        | Research on {your field}, published in full |
-| 2   | `reports-list` (cards)                | `ReportsList` |                                             |
-| 3   | `cta` (minimal · 1 CTA)               | `CTA`         | Want the next one as it lands?              |
-
-<!-- generated:end -->
-
-`/about`:
-
-<!-- generated:begin page=/about -->
-
-| #   | Section                                    | Component      | Copy (first line)                                                      |
-| --- | ------------------------------------------ | -------------- | ---------------------------------------------------------------------- |
-| 1   | `content-block` (narrow · eyebrow "About") | `ContentBlock` | We work with a small number of {the people you serve}, for a long time |
-| 2   | `team` (with-large-images · members ×6)    | `Team`         | Partners                                                               |
-| 3   | `cta` (minimal · 2 CTAs)                   | `CTA`          | Work with us                                                           |
-
-<!-- generated:end -->
-
-`/services`:
-
-<!-- generated:begin page=/services -->
-
-| #   | Section                                | Component | Copy (first line)           |
-| --- | -------------------------------------- | --------- | --------------------------- |
-| 1   | `hero` (centered · eyebrow "Services") | `Hero`    | Three ways to work together |
-| 2   | `items` (columns=3 · items ×3)         | `Items`   | Engagements                 |
-| 3   | `cta` (minimal · 1 CTA)                | `CTA`     | Not sure which one?         |
-
-<!-- generated:end -->
-
-`/services/[slug]`:
-
-<!-- generated:begin page=/services/[slug] -->
-
-_Detail route over `content/en/Service/` — 3 seed pages: `first-engagement.mdx`, `second-engagement.mdx`, `third-engagement.mdx`._
-<!-- generated:end -->
-
-`/contact`:
-
-<!-- generated:begin page=/contact -->
-
-| #   | Section                               | Component | Copy (first line)             |
-| --- | ------------------------------------- | --------- | ----------------------------- |
-| 1   | `hero` (centered · eyebrow "Contact") | `Hero`    | Say what you are trying to do |
-| 2   | `cta` (minimal · 1 CTA)               | `CTA`     | Would a call be faster?       |
-
-<!-- generated:end -->
-
-`/referral`:
-
-<!-- generated:begin page=/referral -->
-
-| #   | Section                                                        | Component    | Copy (first line)                        |
-| --- | -------------------------------------------------------------- | ------------ | ---------------------------------------- |
-| 1   | `hero` (centered · eyebrow "Referrals" · checklist ×3 · 1 CTA) | `Hero`       | Know someone who should be on this list? |
-| 2   | `stair-steps` (tiles ×3)                                       | `StairSteps` | Three steps, about a minute              |
-| 3   | `cta` (minimal · 1 CTA)                                        | `CTA`        | Make an introduction                     |
-
-<!-- generated:end -->
-
-`/faq`:
-
-<!-- generated:begin page=/faq -->
-
-| #   | Section                                                       | Component | Copy (first line)      |
-| --- | ------------------------------------------------------------- | --------- | ---------------------- |
-| 1   | `faq` (centered · items ×5 · supportLink · initialOpen first) | `FAQ`     | Questions              |
-| 2   | `cta` (minimal · 1 CTA)                                       | `CTA`     | Still have a question? |
-
-<!-- generated:end -->
-
-`/glossary`, `/newsletter` (base-layer seeds every starter carries, #6658 D5):
-
-<!-- generated:begin page=/glossary -->
-
-| #   | Section                             | Component       | Copy (first line)                            |
-| --- | ----------------------------------- | --------------- | -------------------------------------------- |
-| 1   | `hero` (eyebrow "Glossary" · 1 CTA) | `Hero`          | {Glossary: the terms your customers look up} |
-| 2   | `glossary-index` (columns)          | `GlossaryIndex` | {Terms, A to Z}                              |
-
-<!-- generated:end -->
-
-<!-- generated:begin page=/newsletter -->
-
-| #   | Section                               | Component    | Copy (first line)                                |
-| --- | ------------------------------------- | ------------ | ------------------------------------------------ |
-| 1   | `hero` (eyebrow "Newsletter" · 1 CTA) | `Hero`       | {Newsletter: what subscribers get and how often} |
-| 2   | `newsletter`                          | `Newsletter` | Subscribe                                        |
-| 3   | `faq` (expanded · items ×3)           | `FAQ`        | FAQs                                             |
-
-<!-- generated:end -->
-
-`/book-a-call` (this template's own override of the base seed — the call to action opens the `/meet` booker the scheduling module supplies, not `/contact`):
-
-<!-- generated:begin page=/book-a-call -->
-
-| #   | Section                                | Component | Copy (first line)                          |
-| --- | -------------------------------------- | --------- | ------------------------------------------ |
-| 1   | `hero` (eyebrow "Book a call" · 1 CTA) | `Hero`    | {Book a call: what a visitor gets from it} |
-| 2   | `items` (columns=3 · items ×3)         | `Items`   | What happens on the call?                  |
-
-<!-- generated:end -->
-
-`/privacy`:
-
-<!-- generated:begin page=/privacy -->
-
-| #   | Section                             | Component         | Copy (first line) |
-| --- | ----------------------------------- | ----------------- | ----------------- |
-| 1   | `document-chassis` (layout=article) | `DocumentChassis` | Privacy Policy    |
-
-<!-- generated:end -->
-
-`/terms`:
-
-<!-- generated:begin page=/terms -->
-
-| #   | Section                             | Component         | Copy (first line) |
-| --- | ----------------------------------- | ----------------- | ----------------- |
-| 1   | `document-chassis` (layout=article) | `DocumentChassis` | Terms of Service  |
-
-<!-- generated:end -->
-
-`/purchase-policy`:
-
-<!-- generated:begin page=/purchase-policy -->
-
-| #   | Section                             | Component         | Copy (first line) |
-| --- | ----------------------------------- | ----------------- | ----------------- |
-| 1   | `document-chassis` (layout=article) | `DocumentChassis` | Purchase Policy   |
-
-<!-- generated:end -->
-
-`/meet`:
-
-<!-- generated:begin page=/meet -->
-
-_Code route — no content, no sections._
-<!-- generated:end -->
-
-`/meet/[slug]`:
-
-<!-- generated:begin page=/meet/[slug] -->
-
-_Code route — no content, no sections._
-<!-- generated:end -->
-
-`/meet/confirmed`:
-
-<!-- generated:begin page=/meet/confirmed -->
-
-_Code route — no content, no sections._
-<!-- generated:end -->
-
-`/appointments`:
-
-<!-- generated:begin page=/appointments -->
-
-_Code route — no content, no sections._
-<!-- generated:end -->
-
-`/flows/[slug]`:
-
-<!-- generated:begin page=/flows/[slug] -->
-
-_Code route — no content, no sections._
-<!-- generated:end -->
-
-`/flows/[slug]/start`:
-
-<!-- generated:begin page=/flows/[slug]/start -->
-
-_Code route — no content, no sections._
-<!-- generated:end -->
-
-`/flows/[slug]/results/[payload]`:
-
-<!-- generated:begin page=/flows/[slug]/results/[payload] -->
-
-_Code route — no content, no sections._
-<!-- generated:end -->
-
-`/reports/[slug]`:
-
-<!-- generated:begin page=/reports/[slug] -->
-
-_Detail route over `content/en/ReportPage/` — 4 seed pages: `annual-letter-2024.mdx`, `field-notes-2023.mdx`, `platform-shift-2025.mdx`, `state-of-the-market-2026.mdx`._
-<!-- generated:end -->
-
-The signal-collectors bundle's sample pages — the project listing, two projects and three thank-you pages — are this template's own roster rows (#6646), so the roster lists every page the scaffold installs.
-
-<!-- generated:begin page=/projects -->
-
-| #   | Section                        | Component | Copy (first line)          |
-| --- | ------------------------------ | --------- | -------------------------- |
-| 1   | `hero` (centered)              | `Hero`    | Projects                   |
-| 2   | `items` (columns=2 · items ×2) | `Items`   | Selected engagements       |
-| 3   | `cta` (2 CTAs)                 | `CTA`     | Have a project like these? |
-
-<!-- generated:end -->
-
-<!-- generated:begin page=/projects/[slug] -->
-
-_Detail route over `content/en/Project/` — 2 seed pages: `fit-check-funnel.mdx`, `launch-site-in-fourteen-days.mdx`._
-<!-- generated:end -->
-
-<!-- generated:begin page=/thanks/[slug] -->
-
-_Detail route over `content/en/ThankYouPage/` — 3 seed pages: `apply.mdx`, `contact.mdx`, `newsletter.mdx`._
-<!-- generated:end -->
-
-### 3a. Deviations from the standard roster (recorded, #6638)
-
-This template is the `organization-service` shape (`shape: organization-service`) rendered in the `minimalism` design (`design: minimalism`). The standard page set for that shape (`derive-roster.py` —
-`entityType=organization · offeringType=services · primaryGoal=generate-leads · scale=global`,
-`mainEntity: Organization`, 33 rows) is the baseline; the design adds no rows of its own —
-the deck home, the mark-only nav and the centered footer are layout, not pages. What this
-roster keeps from the standard set: `HomePage`, `AboutPage`, `ContactPage`, `FAQPage`,
-`PrivacyPage`, `TermsPage`, `ServicesList`, `Service`, and — since #6658, which gives every
-starter these three whatever its shape (`docs/decisions/starter-roster-page-set.md` D4, D7) —
-`GlossaryList`, `NewsletterSignup` and `BookCall` (its `/book-a-call` seed is this template's
-own, pointing at the `/meet` booker).
-
-| Row added   | Why                                                                                                                                                                        |
-| ----------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `/reports`  | the site is reports-first: the deck's landing CTA and slides 5–6 lead here, and it indexes the `signal-collectors` reader at `/reports/<slug>` (§ 2)                       |
-| `/referral` | the referral magnet — the pitch and what a referrer gets, opening the `referral` flow (§ 6); slide 3's action leads here. Both rows are `LandingPage` slugs, not new types |
-
-| Standard row omitted                         | Why                                                                                                          |
-| -------------------------------------------- | ------------------------------------------------------------------------------------------------------------ |
-| `TeamList` · `TeamMember` (entity spine)     | the partners are one `team` slide on the deck and the `/about` page (§ 2, § 5), not a directory              |
-| `CareersList` · `JobPosting` (entity spine)  | not a hiring site; nothing to seed                                                                           |
-| `PartnersList` · `Partner` (entity spine)    | the partner/community strip is a `logoCloud` slide on the deck, not a page                                   |
-| `ProjectsList` · `Project` (offering branch) | the proof is the reports, not a project portfolio                                                            |
-| `Pricing` (offering branch)                  | engagements are booked, not priced on the page; `/pricing` is unrostered, so its seed does not install (§ 4) |
-
-The lead-generation tier (CaseStudies, Testimonials, Clients, UseCases, Events, Downloads) and
-the Resources content system (ResourcesHub, ResourceDetail, HowTo, Whitepaper) are the
-goal-driven default a site prunes; the reports stand in for them here.
-
-## 4. Roster, as the registry declares it
-
-`minimalism-site` is the one declared template that does not reuse `TEMPLATE_BASE_ROSTER`: the deck replaces the document-scroll home, and `/how-it-works`, the product page (`/software/product`), `/pricing` and `/sign-in` are not pages this site has. The roster is what the template IS, so an unrostered page has neither a route directory nor its seed: `scaffold()` installs a `_base` or overlay seed only for a row that names it (#6646), so `content/en/Pricing/pricing.mdx` does not land. The merged roster, as the registry composes it:
-
-<!-- generated:begin roster -->
-
-```
-minimalism-site:
-  requires: [marketing, scheduling, signal-collectors]
-  categories: [real-estate, technology, legal]
-  shape: organization-service
-  design: minimalism
-  roster:
-    - { route: "/",                               kind: page, content: ["content/en/HomePage/home.mdx"] }
-    - { route: "/reports",                        kind: page, content: ["content/en/LandingPage/reports.mdx"] }
-    - { route: "/about",                          kind: page, content: ["content/en/AboutPage/about.mdx"] }
-    - { route: "/services",                       kind: page, content: ["content/en/ServicesList/services.mdx"] }
-    - { route: "/services/[slug]",                kind: page, contentDir: "content/en/Service" }
-    - { route: "/contact",                        kind: page, content: ["content/en/ContactPage/contact.mdx"] }
-    - { route: "/referral",                       kind: page, content: ["content/en/LandingPage/referral.mdx"] }
-    - { route: "/faq",                            kind: page, content: ["content/en/FAQPage/faq.mdx"] }
-    - { route: "/glossary",                       kind: page, content: ["content/en/GlossaryList/glossary.mdx"] }
-    - { route: "/newsletter",                     kind: page, content: ["content/en/NewsletterSignup/newsletter.mdx"] }
-    - { route: "/book-a-call",                    kind: page, content: ["content/en/BookCall/book-call.mdx"] }
-    - { route: "/privacy",                        kind: page, content: ["content/en/PrivacyPage/privacy.mdx"] }
-    - { route: "/terms",                          kind: page, content: ["content/en/TermsPage/terms.mdx"] }
-    - { route: "/purchase-policy",                kind: page, content: ["content/en/PurchasePolicyPage/purchase-policy.mdx"] }
-    - { route: "/projects",                       kind: page, content: ["content/en/ProjectsList/projects.mdx"] }
-    - { route: "/projects/[slug]",                kind: page, contentDir: "content/en/Project" }
-    - { route: "/thanks/[slug]",                  kind: page, contentDir: "content/en/ThankYouPage" }
-    - { route: "/meet",                           kind: route }
-    - { route: "/meet/[slug]",                    kind: route }
-    - { route: "/meet/confirmed",                 kind: route }
-    - { route: "/appointments",                   kind: route }
-    - { route: "/flows/[slug]",                   kind: route }
-    - { route: "/flows/[slug]/start",             kind: route }
-    - { route: "/flows/[slug]/results/[payload]", kind: route }
-    - { route: "/reports/[slug]",                 kind: page, contentDir: "content/en/ReportPage" }
-```
-
-<!-- generated:end -->
-
-By source:
-
-```
-template:           / · /reports · /about · /services · /services/<slug> · /contact
-                    /referral · /faq · /privacy · /terms
-scheduling:         /meet · /meet/<slug> · /meet/confirmed
-signal-collectors:  /flows/<slug> · /flows/<slug>/start · /flows/<slug>/results/<payload>
-                    /reports/<slug>                                    (#5562)
-```
-
-`/reports` and `/referral` carry no `GATEABLE_SURFACES` entry and need none: both are single-segment `LandingPage` slugs served by the generic `[slug]` route (#5469 D2), the same mechanism Free's `/how-it-works` uses. The three module-less surfaces this roster enables are `privacy`, `services` and `terms`.
-
-## 5. Renaming `/about`
-
-Many sites want this page at `/partners`, `/team`, `/family` or `/company`. That is a ROUTE rename in the customer's scaffold, never a content move and never something the template does for them — `AboutPage` is a content type in the schema registry, not a URL.
-
-1. Keep `content/en/AboutPage/`.
-2. `git mv "apps/web/app/[locale]/about" "apps/web/app/[locale]/partners"`.
-3. Update the one footer label that names it (`messages/<locale>.json`).
-
-Once #5572's routes map ships in the scaffold this collapses to one row: the `/about` row's `route`, plus a `legacyRoutes` entry so the old path 301s. The `postInstall` message says the same thing to the buyer.
-
-## 6. The referral request
-
-`/referral` is the magnet — the pitch and what a referrer gets. Its bottom action opens the REQUEST, which is a `signal-collectors` flow: `flows/referral.flow.json` in this tree installs to `database/flows/referral.flow.json` and is served at `/flows/referral/start` (`InstrumentCapturePage`). One field step (name, email, who and why), then a `message` step that confirms inline.
-
-The issue named the path `/referral/request`. That path has no `ROUTES` row and no route directory, so serving it would mean shipping a `page.tsx` into every scaffold for one template's page — which a template may never do. **The lead's `source` is `flow:referral`**, not the bare `referral`: `flow-engine.ts` composes it as `` `flow:${slug}` `` for every flow, and that is not a template-level knob. Recorded on #5589 for Sam; his call supersedes.
-
-## 7. Component inventory
-
-Every component the roster rows' seed content composes today (generated):
-
-<!-- generated:begin inventory -->
-
-| Tier     | Used by this template                                                                                                                             |
-| -------- | ------------------------------------------------------------------------------------------------------------------------------------------------- |
-| Shell    | `MarketingShell`                                                                                                                                  |
-| Chrome   | `Nav`, `Footer`, `Banner` (+ `BannerConsentIsland`, `BannerDismissIsland`)                                                                        |
-| Sections | `ContentBlock`, `CTA`, `DocumentChassis`, `FAQ`, `GlossaryIndex`, `Hero`, `Items`, `LogoCloud`, `Newsletter`, `ReportsList`, `StairSteps`, `Team` |
-
-<!-- generated:end -->
-
-## 8. Known gaps this manifest depends on
-
-| Gap                                                                 | Issue      |
-| ------------------------------------------------------------------- | ---------- |
-| The deck's Nav wiring (`sticky` + `deckMorph` under `home: "deck"`) | #5697      |
-| `/about` rename as one routes-map row                               | #5572      |
-| The Pro demo host `minimalism-site.ailaunchkit.ai` — provisioning   | #5589 body |