Skip to main content
Specification & IP

AI Design Templates

SS-RP-2026-013aigenerative aispec draft
Created 2026-06-04Updated 2026-07-09
Brief

AI Design Templates — Product Brief

Idea: AI Design Templates (SS-RP-2026-013) Product: AI Platform › Generative AI Status: final Owner: Dan (Product Lead) UX source of truth: ux/README.md · runnable prototype at ux/prototype/index.html Sibling idea (guided-workflow bet, kept separate): generative-ai-chat-interface

Problem

The Visual Designer's "Edit with AI" tab today is a near-empty prompt panel. As captured in the sibling idea's brief (generative-ai-chat-interface/brief.md § Problem), this has three failure modes: most users don't know what to type (blank-page paralysis), typing is slow even for users who do, and free-text prompts don't build trust because the user can't preview what the AI will do.

Phase 1 of the AI-tab rework (the sibling) bet on a 5-step guided flow rooted in a chosen design "system." This idea — Phase 2 — takes a sharper, more shippable cut of that bet: a browsable catalog of real, generatable designs the user can pick, inspect, lightly tune, and generate, with the existing free-text generate flow still available as a subpage for power users.

The competitive context is unchanged from the sibling research: one-click "style template" tools (Neighborbrite, Garden AI) reduce friction but collapse the entire design into a single one-shot generation (research/report.md § Market Landscape). SimplyScapes' edge is structure, not raw generation horsepower.

Strategic Fit

This is the concrete first deliverable of the "out-structure, don't out-generate" AI direction. Rather than competing on who has the best from-scratch image model, SimplyScapes wins by giving users a curated, opinionated, regionally-aware catalog of design templates — each with a real plant palette — that a homeowner can pick with confidence and a pro can stand behind.

  • Priority alignment: Strong. Directly serves the AI guided-design strategy (structured templates over pure generation) and reinforces the Visual Designer as the default AI-assisted design surface.
  • Reuse of existing IP: The catalog deliberately mirrors the Plant Collections ⇄ Plants model already shipped in the Plants tab (see Data Model Notes). We are re-applying a proven, already-built relationship pattern — not inventing a new one.
  • Sequencing: Ships independently of the heavier sibling bet (the 5-step guided flow, Property Design Profile, references). Those remain in generative-ai-chat-interface and are deferred here (see Out of scope).

Scope

CEO direction, locked 2026-06-04. Pass-through exactly — do not re-expand the out-of-scope items.

In scope

  1. Design Styles — the "Edit with AI" homescreen presents a grid of Design Styles (categories): Utah Localscape, Xeriscape, Naturalistic, Fire Resilient, Cottage, Modern, Mediterranean. Each is a card with image, name, and tagline. Prototype: StylesGrid / StyleCardLarge in home.jsx; data SYSTEMS in data.jsx.

  2. AI Templates — tapping a Design Style opens its scrollable list of AI Templates (TemplateListScreen). Each template card shows image, name, and a "{N} plants" summary line. Tapping a template opens its detail (DetailScreen): hero image gallery, an editable plant palette (include-list, all plants on by default), a per-template custom-instructions field (PRO), and a Generate action. Prototype: TemplateListScreen + DetailScreen in home.jsx; data TEMPLATES + STYLE_TEMPLATES in data2.jsx.

  3. Edit History — a slide-up drawer (HistoryDrawer) showing a chat-style before→after log of edits with a per-entry restore affordance. Opened by the "Edit history" trigger (HistoryTrigger).

  4. Custom Edits — a free-text prompt input pinned to the bottom of that same drawer, opened by the "Describe a custom edit…" trigger (CustomPromptTrigger). Edit History and Custom Edits share one screen. Per CEO direction this is the existing AI-tab generate experience embedded as a subpage — it should look essentially identical to what the AI tab has today and should be treated as reusing/embedding that flow, not rebuilding it. Prototype: HistoryTrigger, CustomPromptTrigger, and HistoryDrawer in app.jsx.

Out of scope

