create-ailk 0.1.0

package/templates/content/en/LandingPage/platform.mdx

@@ -0,0 +1,369 @@
+---
+type: "LandingPage"
+slug: "platform"
+title: "13 capabilities. 10 shipped. 3 planned. No blur between them."
+description: "AILK's honest capability roster: 10 Installed capabilities shipping today, 3 Platform Services planned but not yet built — scored, not pitched."
+sections:
+  [
+    {
+      "id": "hero",
+      "type": "hero",
+      "data":
+        {
+          "headline": "13 capabilities. 10 shipped. 3 planned. No blur between them.",
+          "subheadline": "Every AILK capability is scored Installed or Platform Service — never folded into one undifferentiated feature list.",
+          "body": "This is the roster we hold ourselves to before we sell it to you. We don't invent ship dates for what isn't built. If a capability isn't shipped, this page says so — not your account manager, three months into the engagement.",
+          "badge": "Ten Installed. Three Platform Services. Published, not pitched.",
+          "primaryCta":
+            { "label": "Clone the OSS foundation", "href": "/developers" },
+          "secondaryCta":
+            {
+              "label": "See Enterprise pricing",
+              "href": "/pricing",
+              "variant": "outline",
+            },
+        },
+    },
+    {
+      "id": "honesty-principle",
+      "type": "content-block",
+      "data":
+        {
+          "headline": "Why we publish what isn't built yet",
+          "body": "Hiding the roadmap costs more trust than showing it. A buyer evaluating a pre-launch foundation can't verify a promise — only a label. So every AILK capability carries one of two: Installed, meaning it's in the repo and running in production today, or Platform Service, meaning it's scoped and scheduled but not built.\n\nMost vendors describe unshipped features in the present tense and let the buyer discover the gap later. We built the opposite habit on purpose. The `ailk audit` CLI that scores a site's AEO structure runs today. The Enterprise multi-tenant entitlement that lets a firm manage a portfolio of client sites from one dashboard does not. We say so, on this page, without softening the gap with an invented date.\n\nThe bet: a serious evaluator — an agency standardizing its stack, a developer deciding what to build on — discounts an unlabeled roadmap and rewards a labeled one. If we're wrong about that, the roster stays honest regardless.",
+        },
+    },
+    {
+      "id": "capability-counts",
+      "type": "stats",
+      "data":
+        {
+          "headline": "What's shipped, what's planned",
+          "variant": "tiles",
+          "items":
+            [
+              {
+                "value": 10,
+                "label": "Installed — shipped, running in production",
+                "tone": "success",
+              },
+              {
+                "value": 3,
+                "label": "Platform Services — planned, not yet built",
+                "tone": "warning",
+              },
+              {
+                "value": 13,
+                "label": "Total capabilities tracked publicly, no exceptions",
+                "tone": "default",
+              },
+            ],
+        },
+    },
+    {
+      "id": "installed-capabilities",
+      "type": "items",
+      "data":
+        {
+          "headline": "What ships today: the Installed capabilities",
+          "description": "Ten capabilities, in the repo, running on our own sites right now.",
+          "columns": 2,
+          "items":
+            [
+              {
+                "title": "Typed schema registry",
+                "description": "Sixty page types, each with its own Zod validation and JSON-LD builder generated straight from frontmatter. Ship a page and the schema markup ships with it — no separate plugin, no manual JSON-LD authoring.",
+              },
+              {
+                "title": "FAQ, glossary, and entity markup",
+                "description": "Organization, Person, and LocalBusiness identity markup, plus FAQ and glossary schema, are native to the page types. The structure a model needs to attribute a page to a brand is built in before you write a word of content.",
+              },
+              {
+                "title": "Peer-surfaces architecture",
+                "description": "Three apps in one repo — `apps/web` for humans, `apps/mcp` for agents, `apps/api` for programmatic callers. CI checks the parity between all three on every commit; a mismatch fails the build instead of shipping quietly.",
+              },
+              {
+                "title": "First-class MCP server",
+                "description": "Agents call AILK the same way a human browses it. The MCP server exposes the site's capabilities as typed tools, tested against the same parity suite as the web UI on every commit.",
+              },
+              {
+                "title": "`ailk audit` CLI",
+                "description": "Run it pre-launch and again in CI on every pull request. It flags the missing schema, the ambiguous entity, and the page with no JSON-LD while there's still time to fix it — the alternative is hearing about it from a client.",
+              },
+              {
+                "title": "Apache 2.0 license",
+                "description": "The entire OSS layer is Apache 2.0. No source-available carve-out, no license that flips once you start making money. Paid tiers add capability on top; what's already in the repo stays there.",
+              },
+              {
+                "title": "`create-ailk` scaffolder",
+                "description": "One command generates the three-peer-app skeleton — web, MCP, API — wired and ready to deploy. What used to take a senior developer a setup sprint now takes one terminal command.",
+              },
+              {
+                "title": "The `.claude/` agent-skill bundle",
+                "description": "Eight named skills — `extract-design-from-reference`, `suggest-site-pages`, `scaffold-page`, `add-schema`, `audit-site`, `scaffold-auth`, `scaffold-commerce`, `provision-config` — ship with the repo so an agent can carry setup and iteration work end to end.",
+              },
+              {
+                "title": "JSON-LD emission from frontmatter",
+                "description": "Structured data compiles straight from the MDX frontmatter you already write. There's no separate config file to keep in sync — the content and the markup describing it live in the same place.",
+              },
+              {
+                "title": "Working Theory integration surface",
+                "description": "AILK stands alone for developers and agencies. For customers who also run Working Theory Platform, the two publish into the same substrate with the deepest integration available — better together, never required.",
+              },
+            ],
+        },
+    },
+    {
+      "id": "platform-services",
+      "type": "items",
+      "data":
+        {
+          "headline": "What's coming: the Platform Services roster",
+          "description": "Three capabilities, scoped and scheduled, not yet in the repo.",
+          "columns": 3,
+          "items":
+            [
+              {
+                "title": "Multi-tenant entitlement (Enterprise)",
+                "description": "White-label branding, per-seat licensing, and cross-site rollup reporting — built for firms running a portfolio of client sites rather than one at a time, gated as a planned Enterprise entitlement rather than a separate tier. It's scoped, not shipped, and we're saying so plainly rather than dressing it up as available.",
+              },
+              {
+                "title": "Fleet management dashboard",
+                "description": "One screen showing every client deployment, every AEO score, and every pending update — instead of the twenty separate logins a multi-site agency juggles today. This depends on the Enterprise multi-tenant entitlement's per-seat model existing first, so it ships after that entitlement, not alongside it. Neither has a locked date yet.",
+              },
+              {
+                "title": "Pro lead-routing pipeline",
+                "description": "The system that routes a Pro trial signup straight into a sales conversation, without someone triaging the inbox by hand. We'll build it once trial volume justifies automating the handoff. Until then, every signup reaches a person — slower, but it's where the team's attention actually goes, rather than a script standing in for the real thing.",
+              },
+            ],
+        },
+    },
+    {
+      "id": "why-not-shipped",
+      "type": "objection",
+      "data":
+        {
+          "headline": "Why isn't the multi-tenant entitlement live yet?",
+          "items":
+            [
+              {
+                "objection": "Why isn't the multi-tenant entitlement live yet?",
+                "response": "Because building it before agencies told us what they needed would mean guessing at per-seat pricing, white-label scope, and rollup reporting — and shipping a v1 that doesn't match how firms actually run a portfolio of sites. We're gathering that input before it gets built, not after — reach out through the pricing page if fleet management is a requirement for your firm. Everyone else gets it built once, correctly, instead of rebuilt twice.",
+              },
+            ],
+        },
+    },
+    {
+      "id": "dogfooding-proof",
+      "type": "content-block",
+      "data":
+        {
+          "headline": "We run on the same roster we're showing you",
+          "body": "Sam Henry, Working Theory, and SalesSmyth all publish on AILK today, on the Installed capabilities listed above — not a version with extra features switched on for the team that built it. The schema registry and the peer-surfaces architecture exist in their current shape because we hit the problems those capabilities solve first, on our own sites, before shipping them to anyone else. Call it the origin of the design rather than a testimonial about it. If the `ailk audit` CLI ever produced a false pass, we'd be the first to notice — we run it against our own pages, in our own CI, before anyone outside the team does.",
+        },
+    },
+    {
+      "id": "capability-faq",
+      "type": "faq",
+      "data":
+        {
+          "headline": "Capability roster — common questions",
+          "items":
+            [
+              {
+                "question": "What's the difference between the OSS layer and the paid tiers?",
+                "answer": "The OSS layer under Apache 2.0 is structurally complete — schema registry, peer surfaces, the audit CLI, and scaffolding all ship free. Pro and Pro Plus add capability on top of that foundation. Neither tier gates access to what's already in the repo.",
+              },
+              {
+                "question": "Is the `ailk audit` CLI part of the Installed set or a Platform Service?",
+                "answer": "Installed. It ships in the OSS layer today, runs pre-launch and in CI on every pull request, and scores a site's AEO structure for free. It's one of the ten capabilities running in production right now.",
+              },
+              {
+                "question": "Will Installed capabilities ever move backward into Platform Services?",
+                "answer": "No. Once a capability ships in the OSS layer under Apache 2.0, it stays. Reversing that would break the license promise the whole roster depends on — the same promise that gives the Installed label its meaning.",
+              },
+            ],
+        },
+    },
+    {
+      "id": "final-cta",
+      "type": "cta",
+      "data":
+        {
+          "headline": "Start on what's already shipped",
+          "description": "Ten capabilities are running in production today — clone the OSS foundation and use them now, or book a Launch Service call and we deploy them for you. Managing a portfolio of client sites instead? See the Enterprise entitlement on the pricing page.",
+          "primaryCta":
+            { "label": "Clone the OSS foundation", "href": "/developers" },
+          "secondaryCta":
+            {
+              "label": "See Enterprise pricing",
+              "href": "/pricing",
+              "variant": "outline",
+            },
+        },
+    },
+  ]
+status: "Approved"
+pageKey: "LandingPage (/platform)"
+entity: "ailaunchkit"
+urlSlug: "platform"
+lastUpdated: "2026-07-06"
+pageLevelSchemaType: "LandingPage"
+---
+
+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: { "@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",
+            description: "Per user, per year",
+          },
+          {
+            "@type": "Offer",
+            name: "Pro Plus",
+            price: "449",
+            priceCurrency: "USD",
+            description: "Per user, per month",
+          },
+          {
+            "@type": "Offer",
+            name: "Launch Service",
+            price: "2495",
+            priceCurrency: "USD",
+          },
+        ],
+        contributor: [
+          {
+            "@type": "SoftwareApplication",
+            name: "Claudio Planck",
+            description:
+              "AI engineering agent contributing to architecture, code review, and implementation across the AILK substrate.",
+          },
+          {
+            "@type": "SoftwareApplication",
+            name: "Anders Stewart",
+            description:
+              "AI VP Engineering agent owning implementation strategy across the AILK substrate.",
+          },
+        ],
+      },
+      {
+        "@type": "WebPage",
+        "@id": "https://ailaunchkit.ai/platform#webpage",
+        url: "https://ailaunchkit.ai/platform",
+        name: "13 capabilities. 10 shipped. 3 planned. No blur between them.",
+        description:
+          "AILK's honest capability roster: 10 Installed capabilities shipping today, 3 Platform Services planned but not yet built — scored, not pitched.",
+        isPartOf: { "@id": "https://ailaunchkit.ai/#product" },
+        mainEntity: {
+          "@type": "ItemList",
+          name: "AILK Capability Roster",
+          numberOfItems: 13,
+          itemListElement: [
+            { "@type": "ListItem", position: 1, name: "Typed schema registry" },
+            {
+              "@type": "ListItem",
+              position: 2,
+              name: "FAQ, glossary, and entity markup",
+            },
+            {
+              "@type": "ListItem",
+              position: 3,
+              name: "Peer-surfaces architecture",
+            },
+            {
+              "@type": "ListItem",
+              position: 4,
+              name: "First-class MCP server",
+            },
+            { "@type": "ListItem", position: 5, name: "`ailk audit` CLI" },
+            { "@type": "ListItem", position: 6, name: "Apache 2.0 license" },
+            {
+              "@type": "ListItem",
+              position: 7,
+              name: "`create-ailk` scaffolder",
+            },
+            {
+              "@type": "ListItem",
+              position: 8,
+              name: "The `.claude/` agent-skill bundle",
+            },
+            {
+              "@type": "ListItem",
+              position: 9,
+              name: "JSON-LD emission from frontmatter",
+            },
+            {
+              "@type": "ListItem",
+              position: 10,
+              name: "Working Theory integration surface",
+            },
+            {
+              "@type": "ListItem",
+              position: 11,
+              name: "Multi-tenant entitlement — Enterprise (Platform Service — planned)",
+            },
+            {
+              "@type": "ListItem",
+              position: 12,
+              name: "Fleet management dashboard (Platform Service — planned)",
+            },
+            {
+              "@type": "ListItem",
+              position: 13,
+              name: "Pro lead-routing pipeline (Platform Service — planned)",
+            },
+          ],
+        },
+      },
+    ],
+  }}
+/>
+
+{/* Rendered from frontmatter `sections[]`; the MDX body is not read by the section-catalog renderer. Landed by land-section-catalog.py (#3111). */}

