create-ailk 0.1.0 → 0.1.1

package/templates/content/_site.mdx

@@ -1,38 +1,37 @@
 ---
 version: "1"
-siteName: AI Launch Kit
-baseUrl: https://ailaunchkit.ai
+siteName: "{{COMPANY_NAME}}"
+baseUrl: https://{{COMPANY_DOMAIN}}
 defaultLocale: en
 siteIdentity:
   kind: Organization
-  name: AI Launch Kit
-  url: https://ailaunchkit.ai
-  logo: https://ailaunchkit.ai/opengraph-image.png
+  name: "{{COMPANY_NAME}}"
+  url: https://{{COMPANY_DOMAIN}}
   description: >
-    AI Launch Kit is the open-source website foundation for the agent-first
-    internet. Apache 2.0, agent-ready, AEO-scored, deployable in days.
-  sameAs:
-    - https://github.com/tailwind-ai/ai-launch-kit
-  foundingDate: "2024"
-  founderName: Sam Henry
+    One or two sentences describing what your organization does. This text is
+    read by answer engines as your canonical self-description, so make it
+    concrete — what you do, for whom.
+  sameAs: []
 analytics:
-  vercelAnalytics: true
-brand:
-  logomark:
-    light: /logomark-light.svg
-    dark: /logomark-dark.svg
-    alt: AI Launch Kit
+  vercelAnalytics: false
 ---
 
 <!--
-This file is your site's canonical configuration. Edit the frontmatter
-above to set your site name, base URL, default locale, and identity
-(Organization, Person, or LocalBusiness).
+This file is your site's canonical configuration. Edit the frontmatter above to
+set your site name, base URL, default locale, and identity.
 
-For the agent-operator workflow, use the `set_site_identity` MCP tool
-instead of editing this file directly — it validates input and writes
-with optimistic locking.
+`siteIdentity.kind` takes one of three values:
 
-See docs/site-config.md (introduced in Phase 3) for the full schema
-reference and the three identity kinds.
+  - Organization  — a company, agency, nonprofit, or team
+  - Person        — a solo practitioner, consultant, or personal site
+  - LocalBusiness — a business with a physical location customers visit
+
+`sameAs` is the list of URLs that are unambiguously the same entity as you —
+your LinkedIn company page, your GitHub org, your X profile. Answer engines use
+it to reconcile your site with the rest of your presence, so it is worth
+filling in.
+
+For the agent-operator workflow, use the `set_site_identity` MCP tool rather
+than editing this file directly — it validates input and writes with optimistic
+locking.
 -->

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

@@ -1,19 +1,29 @@
 ---
 type: "AboutPage"
 slug: "about"