Called out explicitly as deferred. Note them; do not build them here.

  • Style Quiz — the "Take the style + site quiz" CTA, QuizMergedSheet, QUESTIONNAIRE, and SiteAnalysis. (app.jsx, data2.jsx)
  • Edit Panel — the "Edit" action row (EDIT_ITEMS: Remove items, Add items, Change angle, Add labels, Adjust) and the RemoveDetail / AddSpaceDetail / AdjustDetail screens.
  • AI credits in the UI — the "42 credits" chip, the "1 generation · ≈ $0.04" line, and "counts against your monthly quota." Strip all credit/quota UI from the in-scope screens.
  • Template "At a glance" facts block — the maintenance / water / best-for / cost block on the template detail (Section2/FactRow).
  • "Also in these styles" chips — the reverse-lookup chip row on the template detail (stylesForTemplate). The many-to-many model itself stays (it drives each style's template list); only the reverse display is removed.

Open questions for CEO (deferred-but-unconfirmed)

Confirmed deferred by the CEO on 2026-06-04 — all five stay out of Phase 1 (spec §12, decision 6).

These appear in the prototype but are not on the CEO's in-scope list. Treat as deferred and confirm before any future expansion:

  • References block (ReferencesBlock — property / aspirational reference images).
  • Views / camera angles (the Views rail tab, VIEW_ITEMS, saved camera snapshots).
  • Property Design Profile (the property-scoped profile entity from the sibling idea).
  • Site Analysis (the auto-detected PHOTO_CONTEXT / EXIF panel).
  • The 5-step guided flow (screens.jsx Step 1–5) carried over from the sibling guided-workflow idea.

Hypothesis

A browsable catalog of curated, regionally-aware AI Templates, organized under Design Styles and lightly tunable (plant-palette include-list + optional custom prompt), will let homeowners produce a trustworthy, generatable design with zero typing and one or two taps — outperforming both the empty-prompt status quo and competitors' one-shot style transforms — while preserving the existing free-text generate flow for power users via the embedded Edit History + Custom Edits drawer.

Key Constraints

  • Panel-only surface. Like the sibling idea, every in-scope screen lives inside the Visual Designer's AI panel (the prototype renders at a fixed panel width with an internal title bar and back-navigation). No new top-bar chrome, breadcrumbs, or out-of-panel routes. See the sibling brief's Surface Constraints.
  • Catalog content is seed / admin-curated. Design Styles, AI Templates, their plant palettes, prompt fragments, and galleries are curated content, not user-generated. The user edits a working copy of a template's plant palette at generate time; they do not edit the catalog itself. (2026-07-09: curation now happens in a real admin back-office — see Admin Templates Back-Office.)
  • Many-to-many is the headline. A template can belong to several styles. The model must support this from day one (see Data Model Notes). With the "Also in these styles" chips out of scope, the reverse direction is now data-only (it enables catalog reuse across styles); the forward direction (style → its templates) is what the UI uses.
  • Edit History + Custom Edits reuse, not rebuild. The drawer is the existing generate flow embedded as a subpage. Do not redesign it.
  • No credits/quota surfaces in any in-scope screen.

Data Model Notes

Product-level — what entities exist and how they relate. The developer (Matej) owns the DDL, Hasura metadata, and GraphQL shape; table/column specifics are spec notes, not contracts.

Design Style ⇄ AI Template is many-to-many, deliberately mirroring the existing Plant Collections ⇄ Plants relationship in the Plants tab. The prototype encodes this directly (see the comment block atop the TEMPLATES section in data2.jsx).

| Entity | Role | Prototype shape | |--------|------|-----------------| | Design Style | A category. Browsable, curated. | SYSTEMS: { id, name, tagline, img } | | AI Template | The real, generatable design (image + plant palette + gallery + a curated prompt fragment). | TEMPLATES: { id, name, img, desc, plants[], images[] } (prototype's display-only facts{…} is not stored) | | Style ⇄ Template join | Many-to-many map. One template lives in several styles. | STYLE_TEMPLATES (e.g. water-wise-gravel is in Xeriscape, Utah Localscape, and Fire Resilient) |

The prototype helpers templatesForStyle(styleId) and stylesForTemplate(templateId) are exactly the two read directions a join table provides. In scope, only the forward direction (templatesForStyle) is surfaced; the reverse (stylesForTemplate, the "Also in these styles" chips) is out of scope, so it stays data-only.

The proven analogy is already in our schema. The Plants tab's collection model is:

  • plant_collection — the collection (analogous to Design Style).
  • plant_collection_item — the join row holding collection_id + plant_id (analogous to the Style ⇄ Template join).
  • plant — the leaf item (analogous to AI Template).

The spec re-applies this same three-table shape. The one structural difference: an AI Template carries richer attributes (description, gallery, a curated prompt fragment) than a plant, so the template entity is heavier than a bare plant row — but the relationship topology is identical.

Seed/admin-curated vs. user-editable: Design Styles, Templates, the join, plant palettes, prompt fragments, and galleries are seed/admin-curated. At generate time the user edits an in-memory working copy of the template's plant palette (toggle off, remove, add) — this feeds the generation prompt and does not mutate the catalog. The plant palette's "add" pool draws from existing plant data, reinforcing the plant-collection analogy.

2026-07-09 note on the sections below: everything from Admin Templates Back-Office onward is a dated addition from the 2026-07-06 Utah Water Ways (UWW) program meeting and CEO rulings of 2026-07-09. These sections document what already exists, plus forward-looking candidate/concept directions — they do not reopen the locked 2026-06-04 Phase 1/2 in/out scope above.

Admin Templates Back-Office (2026-07-09)

The catalog's curation surface is no longer hypothetical. An admin templates back-office exists — built ahead of its own documentation and demoed live by the CEO to Utah Water Ways (Cynthia Bee) at the 2026-07-06 program meeting. It provides:

  • template CRUD with images (cover + gallery),
  • the generation prompt fragment and description,
  • the public/private flag (today's only visibility control),
  • the template's associated plant list, and
  • many-to-many design-style associations.

As-built detail lives in spec §13. The product consequence: authoring new templates and patterns — including the Utah pattern library and partner-sponsored patterns below — is an admin content task, not a development task. Ongoing catalog maintenance is the template system's named operating cost.

Template & Plant-List Scoping (candidate, 2026-07-09)

Today a template or style is either globally public or admin-only (is_public). The candidate direction (CEO 2026-07-09 — explicitly "don't close down discovery") is to scope templates, design styles, and their plant lists along three dimensions:

  1. Geography / jurisdiction — State, water District, Municipality, or HOA boundary, via a candidate PostGIS geo-entity overlay (State/District/Municipality/HOA entities matched to the property address).
  2. Whitelabel instance — instance-/location-specific Design Styles and AI Templates with their plant lists, following the shipped instance_plant_collection precedent in the white-label capability brief.
  3. Partner (builder/HOA) — see the sponsored tier concept.

The value is auto-compliance by default: a Daybreak address surfaces the pre-approved HOA plant list and patterns first, making compliant choices the default path instead of homework. Technical exploration (resolution semantics, candidate schema options, open questions) lives in spec §14. The plant-list half must be reconciled with plant-roster-templates so we do not grow competing plant-list systems.

Utah Pattern Library Content Plan (2026-07-09)

From the 2026-07-06 UWW program meeting — the first jurisdiction-scoped content set for the template catalog:

  • Cynthia's 5 park-strip patterns. Cynthia Bee is producing five named park-strip planting patterns (in progress on her side), targeted as the first neighborhood patterns in the catalog. No park-strip patterns exist as templates today — the seeded "Breezy DG Parkway Garden" template only proves park-strip designs are expressible in the model.
  • The Localscapes set. JVWCD's ready-made plans — including "Mix and Match Park Strip Picks" (a plant-selection guide meeting city codes) and park strip design templates — are already inventoried in the LocalScapes research report §4 Available Resources.
  • Eligibility by construction. Author each pattern as a pre-vetted recipe per the H4 recipe framing — every offered look already qualifies. Encode the Localscapes rules: turf at most 35% of total landscape area, 8-ft minimum width, and a single contiguous shape (report §1).
  • Jurisdiction-scoping precedent. Draper City code §9-23-030 directly codifies the 5 Localscapes elements (report §5) — documented evidence that jurisdiction-scoped patterns track real municipal law, not just program guidelines.
  • Program goal. "By 2034, no grass park strips" (Cynthia Bee, 2026-07-06). The park-strip pattern set is the conversion vehicle for that goal.

Builder/HOA Sponsored Tier (concept, 2026-07-09)

From an exploratory builder conversation (Ivory Homes) at the 2026-07-06 meeting: builders and HOAs sponsor their pre-approved patterns and plant lists into the system, geo-/HOA-scoped via the scoping model, so their buyers get through HOA approval fast — "the work's already been done… simply an admin task on our side."

Mechanically this is the partner dimension of the scoping model plus back-office content authoring; the net-new build is small. This brief documents the capability only — commercial terms for this tier are handled privately and are intentionally not recorded in this public repository.

Version History

| Date & Time (MT) | Author | Summary | |-------------------------|--------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | 2026-06-04 04:30 PM MT | Dan | Initial brief, authored final per CEO scope direction (2026-06-04). Locked in/out scope (Design Styles, AI Templates, Edit History, Custom Edits in; Style Quiz, Edit Panel, credits UI out). Captured the Design Style ⇄ AI Template many-to-many model and its Plant Collections ⇄ Plants analogy (incl. the real plant_collection/plant_collection_item/plant schema). Flagged References / Views / Profile / Site Analysis / 5-step flow as deferred-but-unconfirmed open questions for the CEO. Cited sibling generative-ai-chat-interface research rather than duplicating it. | | 2026-06-04 05:40 PM MT | Jarvis | Renamed idea "Design Styles & AI Templates" → "AI Design Templates" per CEO. Slug design-styles-ai-templates → ai-design-templates (directory, _meta.yaml, _catalog.yaml, stage parent fields, doc titles). No scope or content change. | | 2026-06-04 06:20 PM MT | Jarvis | Removed the template-detail "At a glance" facts block and "Also in these styles" chips from scope per CEO. Kept the many-to-many data model (forward style→template lookup drives the UI; reverse is now data-only). Updated Strategic Fit, Scope (in/out), Key Constraints, and Data Model Notes. | | 2026-06-04 07:55 PM MT | Jarvis | Data model: dropped facts from AI Template entirely and added a curated prompt fragment field (injected into the generation prompt). Updated Key Constraints + Data Model Notes. Detailed DDL and the prompt-construction guidance live in the spec. | | 2026-06-04 08:30 PM MT | Jarvis | Recorded the CEO's resolutions of the six spec §12 open questions. Notably keep both custom-edit entry points (per-template PRO field + drawer). Updated the AI Templates scope (added the custom-instructions field; dropped the stale list-card water token) and confirmed the deferred items stay out of Phase 1. | | 2026-07-09 06:25 PM MT | Dan | Dated additions from the 2026-07-06 Utah Water Ways program meeting + CEO 2026-07-09 rulings (locked 2026-06-04 scope unchanged): documented the existing admin templates back-office (demoed live 2026-07-06); added the candidate template & plant-list scoping direction (geography/jurisdiction via PostGIS geo-entity overlay, whitelabel instance, partner — auto-compliance by default); added the Utah pattern library content plan (Cynthia's 5 park-strip patterns, Localscapes set incl. Mix and Match Park Strip Picks, eligibility-by-construction with 35%/8-ft/single-shape rules, Draper §9-23-030 precedent, 2034 no-grass-park-strips goal); added the builder/HOA sponsored-tier concept (capability only; commercial terms handled privately). Cross-linked the plant-roster-templates reconciliation note. |

Design Style Search Volume

Design Style Search-Volume Validation & Ship Priority

Date: 2026-07-08 | Author: Research Analyst (/ss-research) For: AI Design Templates — prioritizing which of the 18 staged Design Styles ship first once Hasura dev access is restored. Companion: design-style-roadmap.md

TL;DR

Demand is not evenly spread across the 18 staged styles. Four are national head-terms with the highest and best-corroborated search demand — Curb Appeal, Modern Farmhouse, English Cottage Garden, and Low-Maintenance Modern — and should be the first cohort made publicly visible. A second cohort rides strong momentum rather than raw volume (Edible Kitchen Garden, No-Mow Meadow, Family Outdoor Living, Japanese Zen, Tropical FL). The regional styles (Southern Charm, Texas Hill Country, Mountain Modern, Coastal NE, PNW Woodland) have smaller absolute pools but far less competition and open whole metros — ship them as we push into those markets, not on a national-volume basis. Firewise and Kid & Pet are lower-volume but high-intent/high-strategic-fit (white-label B2B and family persona respectively).

Methodology caveat: no programmatic keyword-tool access (Keyword Planner / Semrush / Ahrefs). Tiers below are directional, triangulated from live 2026 trend coverage, the volume brackets in our own website-rebuild SEO docs, and analyst head-term knowledge. A one-time Semrush/Ahrefs export (see Next Steps) would convert these tiers into exact monthly-volume integers and settle the two or three close calls.

Method

Three independent signals per style, combined:

  1. Head-term volume — the style name as a US search (e.g. "modern farmhouse landscaping", "cottage garden ideas"), directional bracket.
  2. Momentum — rising / flat / seasonal, from live 2026 trend authorities (Homes & Gardens, House Digest, PHS, Houzz activity).
  3. Reach & fit — national vs regional addressable pool, conversion intent, and strategic fit (white-label B2B pivot, turf-rebate work, existing marketing audiences).

Corroboration from our own corpus: 03b-content-strategy.md already scores "Front Yard Curb Appeal Ideas" a top priority (7.6) and names cottage / Mediterranean / Japanese / modern among the style-guide set worth building; 04c-programmatic-seo.md brackets "curb appeal" flowering-plant terms at 5K–15K.

External signal (2026): modern-minimalist, cottage garden, and xeriscape lead global style search; cottage/English/romantic styles draw the highest engagement among redesign planners; rewilding / no-mow / native meadow is called out repeatedly as the fastest-rising movement; edible landscaping and lawn-reduction / curb appeal are named top-rising 2026 front-yard themes. (Sources table below.)

Ship-Priority Tiers

Head-term volume brackets are directional US monthly estimates for the primary style query, not exact tool figures.

Tier 1 — First cohort (highest demand × national reach, corroborated)

| Style | Head-term bracket | Momentum | Why first | |---|---|---|---| | Curb Appeal Front-Yard Pack | High (30K–50K aggregate) | Rising | Biggest top-of-funnel pool; national; our own SEO priority 7.6; retargets pre-sale/refinance intent | | Modern Farmhouse | High (10K–20K) | Rising | Dominant home-architecture trend; homeowners search by house style; Houzz shows heavy active ideabook volume | | English Cottage Garden | High (20K–40K aggregate) | Evergreen | Highest engagement per redesign-planner data; already validated by our Three-Styles carousel ad | | Low-Maintenance Modern (NY) | Very high ("low maintenance landscaping") | Rising | Already the apply-order anchor; "low-maintenance" is a perennial top-5 national term — correctly front-loaded |

Tier 2 — Fast follow (strong momentum, or high volume that's diffuse)

| Style | Head-term bracket | Momentum | Why | |---|---|---|---| | No-Mow Meadow / Rewilded Lawn | Moderate (5K–15K aggregate) | Fastest-rising | The 2026 movement (no-mow, native meadow, clover lawn); synergy with turf-rebate work | | Edible Kitchen Garden | Moderate–high (10K–20K) | Rising | Named a top-rising theme; strongest content/social angle of the set | | Japanese / Zen Courtyard | High (30K–50K "japanese garden") | Evergreen | Big evergreen volume + small-space fit; note it trails cottage/minimalist on intent-to-redesign | | Family Outdoor Living | Volume huge but diffuse ("backyard ideas" 100K+; "outdoor living" ~5–10K) | Rising | Lifestyle framing converts well; head term is an umbrella, so treat as a hub not a precise keyword | | Tropical Resort (Florida) | Moderate–high in-region (10K–20K) | Flat–rising | FL is a huge single-state market; strong in-region head term |

Tier 3 — Regional coverage & intent plays (ship as we open the metro)

| Style | Head-term bracket | Momentum | Why | |---|---|---|---| | Southern Charm (SE) | Moderate, diffuse | Flat | Biggest unserved region (Atlanta/Carolinas/Nashville/Gulf); value is coverage, not head-term volume | | Texas Hill Country | Low–moderate (2K–5K) | Rising | Distinct identity, Austin/SA growth corridor, high intent, drought pressure | | Firewise Defensible Space | Moderate in-region (5K–10K), seasonal spikes | Rising w/ fire season | High intent; ties to the white-label B2B pivot and institutional angle — strategic weight beyond volume | | Mountain Modern (Rockies) | Low (1K–3K) | Rising | Denver/SLC/Boise are high-value, fast-growing metros | | Kid & Pet Friendly | Moderate (5K–10K "dog friendly / pet friendly backyard") | Flat | Steady, high-intent family persona; durable conversion | | Small-Space Urban Courtyard | Moderate ("small backyard" huge; "courtyard garden" ~5K–10K) | Flat | Synergy with LMM (NY) in dense metros |

Tier 4 — Niche head-term (keep in catalog, lowest ship priority)

| Style | Head-term bracket | Momentum | Why | |---|---|---|---| | Midwest Prairie Native | Low–moderate | Rising w/ rewilding | Real momentum but overlaps No-Mow; ship the No-Mow leader first | | Coastal New England | Low (niche style term; "hydrangea" high but generic) | Flat | Distinct region, small style-term pool | | Pacific Northwest Woodland | Low (niche; "shade garden" adjacency) | Flat | Seattle/Portland; niche style term, ship on regional push |

How this interacts with the technical apply order

The roadmap's 18-seed batch apply order is a crossover-ordinal dependency chain — it dictates the sequence SQL must run in, not business priority. These two orderings are independent:

  • Apply all 18 in the dependency sequence in one batch once dev DB access returns (they share join ordinals; partial application risks collisions).
  • Publish / feature them to customers on the demand tiers above — wire S3 covers and flip public visibility for Tier 1 first, then Tier 2, releasing regional styles (Tier 3) alongside the geo-marketing push into each metro.

So the recommendation is: keep the apply batch intact, but stage the rollout/featuring Tier 1 → Tier 4.

Open questions / where exact numbers would change the call

  • Japanese Zen (Tier 2) vs a Tier 1 slot: its raw volume rivals cottage, but intent-to-redesign is weaker. An exact Semrush pull on "japanese garden ideas" vs "japanese garden landscaping" would settle whether it earns a first-cohort slot.
  • Family Outdoor Living head term is an umbrella — needs a keyword cluster (firepit / outdoor kitchen / pergola) pulled to size properly.
  • No-Mow vs Midwest Prairie overlap: confirm they don't cannibalize before shipping both.

Recommended Next Steps

  1. One-time keyword-tool export (Semrush or Ahrefs; Marketing owns a seat) for the 18 head terms + top 3 modifiers each → replace the directional brackets here with exact monthly volumes and KD (difficulty). ~1 hour; converts this from directional to decisive.
  2. Ship-rollout: wire covers + public visibility Tier 1 first once dev DB access is restored (blocked since 2026-07-01).
  3. Feed the Tier-1 head terms to the website-rebuild style-guide content plan so catalog styles and SEO landing pages launch together.

Sources

| # | Type | Reference | URL | |---|------|-----------|-----| | 1 | Trend authority | Homes & Gardens — 2026 front-yard trends (lawn reduction, water-wise) | https://www.homesandgardens.com/gardens/front-yard-trends-2026 | | 2 | Trend authority | House Digest — Landscaping Trends Taking Over 2026 | https://www.housedigest.com/2182583/landscaping-trends-2026/ | | 3 | Trend authority | Homes & Gardens — 2026 landscape design trends (style popularity) | https://www.homesandgardens.com/gardens/2026-landscape-design-trends | | 4 | Trend authority | PHS — Top 10 Gardening Trends for 2026 | https://phsonline.org/for-gardeners/gardeners-blog/top-gardening-trends-2026 | | 5 | Movement signal | Gardening Know How — Rewilding Your Lawn | https://www.gardeningknowhow.com/lawn-care/lawn-substitutes/rewilding-trend | | 6 | Movement signal | Popular Science — no-mow lawn / grass alternatives | https://www.popsci.com/environment/no-mow-lawn-ideas-grass-alternatives/ | | 7 | Activity proxy | Houzz — Modern Farmhouse landscaping ideabooks (volume proxy) | https://www.houzz.com/photos/farmhouse-landscaping-ideas-phbr1-bp~t_728~s_2114 | | 8 | Regional/fire | UC ANR — Firewise / fire-resistant landscaping | https://ucanr.edu/blog/real-dirt/article/fire-resistant-landscaping | | 9 | Internal corpus | website-rebuild content strategy (curb-appeal priority 7.6, style guides) | docs/simplyscapes/marketing/website-rebuild/03b-content-strategy.md | | 10 | Internal corpus | website-rebuild programmatic SEO (keyword volume brackets) | docs/simplyscapes/marketing/website-rebuild/04c-programmatic-seo.md |

Version History

| Date | Change | Author | |------|--------|--------| | 2026-07-08 | Initial search-volume validation & 4-tier ship priority for the 18 staged Design Styles | ss-research |