package/templates/content/en/LandingPage/platform.schema.json

@@ -0,0 +1,166 @@
+{
+  "@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": {
+        "@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",
+          "description": "Per user, per year"
+        },
+        {
+          "@type": "Offer",
+          "name": "Pro Plus",
+          "price": "449",
+          "priceCurrency": "USD",
+          "description": "Per user, per month"
+        },
+        {
+          "@type": "Offer",
+          "name": "Launch Service",
+          "price": "2495",
+          "priceCurrency": "USD"
+        }
+      ],
+      "contributor": [
+        {
+          "@type": "SoftwareApplication",
+          "name": "Claudio Planck",
+          "description": "AI engineering agent contributing to architecture, code review, and implementation across the AILK substrate."
+        },
+        {
+          "@type": "SoftwareApplication",
+          "name": "Anders Stewart",
+          "description": "AI VP Engineering agent owning implementation strategy across the AILK substrate."
+        }
+      ]
+    },
+    {
+      "@type": "WebPage",
+      "@id": "https://ailaunchkit.ai/platform#webpage",
+      "url": "https://ailaunchkit.ai/platform",
+      "name": "13 capabilities. 10 shipped. 3 planned. No blur between them.",
+      "description": "AILK's honest capability roster: 10 Installed capabilities shipping today, 3 Platform Services planned but not yet built — scored, not pitched.",
+      "isPartOf": {
+        "@id": "https://ailaunchkit.ai/#product"
+      },
+      "mainEntity": {
+        "@type": "ItemList",
+        "name": "AILK Capability Roster",
+        "numberOfItems": 13,
+        "itemListElement": [
+          {
+            "@type": "ListItem",
+            "position": 1,
+            "name": "Typed schema registry"
+          },
+          {
+            "@type": "ListItem",
+            "position": 2,
+            "name": "FAQ, glossary, and entity markup"
+          },
+          {
+            "@type": "ListItem",
+            "position": 3,
+            "name": "Peer-surfaces architecture"
+          },
+          {
+            "@type": "ListItem",
+            "position": 4,
+            "name": "First-class MCP server"
+          },
+          {
+            "@type": "ListItem",
+            "position": 5,
+            "name": "`ailk audit` CLI"
+          },
+          {
+            "@type": "ListItem",
+            "position": 6,
+            "name": "Apache 2.0 license"
+          },
+          {
+            "@type": "ListItem",
+            "position": 7,
+            "name": "`create-ailk` scaffolder"
+          },
+          {
+            "@type": "ListItem",
+            "position": 8,
+            "name": "The `.claude/` agent-skill bundle"
+          },
+          {
+            "@type": "ListItem",
+            "position": 9,
+            "name": "JSON-LD emission from frontmatter"
+          },
+          {
+            "@type": "ListItem",
+            "position": 10,
+            "name": "Working Theory integration surface"
+          },
+          {
+            "@type": "ListItem",
+            "position": 11,
+            "name": "Multi-tenant entitlement — Enterprise (Platform Service — planned)"
+          },
+          {
+            "@type": "ListItem",
+            "position": 12,
+            "name": "Fleet management dashboard (Platform Service — planned)"
+          },
+          {
+            "@type": "ListItem",
+            "position": 13,
+            "name": "Pro lead-routing pipeline (Platform Service — planned)"
+          }
+        ]
+      }
+    }
+  ]
+}