-title: "Sam Henry, Working Theory, and SalesSmyth all run on AILK."
-description: "Sam Henry, Working Theory, and SalesSmyth all run on AI Launch Kit. Meet the team building the open-source foundation for the agent-first internet."
-sections: [{"id": "hero", "type": "hero", "data": {"headline": "Sam Henry, Working Theory, and SalesSmyth all run on AILK.", "subheadline": "Building the foundation first forced the architecture — a typed schema registry, CI-enforced parity, agent-ready surfaces — before it was a product for anyone else.", "body": "Apache 2.0. The architecture is observable in the repo, not on a slide deck — the parity test runs in CI and `.well-known/mcp.json` is live at every deployed URL, including this one.", "primaryCta": {"label": "See the substrate", "href": "/ailk", "variant": "default"}, "secondaryCta": {"label": "Read the foundation thinking", "href": "/blog/ai-seo-foundation", "variant": "outline"}, "variant": "default"}}, {"id": "why-we-exist", "type": "content-block", "data": {"headline": "Why does AILK exist?", "body": "AILK exists because the page — not the site — is the unit of citation in AI search. Most of the web wasn't built for the audience now reading it on a buyer's behalf. When ChatGPT recommends a business, it assembles that recommendation from pages it has read, attributed to a source, and judged trustworthy enough to quote.\n\nWordPress was built when Google was the only entry point. SaaS starters shipped for dashboards and auth — not marketing pages. Closed builders locked customers in by design; that was always the business model. None of them were built for a model to read a page, recognize the brand behind it, and trust the structure enough to cite it.\n\nWe needed that foundation ourselves, first. Sam Henry needed it for his own site. Working Theory needed it to publish a growth-marketing system. SalesSmyth, for GTM consulting. None of the existing options cleared the bar, so the foundation got built — and then opened, Apache 2.0, for anyone building the same kind of site.", "variant": "wide"}}, {"id": "what-a-foundation-must-do", "type": "items", "data": {"headline": "What does a foundation have to do in the agent-first internet?", "description": "Five requirements. None of them are AILK features — they're what any site needs to publish into a world where AI systems read pages and recommend brands.", "columns": 3, "items": [{"title": "Be read correctly", "description": "A model should know what the page is about and which business it belongs to without guessing. If it has to guess, it cites someone else."}, {"title": "Work for non-human visitors", "description": "Agents now research on behalf of buyers. The foundation exposes itself to them as a first-class audience, not a degraded API."}, {"title": "Surface its own gaps", "description": "AEO problems are silent — the site doesn't crash, it just doesn't get cited. A foundation should catch structural gaps the way a linter catches type errors."}, {"title": "Belong to the people running on it", "description": "Foundations that lock customers in shape their roadmap around lock-in. Apache 2.0 keeps that pressure off the roadmap."}, {"title": "Fit inside the engagement", "description": "An SMB site engagement runs weeks, not quarters. A foundation that requires a multi-month custom build breaks the economics."}], "variant": "default"}}, {"id": "the-team", "type": "team", "data": {"headline": "Who built AILK?", "description": "AILK is built by the Working Theory Labs team, led by Sam Henry, with two agent team members contributing directly to the codebase. Full bios live where they belong — Sam Henry's at samhenry.org, the wider Working Theory Labs team at workingtheory.ai.", "variant": "with-small-images", "members": [{"name": "Sam Henry", "role": "Creator, AI Launch Kit · Founder, SalesSmyth LLC", "kind": "human", "bio": "Built AILK first for his own site, then opened it. Full background at samhenry.org."}, {"name": "Working Theory Labs team", "role": "Product and engineering — the team behind AILK", "kind": "human", "bio": "The team building the Working Theory product line, including AILK. Full roster at workingtheory.ai."}, {"name": "Claudio Planck", "role": "Agent team member — architecture, code review, and implementation", "kind": "agent", "bio": "AI engineering agent contributing across the AILK substrate."}, {"name": "Anders Stewart", "role": "Agent team member — implementation strategy", "kind": "agent", "bio": "AI VP Engineering agent, coordinating with the human team on shipped work."}]}}, {"id": "relationships", "type": "content-block", "data": {"headline": "How does AILK relate to Working Theory and SalesSmyth?", "body": "AILK is made by SalesSmyth LLC, the company behind the Working Theory product line. It's published under the Working Theory brand. That's why you'll see \"AI Launch Kit by Working Theory\" across the site. Sam Henry created AILK and founded SalesSmyth LLC. Working Theory Platform is a sister product — growth marketing as a system — and publishes into AILK with the deepest integration of any tool in the portfolio. AILK works fully standalone for developers and agencies who never touch Working Theory Platform. Neither product requires the other.", "variant": "default"}}, {"id": "dogfooding-proof", "type": "social-proof", "data": {"headline": "Does the team actually run on AILK?", "variant": "cards", "items": [{"author": "Sam Henry", "content": "Publishes on AILK — the reason the schema registry and the peer-surfaces architecture exist in their current shape. We hit the problem first.", "source": "generic"}, {"author": "Working Theory", "content": "Runs its growth-marketing product line on AILK, publishing into the substrate with the deepest integration in the portfolio.", "source": "generic"}, {"author": "SalesSmyth", "content": "The GTM-consulting brand behind AILK runs its own site on the same foundation it ships to customers.", "source": "generic"}]}}, {"id": "about-faq", "type": "faq", "data": {"headline": "Common questions about AILK and the team behind it", "presentation": "expanded", "items": [{"question": "Is AILK the same company as Working Theory?", "answer": "No. SalesSmyth LLC is the company that makes AILK. Working Theory is the product line — the brand AILK is published under, not a separate company. \"AI Launch Kit by Working Theory\" names the relationship: one maker, one brand, one product."}, {"question": "Who is Sam Henry and what's his role in AILK?", "answer": "Sam Henry created AILK and founded SalesSmyth LLC, the company behind it. He built the foundation for his own site first, then opened it under Apache 2.0. His full background is at samhenry.org; this page covers his role in AILK, not his biography."}, {"question": "Does the AILK team actually use the product?", "answer": "Yes. Sam Henry, Working Theory, and SalesSmyth all publish on AILK today. The schema registry and the peer-surfaces architecture exist in their current shape because the team hit these problems first — not because of a marketing claim."}, {"question": "Do I have to use Working Theory Platform to use AILK?", "answer": "No. AILK works fully standalone for developers and agencies. Working Theory Platform is a separate product — growth marketing as a system — that publishes into AILK with the deepest integration available. It's the recommended substrate for Platform customers who need a website, not a requirement for anyone else."}]}}, {"id": "cta-see-substrate", "type": "cta", "data": {"headline": "See the substrate AILK runs on.", "description": "The same architecture Sam Henry, Working Theory, and SalesSmyth publish on — schema registry, peer surfaces, audit CLI, all Apache 2.0.", "primaryCta": {"label": "See the substrate", "href": "/ailk", "variant": "default"}, "secondaryCta": {"label": "Read the foundation thinking", "href": "/blog/ai-seo-foundation", "variant": "outline"}, "variant": "default"}}]
-status: "Approved"
-pageKey: "AboutPage"
-entity: "ailaunchkit"
-urlSlug: "about-page"
-lastUpdated: "2026-07-06"
-pageLevelSchemaType: "AboutPage"
+title: "About {{COMPANY_NAME}}"
+description: "Replace this with a sentence about who you are and why you do this work."
+sections:
+  [
+    {
+      "id": "hero",
+      "type": "hero",
+      "data":
+        {
+          "headline": "About {{COMPANY_NAME}}",
+          "subheadline": "Replace this with the short version of your story.",
+        },
+    },
+    {
+      "id": "why-we-exist",
+      "type": "content-block",
+      "data":
+        {
+          "headline": "Why we exist",
+          "body": "Replace this paragraph with the reason your organization exists — the problem you kept running into, or the gap you decided to fill. Concrete beats aspirational.",
+        },
+    },
+  ]
 ---
 