package/templates/content/en/LandingPage/vs-ai-website-builders.mdx

@@ -0,0 +1,19 @@
+---
+type: "LandingPage"
+slug: "vs-ai-website-builders"
+title: "AI-generated isn't AI-ready."
+description: "Wix AI and Durable generate sites. AI Launch Kit builds AI-ready ones — schema, agent-readable surfaces, and pre-launch AEO scoring, Apache 2.0."
+sections: [{"id": "hero", "type": "hero", "data": {"badge": "Sam Henry, Working Theory, and SalesSmyth all publish on this foundation.", "headline": "AI-generated isn't AI-ready.", "subheadline": "Wix AI, Hostinger AI, and Durable generate a site fast. None of them ship the schema, the agent-readable surface, or the pre-launch AEO check. Those are what make a site legible to the systems now doing the recommending.", "body": "AI Launch Kit ships all three as defaults — Apache 2.0, audited before launch, and used to publish this page.", "primaryCta": {"label": "Book Launch Service call", "href": "/launch-service"}, "secondaryCta": {"label": "Read the foundation overview", "href": "/ailk", "variant": "outline"}}}, {"id": "what-is-ai-website-builder", "type": "content-block", "data": {"headline": "What is an AI website builder, and where does it fall short?", "body": "An AI website builder is a tool that generates a complete website from a text prompt — Wix AI, Hostinger AI, Durable, and 10Web all work this way. You describe your business, the tool assembles pages, and a working site is live within minutes.\n\nThat speed is real, and it solves a genuine problem for non-technical owners who need something online today. The tool is good at layout and first-draft copy — capable enough to get a business off a blank page.\n\nWhere it falls short is what happens after the button is clicked. The output is frozen at the moment it's generated — built to be scrolled by a human, not read by a model. Most AI-generated sites carry weak or absent schema markup, with no way for an AI agent to query the business's offerings directly. Nothing measures whether the page is structured well enough to be cited when a buyer asks ChatGPT or Perplexity for a recommendation.\n\nThe distinction matters because the audience for a website has split. Buyers still visit pages, but AI systems now read pages on buyers' behalf before a human ever clicks through. The brand that gets recommended is the brand whose pages the model trusted enough to cite. An AI-generated site optimizes for the moment it's created. It says nothing about whether the result still works for the audience reading it six months later."}}, {"id": "ai-generated-vs-ai-ready", "type": "objection", "data": {"headline": "AI-generated vs. AI-ready: what's the actual difference?", "items": [{"objection": "\"It says AI, so it must already be optimized for AI search.\"", "response": "No — generation and legibility are two different problems, and an AI website builder only solves the first. Being 'AI-generated' means a model wrote the copy and assembled the layout. Being 'AI-ready' means the resulting page can be read, attributed to your business, and trusted enough to quote by the AI systems that now do discovery on a buyer's behalf.\n\nThose are structural properties, not marketing claims. A typed schema registry tells a model exactly what a page is and which business it belongs to, while an agent-readable surface lets a buyer's AI assistant query the business directly instead of scraping and guessing. A pre-launch check scores whether the structure is right before the site goes live — not three months later, when the business notices it's invisible in an AI answer.\n\nWix AI, Hostinger AI, and Durable generate the page. None of them ship the schema layer, the agent surface, or the pre-launch score that make it legible to the systems doing the reading. On AI Launch Kit, all three come standard, not bolted on afterward. The page, not the site, is the unit of citation now — and a page nobody can read correctly doesn't get cited."}]}}, {"id": "wix-ai-vs-ailk", "type": "comparison-table", "data": {"headline": "Wix AI vs. AILK: which should you choose?", "eyebrow": "The foundation, side by side", "description": "If you need a site online in minutes and never plan to touch AI search visibility, an AI website builder gets you there. If AI search recommendations matter to your business, the foundation underneath the site is the difference.", "columns": [{"key": "wixai", "name": "Wix AI / Hostinger AI / Durable"}, {"key": "ailk", "name": "AI Launch Kit", "highlighted": true}], "groups": [{"groupName": "The foundation", "rows": [{"featureName": "Structured data / schema markup", "values": {"wixai": "Minimal or absent", "ailk": "60 typed page schemas, built in"}}, {"featureName": "Agent-readable surface", "values": {"wixai": false, "ailk": "Ships as a default, not an add-on"}}, {"featureName": "Pre-launch AEO scoring", "values": {"wixai": false, "ailk": "Runs before launch and in CI on every change"}}, {"featureName": "Ownership / license", "values": {"wixai": "Closed, vendor-hosted", "ailk": "Apache 2.0 — you own the code"}}, {"featureName": "Deploy speed", "values": {"wixai": "Minutes to a first draft", "ailk": "Days, agent-assisted, to a live site"}}, {"featureName": "Vendor lock-in", "values": {"wixai": true, "ailk": false}}]}], "footnote": "Deploy speed reflects a working, reviewed site — not the first generated draft."}}, {"id": "capabilities-ailk-ships", "type": "items", "data": {"headline": "What AILK ships that AI-generated builders don't", "columns": 2, "items": [{"title": "A typed schema registry, built in", "description": "60 page types, each validated and emitting the structured data an AI system needs to identify what a page is and which business it belongs to. No plugin stack to maintain — the schema ships with the page."}, {"title": "A surface agents can call directly", "description": "Every capability works for a human visitor and for an AI agent acting on a buyer's behalf — the same coverage, enforced automatically before anything ships."}, {"title": "A pre-launch AEO check", "description": "Enterprise AEO platforms charge $295 a month or more to measure citation problems after they've already cost the business citations. AILK's audit runs before launch and again on every change — free, built into the foundation."}, {"title": "Apache 2.0, completely", "description": "The foundation is fully open source — no trial, no feature cut at a certain size. Paid tiers add capability. They never gate access to the substrate itself."}, {"title": "Agent-assisted setup and iteration", "description": "Scaffolding a project, adding a schema, adding a new page — all guided agent workflows. What used to require a senior developer and weeks of setup now takes days, and stays that fast after launch."}]}}, {"id": "isnt-ai-builder-faster", "type": "objection", "data": {"headline": "Isn't an AI-generated site faster to launch?", "items": [{"objection": "\"Isn't an AI-generated site just faster to launch?\"", "response": "Generation is faster. Launch is not — and the two are different clocks. An AI website builder can produce a first draft in minutes. But a business still has to review it, fix the parts the model got wrong, and connect it to real content, real pricing, and a real domain. That work takes days regardless of which tool generated the starting point.\n\nAI Launch Kit's agent-assisted scaffolding closes most of that gap on the front end. The project skeleton, the schema, and the initial page set are handled by a guided agent workflow, rather than a senior developer starting from a blank repository. The AILK Launch Service turns that into a fixed two-week deploy, not an open-ended custom build.\n\nThe difference shows up after launch, not before it. On an AI-generated site, adding a new service page or fixing a citation gap means going back through the same generation-and-review cycle. On AILK, the marginal cost of a page approaches zero — a Claude Code session, not a project. The speed that matters is the speed of the tenth page, not the first."}]}}, {"id": "faq", "type": "faq", "data": {"headline": "Common questions about AI-generated builders vs. AILK", "items": [{"question": "Will my Wix AI or Durable site show up in ChatGPT answers?", "answer": "Not reliably, and not because the writing is bad. Most AI-generated sites carry little or no structured markup, so an AI system reading the page has nothing to attribute the content to. Citation depends on the model trusting the page's structure enough to quote it — a property the generation process itself doesn't produce."}, {"question": "Can I migrate an AI-generated site to AILK?", "answer": "Yes. Content and copy transfer directly; what changes is the foundation underneath it. AILK's Launch Service rebuilds the site on the typed schema registry and agent-readable surface, in a fixed two-week engagement. That gives the migration a defined start and end, rather than an open-ended rebuild."}, {"question": "Is AILK also AI-generated?", "answer": "No. AILK is a foundation you or your agency build on, with agent-assisted scaffolding handling the setup work — not a tool that generates a finished site from a prompt. The output is a codebase you own under Apache 2.0, not a hosted result you rent."}, {"question": "What does \"agent-ready\" actually mean?", "answer": "It means an AI agent acting on a buyer's behalf — a different kind of visitor than a search crawler — can read the page, identify the business, and query its offerings directly. It gets the same coverage a human visitor does. That requires an agent-readable surface built into the foundation, which AI-generated builders don't ship."}]}}, {"id": "final-cta", "type": "cta", "data": {"headline": "Ready to build on a foundation AI search can actually read?", "description": "AI Launch Kit is the open-source foundation built for the agent-first internet — Apache 2.0, agent-ready, AEO-scored, deployable in days. Book a Launch Service call and we'll scope a two-week deploy.", "primaryCta": {"label": "Book Launch Service call", "href": "/launch-service"}, "secondaryCta": {"label": "Read the foundation overview", "href": "/ailk", "variant": "ghost"}}}]
+status: "Approved"
+pageKey: "WebPage (/vs/ai-website-builders)"
+entity: "ailaunchkit"
+urlSlug: "vs-ai-website-builders"
+lastUpdated: "2026-07-06"
+pageLevelSchemaType: "LandingPage"
+---
+
+import { JsonLd } from '@/components/JsonLd'
+
+<JsonLd data={{"@context": "https://schema.org", "@graph": [{"@type": "Product", "@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", "manufacturer": {"@type": "Organization", "@id": "https://ailaunchkit.ai/#salessmyth", "name": "SalesSmyth LLC"}, "brand": {"@type": "Brand", "@id": "https://workingtheory.ai/#organization", "name": "Working Theory", "url": "https://workingtheory.ai"}, "creator": {"@type": "Person", "@id": "https://samhenry.org/#person", "name": "Sam Henry"}, "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", "additionalType": "https://schema.org/SoftwareApplication"}, {"@type": "WebPage", "@id": "https://ailaunchkit.ai/vs/ai-website-builders#webpage", "url": "https://ailaunchkit.ai/vs/ai-website-builders", "name": "AI-generated isn't AI-ready.", "description": "Wix AI and Durable generate sites. AI Launch Kit builds AI-ready ones — schema, agent-readable surfaces, and pre-launch AEO scoring, Apache 2.0.", "isPartOf": {"@id": "https://ailaunchkit.ai/#product"}, "about": {"@id": "https://ailaunchkit.ai/#product"}, "mainEntity": {"@type": "FAQPage", "@id": "https://ailaunchkit.ai/vs/ai-website-builders#faq", "mainEntity": [{"@type": "Question", "name": "Will my Wix AI or Durable site show up in ChatGPT answers?", "acceptedAnswer": {"@type": "Answer", "text": "Not reliably, and not because the writing is bad. Most AI-generated sites carry little or no structured markup, so an AI system reading the page has nothing to attribute the content to. Citation depends on the model trusting the page's structure enough to quote it — a property the generation process itself doesn't produce."}}, {"@type": "Question", "name": "Can I migrate an AI-generated site to AILK?", "acceptedAnswer": {"@type": "Answer", "text": "Yes. Content and copy transfer directly; what changes is the foundation underneath it. AILK's Launch Service rebuilds the site on the typed schema registry and agent-readable surface, in a fixed two-week engagement. That gives the migration a defined start and end, rather than an open-ended rebuild."}}, {"@type": "Question", "name": "Is AILK also AI-generated?", "acceptedAnswer": {"@type": "Answer", "text": "No. AILK is a foundation you or your agency build on, with agent-assisted scaffolding handling the setup work — not a tool that generates a finished site from a prompt. The output is a codebase you own under Apache 2.0, not a hosted result you rent."}}, {"@type": "Question", "name": "What does \"agent-ready\" actually mean?", "acceptedAnswer": {"@type": "Answer", "text": "It means an AI agent acting on a buyer's behalf — a different kind of visitor than a search crawler — can read the page, identify the business, and query its offerings directly. It gets the same coverage a human visitor does. That requires an agent-readable surface built into the foundation, which AI-generated builders don't ship."}}]}}]}} />
+
+{/* Rendered from frontmatter `sections[]`; the MDX body is not read by the section-catalog renderer. Landed by land-section-catalog.py (#3111). */}