-import { JsonLd } from '@/components/JsonLd'
-
-<JsonLd data={{"@context": "https://schema.org", "@graph": [{"@type": "Product", "additionalType": "SoftwareApplication", "@id": "https://ailaunchkit.ai/#product", "name": "AI Launch Kit", "alternateName": ["AI Launch Kit by Working Theory", "AILK by Working Theory", "AILK", "@ailaunchkit", "@ailk", "@working-theory", "ai-launch-kit"], "url": "https://ailaunchkit.ai", "description": "AI Launch Kit is the open-source website foundation for the agent-first internet — Apache 2.0, agent-ready, AEO-scored, deployable in days.", "sameAs": ["https://github.com/working-theory-labs/ai-launch-kit", "https://x.com/ailaunchkit", "https://www.npmjs.com/org/ailk", "https://youtube.com/@working-theory", "https://linkedin.com/company/working-theory"], "foundingDate": "2026", "category": "Open-source website foundation", "applicationCategory": "DeveloperApplication", "operatingSystem": "Cross-platform (Node.js)", "license": "https://www.apache.org/licenses/LICENSE-2.0", "codeRepository": "https://github.com/working-theory-labs/ai-launch-kit", "manufacturer": {"@type": "Organization", "@id": "https://ailaunchkit.ai/#salessmyth", "name": "SalesSmyth LLC"}, "brand": {"@type": "Brand", "@id": "https://workingtheory.ai/#brand", "name": "Working Theory", "url": "https://workingtheory.ai"}, "creator": {"@type": "Person", "@id": "https://samhenry.org/#person", "name": "Sam Henry", "url": "https://samhenry.org"}, "contributor": [{"@type": "SoftwareApplication", "name": "Claudio Planck", "description": "AI engineering agent contributing across the AILK substrate."}, {"@type": "SoftwareApplication", "name": "Anders Stewart", "description": "AI VP Engineering agent, coordinating with the human team on shipped work."}]}, {"@type": "AboutPage", "@id": "https://ailaunchkit.ai/about/#webpage", "url": "https://ailaunchkit.ai/about", "name": "About", "description": "Sam Henry, Working Theory, and SalesSmyth all run on AI Launch Kit. Meet the team building the open-source foundation for the agent-first internet.", "isPartOf": {"@id": "https://ailaunchkit.ai/#product"}, "mainEntity": {"@type": "Organization", "@id": "https://ailaunchkit.ai/#salessmyth", "name": "SalesSmyth LLC"}, "about": {"@id": "https://ailaunchkit.ai/#product"}}]}} />
-
-{/* Rendered from frontmatter `sections[]`; the MDX body is not read by the section-catalog renderer. Landed by land-section-catalog.py (#3111). */}
+{/* Rendered from frontmatter `sections[]`. A `team` section is a good next addition here once you have people to list. */}

package/templates/content/en/ContactPage/contact.mdx

@@ -1,19 +1,28 @@
 ---
 type: "ContactPage"
 slug: "contact"
-title: "Contact AI Launch Kit"
-description: "Contact AI Launch Kit by email, intro call, or GitHub Issues — reach the Working Theory team for Pro, Pro Plus, Launch Service, or OSS support."
-sections: [{"id": "contact-hero", "type": "hero", "data": {"headline": "Contact AI Launch Kit", "subheadline": "Email us, book an intro call, or open a GitHub issue — whichever matches what you need.", "primaryCta": {"label": "Email hello@ailaunchkit.ai", "href": "mailto:hello@ailaunchkit.ai"}, "secondaryCta": {"label": "Book an intro call", "href": "/book-call", "variant": "outline"}}}, {"id": "contact-framing", "type": "content-block", "data": {"body": "Evaluating Pro, Pro Plus, or Launch Service? Email or book an intro call directly. Running the Apache 2.0 foundation and need OSS support? Open a GitHub issue, where the codebase context already lives. Both paths reach the Working Theory team. Pick the one that matches what you're doing."}}, {"id": "contact-channels-primary", "type": "contact-channels", "data": {"items": [{"icon": "mail", "headline": "Email", "description": "hello@ailaunchkit.ai — the direct line to the Working Theory team. Use this for pricing questions, Launch Service scoping, or anything that doesn't fit a GitHub issue.", "cta": {"label": "Email hello@ailaunchkit.ai", "href": "mailto:hello@ailaunchkit.ai"}}, {"icon": "calendar", "headline": "Book an intro call", "description": "For Pro, Pro Plus, or Launch Service — a short call to scope what you need before you commit to a tier.", "cta": {"label": "Book an intro call", "href": "/book-call"}}, {"icon": "github", "headline": "GitHub Issues", "description": "For OSS support, bugs, and feature requests against the AI Launch Kit repo. The direct path for anything code-related.", "cta": {"label": "Open a GitHub issue", "href": "https://github.com/working-theory-labs/ai-launch-kit/issues"}}]}}, {"id": "contact-cta-book-call", "type": "cta", "data": {"headline": "Ready to talk Pro, Pro Plus, or Launch Service?", "primaryCta": {"label": "Book an intro call", "href": "/book-call"}, "secondaryCta": {"label": "Email hello@ailaunchkit.ai", "href": "mailto:hello@ailaunchkit.ai", "variant": "ghost"}}}, {"id": "contact-faq", "type": "faq", "data": {"items": [{"question": "Is there a phone number for AI Launch Kit?", "answer": "No. AI Launch Kit doesn't operate a phone line — communication runs async through email and GitHub Issues. Email hello@ailaunchkit.ai or open a GitHub issue and the Working Theory team will follow up."}, {"question": "Where is AI Launch Kit located?", "answer": "AI Launch Kit operates remote. There's no office to visit. The team works across time zones and reaches customers and contributors by email, GitHub, and booked calls."}, {"question": "Should I email or open a GitHub issue?", "answer": "Pricing, Pro, Pro Plus, Launch Service — email or book a call. Bug, feature request, or a question about the OSS codebase — open a GitHub issue. The repo context is already there."}]}}]
-status: "Approved"
-pageKey: "ContactPage"
-entity: "ailaunchkit"
-urlSlug: "contact-page"
-lastUpdated: "2026-07-06"
-pageLevelSchemaType: "ContactPage"
+title: "Contact {{COMPANY_NAME}}"
+description: "How to reach {{COMPANY_NAME}}. Replace this with the channels you actually monitor."
+sections:
+  [
+    {
+      "id": "hero",
+      "type": "hero",
+      "data":
+        {
+          "headline": "Contact {{COMPANY_NAME}}",
+          "subheadline": "Replace this with how you prefer to be reached, and how quickly you reply.",
+        },
+    },
+    {
+      "id": "channels",
+      "type": "content-block",
+      "data":
+        {
+          "body": "Replace this with your contact channels — email, a booking link, a form. List only the ones you actually monitor: a published channel nobody watches is worse than no channel.",
+        },
+    },
+  ]
 ---
 
-import { JsonLd } from '@/components/JsonLd'
-
-<JsonLd data={{"@context": "https://schema.org", "@graph": [{"@type": ["Product", "SoftwareApplication"], "@id": "https://ailaunchkit.ai/#product", "name": "AI Launch Kit", "alternateName": ["AI Launch Kit by Working Theory", "AILK by Working Theory", "AILK", "@ailaunchkit", "@ailk", "@working-theory", "ai-launch-kit"], "url": "https://ailaunchkit.ai", "description": "AI Launch Kit is the open-source website foundation for the agent-first internet — Apache 2.0, agent-ready, AEO-scored, deployable in days.", "sameAs": ["https://github.com/working-theory-labs/ai-launch-kit", "https://x.com/ailaunchkit", "https://www.npmjs.com/org/ailk", "https://youtube.com/@working-theory", "https://linkedin.com/company/working-theory"], "foundingDate": "2026", "category": "Open-source website foundation", "applicationCategory": "DeveloperApplication", "operatingSystem": "Cross-platform (Node.js)", "license": "https://www.apache.org/licenses/LICENSE-2.0", "codeRepository": "https://github.com/working-theory-labs/ai-launch-kit", "manufacturer": {"@id": "https://workingtheory.ai/#organization"}, "brand": {"@id": "https://workingtheory.ai/#organization"}, "creator": {"@id": "https://samhenry.org/#person"}, "offers": [{"@type": "Offer", "name": "Free (OSS, Apache 2.0)", "price": "0", "priceCurrency": "USD"}, {"@type": "Offer", "name": "Pro", "price": "249", "priceCurrency": "USD", "unitText": "per user per year"}, {"@type": "Offer", "name": "Pro Plus", "price": "449", "priceCurrency": "USD", "unitText": "per user per month"}, {"@type": "Offer", "name": "Launch Service", "price": "2495", "priceCurrency": "USD"}]}, {"@type": "ContactPage", "@id": "https://ailaunchkit.ai/contact#webpage", "url": "https://ailaunchkit.ai/contact", "name": "Contact AI Launch Kit", "description": "Contact AI Launch Kit by email, intro call, or GitHub Issues — reach the Working Theory team for Pro, Pro Plus, Launch Service, or OSS support.", "isPartOf": {"@id": "https://ailaunchkit.ai/#product"}, "mainEntity": {"@type": "Organization", "name": "AI Launch Kit by Working Theory", "email": "hello@ailaunchkit.ai", "sameAs": ["https://github.com/working-theory-labs/ai-launch-kit"], "contactPoint": [{"@type": "ContactPoint", "contactType": "customer support", "email": "hello@ailaunchkit.ai", "availableLanguage": "English"}]}}]}} />
-
-{/* Rendered from frontmatter `sections[]`; the MDX body is not read by the section-catalog renderer. Landed by land-section-catalog.py (#3111). */}
+{/* Rendered from frontmatter `sections[]`. Swap the content-block above for a `contact-channels` section once you know your channels. */}

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

@@ -1,8 +1,8 @@
 ---
 type: "FAQPage"
 slug: "faq"
-title: "AI Launch Kit — Frequently Asked Questions"
-description: "Answers to the real questions about AI Launch Kit — pre-launch risk, fleet management, Working Theory ties, Next.js requirements, WordPress migration, and Apache 2.0 licensing."
+title: "{{COMPANY_NAME}} — Frequently Asked Questions"
+description: "Answers to the questions people actually ask about {{COMPANY_NAME}}."
 sections:
   [
     {
@@ -10,411 +10,29 @@ sections:
       "type": "hero",
       "data":
         {
-          "headline": "AI Launch Kit — Frequently Asked Questions",
-          "subheadline": "Straight answers, no marketing spin — pre-launch risk, fleet management, Working Theory, Next.js, WordPress migration, licensing. What ships today. What's still ahead.",
+          "headline": "Frequently Asked Questions",
+          "subheadline": "Replace these with the questions you are actually asked.",
         },
     },
     {
-      "id": "faq-pre-launch-concerns",
+      "id": "faq",
       "type": "faq",
       "data":
         {
-          "headline": "Pre-launch concerns",
           "items":
             [
               {
-                "question": "You're pre-launch. Why bet on this?",
-                "answer": "The architecture is observable in the repo, not a pitch deck. The typed schema registry is a directory of 60 entries, the parity test runs in CI, and the audit CLI runs today. You're not taking our word for any of it.",
+                "question": "Replace this with a real question you get asked.",
+                "answer": "Answer it directly, in the first sentence. An FAQ answer that opens with context and buries the answer in paragraph three does not get quoted.",
               },
               {
-                "question": "Is the architecture real, or just a pitch?",
-                "answer": "It's real and checkable. `apps/web`, `apps/mcp`, and `apps/api` run as peer apps in one repo, with a CI-enforced parity test and a live `.well-known/mcp.json` endpoint. Clone the repo and verify it yourself — the `ailk audit` CLI runs against any AILK site, including this one.",
-              },
-              {
-                "question": "What happens if AILK doesn't find traction?",
-                "answer": "You keep everything. AILK ships under Apache 2.0, so the codebase belongs to you regardless of what happens to the company behind it. No lock-in, no dependency on a vendor's survival — the license itself bounds the downside.",
-              },
-              {
-                "question": "Do you have customer proof yet?",
-                "answer": "Not yet from outside the founding team, and we're not pretending otherwise. Sam Henry, Working Theory, and SalesSmyth all publish on AILK today — that's real dogfooding, not a case study. Independent customer proof builds over the next 90–180 days as Launch Service and Pro customers come on.",
-              },
-            ],
-        },
-    },
-    {
-      "id": "faq-fleet-management",
-      "type": "faq",
-      "data":
-        {
-          "headline": "Fleet management",
-          "items":
-            [
-              {
-                "question": "We run a portfolio of client sites. Where's fleet management?",
-                "answer": "Deferred. Fleet management, cross-site rollup, white-label, and per-seat licensing are planned as a future Enterprise multi-tenant entitlement, not a separate tier. At launch, agencies deliver on OSS plus Pro, managed per-site rather than as a fleet.",
-              },
-              {
-                "question": "When will Fleet Management ship?",
-                "answer": "No fixed date. It lands in that same post-launch window, and the exact timing depends on demand for the entitlement. It ships once the core substrate is proven at single-site scale first.",
-              },
-            ],
-        },
-    },
-    {
-      "id": "faq-multi-site",
-      "type": "faq",
-      "data":
-        {
-          "headline": "Multi-site management",
-          "items":
-            [
-              {
-                "question": "How do I manage multiple client sites today, before fleet management ships?",
-                "answer": "Per-site, on OSS or Pro. Each client site is its own AILK deploy with its own repo, schema registry, and audit run. There's no fleet dashboard yet — that's the gap fleet management closes. Nothing stops you from running several client sites in parallel today.",
-              },
-              {
-                "question": "Is there a discount for managing many sites on Pro?",
-                "answer": "Not currently. Pro is priced per user per year ($249), not per site, so an agency running several client sites on one Pro seat pays the same rate regardless of site count. Volume-based agency pricing arrives with the Enterprise multi-tenant entitlement.",
-              },
-            ],
-        },
-    },
-    {
-      "id": "faq-working-theory-relationship",
-      "type": "faq",
-      "data":
-        {
-          "headline": "Working Theory relationship",
-          "items":
-            [
-              {
-                "question": "How does this relate to Working Theory Platform? Am I locked in?",
-                "answer": "You're not locked in. AILK works fully standalone. Working Theory Platform is a separate product — growth marketing as a system that publishes into AILK with the deepest integration available. Neither product requires the other.",
-              },
-              {
-                "question": "Do I need Working Theory Platform to use AILK?",
-                "answer": "No. Clone AILK, deploy it, run it — none of that touches Working Theory Platform. Platform is the recommended layer for customers who also want ongoing growth marketing; it isn't a requirement to use AILK.",
+                "question": "What makes a good FAQ entry?",
+                "answer": "A question phrased the way someone would actually ask it, and an answer that stands alone without the rest of the page. This page emits FAQPage JSON-LD, so each pair is machine-readable on its own.",
               },
             ],
         },
     },
-    {
-      "id": "faq-nextjs-requirement",
-      "type": "faq",
-      "data":
-        {
-          "headline": "Next.js requirement",
-          "items":
-            [
-              {
-                "question": "We're not Next.js native. Is this still for us?",
-                "answer": "Yes, if AI search visibility is the deliverable you're selling. Launch Service is the path — a fixed-scope two-week deploy onto the substrate. Your team owns content and citation work from there. Next.js fluency helps. It isn't required.",
-              },
-              {
-                "question": "Do I need to write MDX myself?",
-                "answer": "No. Launch Service handles the build; your team works in content and citation strategy from there, with no MDX or build pipeline required on your end. Teams that want to write MDX directly can — it's the foundation's native content format.",
-              },
-            ],
-        },
-    },
-    {
-      "id": "faq-migration-from-wordpress",
-      "type": "faq",
-      "data":
-        {
-          "headline": "Migration from WordPress",
-          "items":
-            [
-              {
-                "question": "Can I migrate my existing WordPress site to AILK?",
-                "answer": "Yes, though AILK isn't positioned as a migration tool — it's a foundation you rebuild on. Content and schema get recreated on AILK's typed page structure rather than imported wholesale, since the underlying data models don't match a plugin-based WordPress stack.",
-              },
-              {
-                "question": "What happens to my existing SEO rankings during a move off WordPress?",
-                "answer": "Rankings depend on redirect discipline and content parity, not the platform switch itself. A well-executed move preserves URLs where possible and 301s the rest. It typically improves the schema and entity markup that WordPress plugin stacks handle inconsistently.",
-              },
-              {
-                "question": "How long does a WordPress migration take?",
-                "answer": "Launch Service runs a fixed two-week scope for a new AILK deploy. Actual migration timeline depends on how much existing content needs to be recreated. A small brochure site fits inside two weeks; larger content libraries take longer to fully port over.",
-              },
-            ],
-        },
-    },
-    {
-      "id": "faq-pricing-and-licensing",
-      "type": "faq",
-      "data":
-        {
-          "headline": "Pricing & licensing",
-          "items":
-            [
-              {
-                "question": "What's the difference between Free, Pro, and Pro Plus?",
-                "answer": "Free is the Apache 2.0 OSS foundation — complete, not crippled. Pro adds capability at $249 per user per year. Pro Plus adds ongoing care at $449 per user per month. Paid tiers build on the free foundation; they never gate access to it.",
-              },
-              {
-                "question": "Is the OSS version really free forever?",
-                "answer": 'Yes. AILK''s OSS layer is Apache 2.0 — not source-available, not "free until you make money," and not deliberately crippled to push a paid tier. It''s structurally complete today, and it stays that way regardless of what paid tiers add later.',
-              },
-              {
-                "question": "What license does AILK use?",
-                "answer": "Apache 2.0, the permissive open-source license, published on GitHub with no dual-licensing traps. Clone it. Modify it. Deploy it commercially — no royalty obligations back to Working Theory.",
-              },
-            ],
-        },
-    },
-    {
-      "id": "faq-closing-cta",
-      "type": "cta",
-      "data":
-        {
-          "headline": "Still have questions?",
-          "description": "Talk to us directly about Launch Service, Pro, or Enterprise fleet management — or skip the conversation and clone the OSS foundation yourself.",
-          "primaryCta":
-            { "label": "Book Launch Service call", "href": "/launch-service" },
-          "secondaryCta":
-            {
-              "label": "Clone OSS",
-              "href": "/developers",
-              "variant": "outline",
-            },
-        },
-    },
   ]
-status: "Approved"
-pageKey: "FAQPage"
-entity: "ailaunchkit"
-urlSlug: "faq-page"
-lastUpdated: "2026-07-06"
-pageLevelSchemaType: "FAQPage"
 ---
 
-import { JsonLd } from "@/components/JsonLd";
-
-<JsonLd
-  data={{
-    "@context": "https://schema.org",
-    "@graph": [
-      {
-        "@type": "Product",
-        additionalType: "https://schema.org/SoftwareApplication",
-        "@id": "https://ailaunchkit.ai/#product",
-        name: "AI Launch Kit",
-        alternateName: [
-          "AI Launch Kit by Working Theory",
-          "AILK by Working Theory",
-          "AILK",
-          "@ailaunchkit",
-          "@ailk",
-          "@working-theory",
-          "ai-launch-kit",
-        ],
-        url: "https://ailaunchkit.ai",
-        description:
-          "AI Launch Kit is the open-source website foundation for the agent-first internet — Apache 2.0, agent-ready, AEO-scored, deployable in days.",
-        sameAs: [
-          "https://github.com/working-theory-labs/ai-launch-kit",
-          "https://x.com/ailaunchkit",
-          "https://www.npmjs.com/org/ailk",
-          "https://youtube.com/@working-theory",
-          "https://linkedin.com/company/working-theory",
-        ],
-        foundingDate: "2026",
-        category: "Open-source website foundation",
-        applicationCategory: "DeveloperApplication",
-        operatingSystem: "Cross-platform (Node.js)",
-        license: "https://www.apache.org/licenses/LICENSE-2.0",
-        codeRepository: "https://github.com/working-theory-labs/ai-launch-kit",
-        manufacturer: {
-          "@type": "Organization",
-          "@id": "https://ailaunchkit.ai/#organization",
-          name: "SalesSmyth LLC",
-        },
-        brand: {
-          "@type": "Brand",
-          name: "Working Theory",
-          url: "https://workingtheory.ai",
-        },
-        creator: { "@type": "Person", name: "Sam Henry" },
-        offers: [
-          {
-            "@type": "Offer",
-            name: "Free (OSS)",
-            price: "0",
-            priceCurrency: "USD",
-          },
-          { "@type": "Offer", name: "Pro", price: "249", priceCurrency: "USD" },
-          {
-            "@type": "Offer",
-            name: "Pro Plus",
-            price: "449",
-            priceCurrency: "USD",
-          },
-          {
-            "@type": "Offer",
-            name: "Launch Service",
-            price: "2495",
-            priceCurrency: "USD",
-          },
-        ],
-      },
-      {
-        "@type": "FAQPage",
-        "@id": "https://ailaunchkit.ai/faq#webpage",
-        url: "https://ailaunchkit.ai/faq",
-        name: "AI Launch Kit — Frequently Asked Questions",
-        description:
-          "Answers to the real questions about AI Launch Kit — pre-launch risk, fleet management, Working Theory ties, Next.js requirements, WordPress migration, and Apache 2.0 licensing.",
-        isPartOf: { "@id": "https://ailaunchkit.ai/#product" },
-        mainEntity: [
-          {
-            "@type": "Question",
-            name: "You're pre-launch. Why bet on this?",
-            acceptedAnswer: {
-              "@type": "Answer",
-              text: "The architecture is observable in the repo, not a pitch deck. The typed schema registry is a directory of 60 entries, the parity test runs in CI, and the audit CLI runs today. You're not taking our word for any of it.",
-            },
-          },
-          {
-            "@type": "Question",
-            name: "Is the architecture real, or just a pitch?",
-            acceptedAnswer: {
-              "@type": "Answer",
-              text: "It's real and checkable. `apps/web`, `apps/mcp`, and `apps/api` run as peer apps in one repo, with a CI-enforced parity test and a live `.well-known/mcp.json` endpoint. Clone the repo and verify it yourself — the `ailk audit` CLI runs against any AILK site, including this one.",
-            },
-          },
-          {
-            "@type": "Question",
-            name: "What happens if AILK doesn't find traction?",
-            acceptedAnswer: {
-              "@type": "Answer",
-              text: "You keep everything. AILK ships under Apache 2.0, so the codebase belongs to you regardless of what happens to the company behind it. No lock-in, no dependency on a vendor's survival — the license itself bounds the downside.",
-            },
-          },
-          {
-            "@type": "Question",
-            name: "Do you have customer proof yet?",
-            acceptedAnswer: {
-              "@type": "Answer",
-              text: "Not yet from outside the founding team, and we're not pretending otherwise. Sam Henry, Working Theory, and SalesSmyth all publish on AILK today — that's real dogfooding, not a case study. Independent customer proof builds over the next 90–180 days as Launch Service and Pro customers come on.",
-            },
-          },
-          {
-            "@type": "Question",
-            name: "We run a portfolio of client sites. Where's fleet management?",
-            acceptedAnswer: {
-              "@type": "Answer",
-              text: "Deferred. Fleet management, cross-site rollup, white-label, and per-seat licensing are planned as a future Enterprise multi-tenant entitlement, not a separate tier. At launch, agencies deliver on OSS plus Pro, managed per-site rather than as a fleet.",
-            },
-          },
-          {
-            "@type": "Question",
-            name: "When will Fleet Management ship?",
-            acceptedAnswer: {
-              "@type": "Answer",
-              text: "No fixed date. It lands in that same post-launch window, and the exact timing depends on demand for the entitlement. It ships once the core substrate is proven at single-site scale first.",
-            },
-          },
-          {
-            "@type": "Question",
-            name: "How do I manage multiple client sites today, before fleet management ships?",
-            acceptedAnswer: {
-              "@type": "Answer",
-              text: "Per-site, on OSS or Pro. Each client site is its own AILK deploy with its own repo, schema registry, and audit run. There's no fleet dashboard yet — that's the gap fleet management closes. Nothing stops you from running several client sites in parallel today.",
-            },
-          },
-          {
-            "@type": "Question",
-            name: "Is there a discount for managing many sites on Pro?",
-            acceptedAnswer: {
-              "@type": "Answer",
-              text: "Not currently. Pro is priced per user per year ($249), not per site, so an agency running several client sites on one Pro seat pays the same rate regardless of site count. Volume-based agency pricing arrives with the Enterprise multi-tenant entitlement.",
-            },
-          },
-          {
-            "@type": "Question",
-            name: "How does this relate to Working Theory Platform? Am I locked in?",
-            acceptedAnswer: {
-              "@type": "Answer",
-              text: "You're not locked in. AILK works fully standalone. Working Theory Platform is a separate product — growth marketing as a system that publishes into AILK with the deepest integration available. Neither product requires the other.",
-            },
-          },
-          {
-            "@type": "Question",
-            name: "Do I need Working Theory Platform to use AILK?",
-            acceptedAnswer: {
-              "@type": "Answer",
-              text: "No. Clone AILK, deploy it, run it — none of that touches Working Theory Platform. Platform is the recommended layer for customers who also want ongoing growth marketing; it isn't a requirement to use AILK.",
-            },
-          },
-          {
-            "@type": "Question",
-            name: "We're not Next.js native. Is this still for us?",
-            acceptedAnswer: {
-              "@type": "Answer",
-              text: "Yes, if AI search visibility is the deliverable you're selling. Launch Service is the path — a fixed-scope two-week deploy onto the substrate. Your team owns content and citation work from there. Next.js fluency helps. It isn't required.",
-            },
-          },
-          {
-            "@type": "Question",
-            name: "Do I need to write MDX myself?",
-            acceptedAnswer: {
-              "@type": "Answer",
-              text: "No. Launch Service handles the build; your team works in content and citation strategy from there, with no MDX or build pipeline required on your end. Teams that want to write MDX directly can — it's the foundation's native content format.",
-            },
-          },
-          {
-            "@type": "Question",
-            name: "Can I migrate my existing WordPress site to AILK?",
-            acceptedAnswer: {
-              "@type": "Answer",
-              text: "Yes, though AILK isn't positioned as a migration tool — it's a foundation you rebuild on. Content and schema get recreated on AILK's typed page structure rather than imported wholesale, since the underlying data models don't match a plugin-based WordPress stack.",
-            },
-          },
-          {
-            "@type": "Question",
-            name: "What happens to my existing SEO rankings during a move off WordPress?",
-            acceptedAnswer: {
-              "@type": "Answer",
-              text: "Rankings depend on redirect discipline and content parity, not the platform switch itself. A well-executed move preserves URLs where possible and 301s the rest. It typically improves the schema and entity markup that WordPress plugin stacks handle inconsistently.",
-            },
-          },
-          {
-            "@type": "Question",
-            name: "How long does a WordPress migration take?",
-            acceptedAnswer: {
-              "@type": "Answer",
-              text: "Launch Service runs a fixed two-week scope for a new AILK deploy. Actual migration timeline depends on how much existing content needs to be recreated. A small brochure site fits inside two weeks; larger content libraries take longer to fully port over.",
-            },
-          },
-          {
-            "@type": "Question",
-            name: "What's the difference between Free, Pro, and Pro Plus?",
-            acceptedAnswer: {
-              "@type": "Answer",
-              text: "Free is the Apache 2.0 OSS foundation — complete, not crippled. Pro adds capability at $249 per user per year. Pro Plus adds ongoing care at $449 per user per month. Paid tiers build on the free foundation; they never gate access to it.",
-            },
-          },
-          {
-            "@type": "Question",
-            name: "Is the OSS version really free forever?",
-            acceptedAnswer: {
-              "@type": "Answer",
-              text: "Yes. AILK's OSS layer is Apache 2.0 — not source-available, not \"free until you make money,\" and not deliberately crippled to push a paid tier. It's structurally complete today, and it stays that way regardless of what paid tiers add later.",
-            },
-          },
-          {
-            "@type": "Question",
-            name: "What license does AILK use?",
-            acceptedAnswer: {
-              "@type": "Answer",
-              text: "Apache 2.0, the permissive open-source license, published on GitHub with no dual-licensing traps. Clone it. Modify it. Deploy it commercially — no royalty obligations back to Working Theory.",
-            },
-          },
-        ],
-      },
-    ],
-  }}
-/>
-
-{/* Rendered from frontmatter `sections[]`; the MDX body is not read by the section-catalog renderer. Landed by land-section-catalog.py (#3111). */}
+{/* Rendered from frontmatter `sections[]`. Each question/answer pair is emitted as schema.org FAQPage structured data — keep answers self-contained. */}