create-ailk 0.1.0 → 0.2.0

package/templates/content/en/HowTo/configure-aeo-scoring.mdx

@@ -1,35 +0,0 @@
----
-type: HowTo
-slug: configure-aeo-scoring
-title: How to Configure AEO Scoring
-description: Run the deterministic AEO scorer against your site's pages and interpret the Layer 1 citation-readiness output.
-publishedAt: "2026-05-10"
----
-
-# How to Configure AEO Scoring
-
-`@working-theory/aeo` grades pages against Layer 1 citation-readiness rules. The scorer is deterministic — the same input always returns the same score, with no network calls.
-
-## Step 1 — Install `@working-theory/aeo`
-
-```bash
-pnpm add @working-theory/aeo
-```
-
-## Step 2 — Run the scorer
-
-Pass a `ContentPage` (from the content adapter) to `scoreAeo`:
-
-```ts
-import { scoreAeo } from "@working-theory/aeo";
-const result = scoreAeo(page);
-console.log(result.score, result.findings);
-```
-
-## Step 3 — Interpret findings
-
-Each finding has a `rule`, a `severity` (`error` | `warning` | `info`), and a `message`. Errors block the Layer 1 passing threshold; warnings are informational.
-
-## Step 4 — Fix and re-score
-
-Add missing frontmatter fields (most commonly `publishedAt`, `image`, or a `schema` override). Re-run the scorer until `result.passing` is `true`.

package/templates/content/en/HowTo/set-up-json-ld.mdx

@@ -1,36 +0,0 @@
----
-type: HowTo
-slug: set-up-json-ld
-title: How to Set Up JSON-LD with AI Launch Kit
-description: A step-by-step guide to enabling structured data on your AILK site — from package install to validated schema.org output.
-publishedAt: "2026-05-01"
----
-
-# How to Set Up JSON-LD with AI Launch Kit
-
-Structured data tells answer engines what your pages are about. This guide walks through adding JSON-LD to every page in an AILK site.
-
-## Step 1 — Install `@working-theory/schema`
-
-`@working-theory/schema` ships the typed JSON-LD builders. Add it to your workspace:
-
-```bash
-pnpm add @working-theory/schema
-```
-
-## Step 2 — Add a content directory
-
-Create `content/en/<Type>/` directories for each page type you want to support. Drop an MDX file inside with the required frontmatter fields:
-
-- `type` — the schema.org type key (e.g. `HowTo`)
-- `slug` — the URL segment
-- `title` — page title
-- `description` — one-sentence description
-
-## Step 3 — Wire the route
-
-Create a Next.js route at `app/[locale]/<path>/[slug]/page.tsx`. Import `getMdxSource` from the content lib and `pageToJsonLd` from the JSON-LD bridge. Return a `<JsonLdScript>` alongside your `<main>` element.
-
-## Step 4 — Verify
-
-Run `pnpm preflight`. The type-check step validates that every MDX frontmatter field matches the content adapter's type contract. The build step confirms Next.js can prerender the route.

package/templates/content/en/Integration/github-actions.mdx

@@ -1,31 +0,0 @@
----
-type: Integration
-slug: github-actions
-title: GitHub Actions
-description: Run pnpm preflight, content validation, and AEO scoring automatically on every pull request via GitHub Actions CI.
-schema:
-  mainEntity:
-    "@type": SoftwareApplication
-    name: GitHub Actions
-    applicationCategory: DeveloperTools
-    operatingSystem: Web
----
-
-# GitHub Actions
-
-AILK ships a ready-to-use CI configuration for GitHub Actions. Every pull request runs the full preflight suite: architecture lint, type-check, content validation, and AEO scoring.
-
-## What runs in CI
-
-- `pnpm architecture` — import boundary lint against `architecture.yaml`
-- `pnpm content:check` — MDX frontmatter validation
-- `pnpm --filter @working-theory/web build` — Next.js build verification
-- `pnpm -r test` — full test suite
-
-## Setting up
-
-Copy `.github/workflows/ci.yml` from the AILK template into your repo. The workflow uses `pnpm` caching by default — first runs are slower, subsequent runs pick up the cache.
-
-## AEO regression gate
-
-Add the `@working-theory/aeo` scoring step to your workflow to catch citation-readiness regressions before they ship. The scorer exits non-zero when a page's score drops below its baseline.

package/templates/content/en/Integration/openai-api.mdx

@@ -1,26 +0,0 @@
----
-type: Integration
-slug: openai-api
-title: OpenAI API
-description: Connect AILK-powered sites to OpenAI's API for agent-driven content generation, structured extraction, and answer-engine query routing.
-schema:
-  mainEntity:
-    "@type": SoftwareApplication
-    name: OpenAI API
-    applicationCategory: ArtificialIntelligence
-    operatingSystem: Web
----
-
-# OpenAI API
-
-AILK's MCP server exposes tool definitions that map directly to OpenAI function-calling conventions. Connect your OpenAI-powered agents to AILK data without writing custom adapters.
-
-## What the integration covers
-
-- **Structured extraction** — pass MDX body text through an OpenAI model to extract structured data; write the result back as frontmatter fields
-- **Agent query routing** — route natural-language queries from an OpenAI agent to the correct AILK content type via the MCP tool surface
-- **Schema generation assist** — use a model to suggest schema.org field values from unstructured page content
-
-## Getting started
-
-Set `OPENAI_API_KEY` in your `.env`. Import the client from `@working-theory/api-client` and call `createAgentSession()` to get a session bound to your OpenAI credentials.

package/templates/content/en/Integration/vercel.mdx

@@ -1,32 +0,0 @@
----
-type: Integration
-slug: vercel
-title: Vercel
-description: Deploy AILK-powered Next.js sites to Vercel with zero configuration — environment variable mapping, preview deployment URLs, and edge-runtime compatibility.
-schema:
-  mainEntity:
-    "@type": SoftwareApplication
-    name: Vercel
-    applicationCategory: DeveloperTools
-    operatingSystem: Web
----
-
-# Vercel
-
-AILK's `apps/web` is a standard Next.js application and deploys to Vercel without modification. The `vercel.json` in the template configures preview URL patterns and environment variable mappings.
-
-## Environment variables
-
-Map these from your Vercel project settings:
-
-- `DATABASE_URL` — your Prisma connection string
-- `NEXTAUTH_SECRET` — a random 32-byte secret for session signing
-- `NEXTAUTH_URL` — your production URL (or preview URL for branch deployments)
-
-## Preview deployments
-
-Every pull request gets a unique preview URL. AILK's `verify-preview` script can optionally run Playwright smoke tests against the preview URL before merge.
-
-## Edge compatibility
-
-The MCP server (`apps/mcp`) is not edge-compatible and should be deployed separately as a standard Node.js server. `apps/web` and `apps/api` are edge-compatible and run in Vercel's edge runtime.

package/templates/content/en/IntegrationsList/integrations.mdx

@@ -1,22 +0,0 @@
----
-type: IntegrationsList
-slug: integrations
-title: Integrations
-description: First-party integrations for AI Launch Kit — connect your AILK-powered site to the AI providers, CI platforms, and deployment targets your team already uses.
----
-
-# Integrations
-
-AILK is built to work alongside the tools your team already uses. These integrations cover the most common connection points: AI providers, CI pipelines, and deployment platforms.
-
-## AI providers
-
-Connect to OpenAI, Anthropic, and other model providers via the MCP tool surface. AILK's agent-compatible API routes are model-agnostic — swap providers without changing your content layer.
-
-## CI platforms
-
-GitHub Actions, CircleCI, and similar platforms can run AILK's preflight suite and AEO scoring gate on every pull request. The scoring gate exits non-zero on regression, keeping your citation readiness from drifting.
-
-## Deployment targets
-
-AILK's Next.js web app deploys to Vercel, Netlify, and self-hosted Node.js environments. The API server targets any Node.js 20+ runtime. The MCP server follows the same runtime requirement.

package/templates/content/en/JobPosting/content-strategist.mdx

@@ -1,46 +0,0 @@
----
-type: JobPosting
-slug: content-strategist
-title: Content Strategist
-description: Own the AILK content pipeline — how-to guides, technical articles, whitepapers, and AEO-optimized landing pages. Remote, part-time to full-time.
-publishedAt: "2026-05-05"
-schema:
-  mainEntity:
-    "@type": JobPosting
-    title: Content Strategist
-    description: Own the AILK content pipeline — how-to guides, technical articles, whitepapers, and AEO-optimized landing pages.
-    datePosted: "2026-05-05"
-    employmentType: PART_TIME
-    hiringOrganization:
-      "@type": Organization
-      name: AI Launch Kit
-    jobLocation:
-      "@type": Place
-      address:
-        "@type": PostalAddress
-        addressCountry: US
----
-
-# Content Strategist
-
-AILK ships content alongside code. We need a strategist who understands both — someone who can write a clear how-to guide and also understand why `inLanguage` matters for AEO.
-
-## What you will do
-
-- Plan and produce how-to guides, technical articles, and whitepapers
-- Optimize existing content for Layer 1 AEO citation-readiness
-- Work with the engineering team to document new features as they ship
-- Develop a content calendar aligned with roadmap phases
-
-## What we are looking for
-
-- Strong technical writing — you can explain APIs to developers clearly
-- Curiosity about structured data, schema.org, and answer engine optimization
-- Comfort working asynchronously with a small, distributed team
-- Portfolio of published technical content (blog posts, docs, guides)
-
-## What we offer
-
-- Flexible hours — part-time to full-time based on your availability
-- Fully remote
-- Direct access to the product team for research and context

package/templates/content/en/JobPosting/developer-advocate.mdx

@@ -1,47 +0,0 @@
----
-type: JobPosting
-slug: developer-advocate
-title: Developer Advocate
-description: Help the AILK community succeed — talks, workshops, demos, and the open-source feedback loop between users and the core team.
-publishedAt: "2026-05-10"
-schema:
-  mainEntity:
-    "@type": JobPosting
-    title: Developer Advocate
-    description: Help the AILK community succeed — talks, workshops, demos, and the open-source feedback loop between users and the core team.
-    datePosted: "2026-05-10"
-    employmentType: FULL_TIME
-    hiringOrganization:
-      "@type": Organization
-      name: AI Launch Kit
-    jobLocation:
-      "@type": Place
-      address:
-        "@type": PostalAddress
-        addressCountry: US
----
-
-# Developer Advocate
-
-AILK's community is growing. We need an advocate who can represent the project externally, help developers succeed with the template, and bring real usage patterns back into the product roadmap.
-
-## What you will do
-
-- Give talks and run workshops on AX-first development and structured data
-- Produce demo projects and example integrations
-- Triage community issues and PRs with the engineering team
-- Write blog posts and guides that show AILK solving real problems
-- Represent AILK at developer conferences
-
-## What we are looking for
-
-- Experience in developer relations, developer education, or technical content
-- Comfort on stage and in front of a camera
-- Genuine interest in structured data, AEO, and agent-era product patterns
-- Ability to build and ship small demo projects independently
-
-## What we offer
-
-- Competitive salary + conference travel budget
-- Fully remote with flexibility to attend events
-- Direct input into product direction from community feedback

package/templates/content/en/JobPosting/senior-fullstack-engineer.mdx

@@ -1,57 +0,0 @@
----
-type: JobPosting
-slug: senior-fullstack-engineer
-title: Senior Full-Stack Engineer
-description: Build the AILK platform — schema builders, content adapters, and the Next.js web app. TypeScript-first, test-driven, remote-friendly.
-publishedAt: "2026-05-01"
-schema:
-  mainEntity:
-    "@type": JobPosting
-    title: Senior Full-Stack Engineer
-    description: Build and extend the AILK platform — schema builders, content adapters, and the Next.js web app. TypeScript-first, test-driven, remote-friendly.
-    datePosted: "2026-05-01"
-    employmentType: FULL_TIME
-    hiringOrganization:
-      "@type": Organization
-      name: AI Launch Kit
-    jobLocation:
-      "@type": Place
-      address:
-        "@type": PostalAddress
-        addressCountry: US
-    baseSalary:
-      "@type": MonetaryAmount
-      currency: USD
-      value:
-        "@type": QuantitativeValue
-        minValue: 150000
-        maxValue: 200000
-        unitText: YEAR
----
-
-# Senior Full-Stack Engineer
-
-We are looking for a senior engineer to join the core AILK team. You will own features end-to-end — from schema builder design to Next.js route implementation to CI green.
-
-## What you will do
-
-- Design and implement new schema.org builders in `@working-theory/schema`
-- Build Next.js routes and content adapter extensions
-- Write tests first (TDD is the default, not the exception)
-- Review PRs and mentor junior contributors
-- Participate in architecture decisions
-
-## What we are looking for
-
-- 5+ years of TypeScript in production
-- Experience with Next.js App Router and React Server Components
-- Familiarity with schema.org, structured data, or AEO a plus
-- Strong testing discipline — you reach for tests before implementation
-- Clear written communication (we are async-first)
-
-## What we offer
-
-- Competitive salary ($150k–$200k depending on experience)
-- Fully remote, async-first culture
-- Meaningful equity in a growing OSS business
-- Access to the full AILK toolchain from day one

package/templates/content/en/LandingPage/aeo-audit.mdx

@@ -1,19 +0,0 @@
----
-type: "LandingPage"
-slug: "aeo-audit"
-title: "Score your AEO structure before your site ships."
-description: "See what ailk audit checks before your site ships — free, in the Apache 2.0 foundation, running the same schema and structured-data checks enterprise AEO platforms charge to run after launch."
-sections: [{"id": "hero", "type": "hero", "data": {"badge": "Free in the Apache 2.0 foundation — runs pre-launch and in CI", "headline": "Score your AEO structure before your site ships.", "subheadline": "ailk audit runs the same schema and structured-data checks in your terminal and in CI. Free, in the Apache 2.0 foundation. Catches a missing schema or an unscored page before it costs a citation.", "primaryCta": {"label": "Clone the OSS", "href": "https://github.com/working-theory-labs/ai-launch-kit", "external": true, "variant": "default"}, "secondaryCta": {"label": "Read about the foundation", "href": "/ailk", "external": false, "variant": "ghost"}}}, {"id": "insight-bridge", "type": "content-block", "data": {"headline": "The page is the unit of citation, not the site.", "body": "When an AI system recommends a business, it read pages, attributed them to a brand, and quoted what it trusted enough to cite. A site can rank well, load fast, and still never get quoted, because the page itself didn't carry the structure a model needs to identify the brand behind it and trust the claim.\n\nThat structure is checkable. Missing schema. Ambiguous entity markup. A page that never emits JSON-LD. These are AEO problems, and AEO problems are silent — the site doesn't crash, it just doesn't get cited, and nothing tells you why.\n\nailk audit exists to make that failure loud instead of silent. It runs against the typed schema registry every AILK page ships with, checking the structural properties a model relies on to extract and attribute a claim. It reports the gaps before the site goes live, not three months after an agency notices the client stopped showing up in AI answers."}}, {"id": "what-it-measures", "type": "feature", "data": {"headline": "ailk audit checks the structural properties AI systems need to cite a page.", "description": "It runs against AILK's typed schema registry of 60 page-type entries, scoring each page for the specific things a model looks for before it trusts a claim enough to quote it.", "features": [{"title": "Schema presence and validity", "description": "Confirms each page type carries the right JSON-LD, validated per-type against the typed registry — not a generic schema stub."}, {"title": "Entity clarity", "description": "Flags a page where the brand behind the claim isn't unambiguous, the exact gap that leaves a model unable to attribute what it's reading."}, {"title": "JSON-LD emission", "description": "Verifies the page actually emits the markup at build time, not just that the frontmatter intends to."}, {"title": "FAQ and glossary structure", "description": "Checks that FAQ and glossary content is marked up so it's extractable as a direct answer, not buried in undifferentiated prose."}]}}, {"id": "audit-checks-list", "type": "items", "data": {"headline": "What a failed check actually looks like", "description": "Four failure patterns ailk audit is built to catch — the ones that cost a citation without ever throwing an error.", "columns": 2, "items": [{"title": "The missing schema", "description": "A page ships without the JSON-LD its page type requires. It renders fine for a human visitor and stays invisible to a model deciding what to cite."}, {"title": "The ambiguous entity", "description": "A page never clearly states which brand it belongs to. A model reading it can't attribute the claim, so it looks elsewhere for a source it can name."}, {"title": "The silent JSON-LD failure", "description": "The frontmatter is correct, but the build step never emits the markup. Nothing breaks visibly; the page just quietly stops being structured data."}, {"title": "The unscored page", "description": "A page gets added after the last audit runs and never gets checked. In CI, this is the exact gap the parity and schema checks catch automatically."}]}}, {"id": "vs-enterprise-aeo", "type": "comparison-table", "data": {"eyebrow": "The structural difference", "headline": "Pre-launch and free, instead of post-hoc and paid", "description": "Enterprise AEO platforms charge $295 or more a month to measure whether a site is already being cited, after the structural gap has already cost the citation. ailk audit measures the structure itself, before the site ships.", "columns": [{"key": "ailk", "name": "ailk audit", "highlighted": true}, {"key": "enterprise", "name": "Enterprise AEO platform"}], "groups": [{"groupName": "What it measures and when", "rows": [{"featureName": "Cost", "values": {"ailk": "Free, in the Apache 2.0 OSS", "enterprise": "$295+/month"}}, {"featureName": "When it runs", "values": {"ailk": "Pre-launch and in CI, on every change", "enterprise": "Post-launch, after citations are already lost"}}, {"featureName": "What it measures", "values": {"ailk": "Structural readiness — schema, entity clarity, JSON-LD emission", "enterprise": "Citation share and prompt-level visibility, after the fact"}}, {"featureName": "License", "values": {"ailk": "Apache 2.0 — complete, not gated", "enterprise": "Proprietary, subscription-gated"}}]}], "footnote": "The two aren't the same tool. Post-hoc citation tracking still has value once a site is live. ailk audit's job is making sure the structure is right before that tracking ever starts."}}, {"id": "why-free-in-oss", "type": "content-block", "data": {"headline": "Structural readiness isn't a premium feature.", "body": "AILK's OSS layer is Apache 2.0 — not source-available, not free-until-you-make-money. It isn't deliberately limited so a paid tier can earn. Paid tiers on AILK add capability. They don't gate access, and a structural AEO check is access, not capability.\n\nThat's why ailk audit ships in the free foundation and runs in CI on every change, not behind a login. A developer or an AEO-practitioner agency should be able to verify the structure is right without a subscription standing between them and the answer."}}, {"id": "page-faq", "type": "faq", "data": {"headline": "Common questions about ailk audit", "items": [{"question": "Is ailk audit different from a schema markup validator?", "answer": "Yes. A schema markup validator checks whether existing JSON-LD is syntactically correct. ailk audit checks something upstream of that: whether the right schema exists at all for a given page type, whether it's emitted at build time, and whether the entity behind the page is unambiguous. It's a structural readiness check, not a syntax check."}, {"question": "Does ailk audit replace a structured data testing tool?", "answer": "It complements one. A structured data testing tool validates a single page's markup after the fact. ailk audit runs across the whole site, pre-launch and in CI, against AILK's typed schema registry, so gaps get caught before a page ships rather than found one URL at a time afterward."}, {"question": "What does 'AEO scoring' mean in ailk audit's output?", "answer": "The score reflects structural readiness for AI-mediated discovery: schema presence, entity clarity, and JSON-LD emission per page type. It's not citation volume or ranking position. It answers whether the page is built so a model can read and attribute it, not how often the page is already being cited."}, {"question": "Can I run an AI search audit against a site I don't own?", "answer": "ailk audit is built to run against any AILK site, including this one, since it checks structure that's already public in the rendered page and its JSON-LD. Running it against a non-AILK site isn't the intended use case; the checks are built against AILK's typed schema registry, not a generic crawler."}]}}, {"id": "closing-cta", "type": "cta", "data": {"headline": "Clone the OSS and run your first audit.", "description": "ailk audit ships in the Apache 2.0 foundation. Clone the repo, scaffold a site, and run the check before you ship the first page, not after you notice you're invisible.", "primaryCta": {"label": "Clone the OSS", "href": "https://github.com/working-theory-labs/ai-launch-kit", "external": true, "variant": "default"}}}]
-status: "Approved"
-pageKey: "WebPage (/aeo-audit)"
-entity: "ailaunchkit"
-urlSlug: "aeo-audit"
-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"}}, {"@type": "WebPage", "@id": "https://ailaunchkit.ai/aeo-audit#webpage", "url": "https://ailaunchkit.ai/aeo-audit", "name": "Score your AEO structure before your site ships.", "description": "See what ailk audit checks before your site ships — free, in the Apache 2.0 foundation, running the same schema and structured-data checks enterprise AEO platforms charge to run after launch.", "isPartOf": {"@id": "https://ailaunchkit.ai/#product"}, "mainEntity": {"@type": "FAQPage", "@id": "https://ailaunchkit.ai/aeo-audit#faq", "mainEntity": [{"@type": "Question", "name": "Is ailk audit different from a schema markup validator?", "acceptedAnswer": {"@type": "Answer", "text": "Yes. A schema markup validator checks whether existing JSON-LD is syntactically correct. ailk audit checks something upstream of that: whether the right schema exists at all for a given page type, whether it's emitted at build time, and whether the entity behind the page is unambiguous. It's a structural readiness check, not a syntax check."}}, {"@type": "Question", "name": "Does ailk audit replace a structured data testing tool?", "acceptedAnswer": {"@type": "Answer", "text": "It complements one. A structured data testing tool validates a single page's markup after the fact. ailk audit runs across the whole site, pre-launch and in CI, against AILK's typed schema registry, so gaps get caught before a page ships rather than found one URL at a time afterward."}}, {"@type": "Question", "name": "What does 'AEO scoring' mean in ailk audit's output?", "acceptedAnswer": {"@type": "Answer", "text": "The score reflects structural readiness for AI-mediated discovery: schema presence, entity clarity, and JSON-LD emission per page type. It's not citation volume or ranking position. It answers whether the page is built so a model can read and attribute it, not how often the page is already being cited."}}, {"@type": "Question", "name": "Can I run an AI search audit against a site I don't own?", "acceptedAnswer": {"@type": "Answer", "text": "ailk audit is built to run against any AILK site, including this one, since it checks structure that's already public in the rendered page and its JSON-LD. Running it against a non-AILK site isn't the intended use case; the checks are built against AILK's typed schema registry, not a generic crawler."}}]}}]}} />
-
-{/* 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/aeo-audit.schema.json

@@ -1,92 +0,0 @@
-{
-  "@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"
-      }
-    },
-    {
-      "@type": "WebPage",
-      "@id": "https://ailaunchkit.ai/aeo-audit#webpage",
-      "url": "https://ailaunchkit.ai/aeo-audit",
-      "name": "Score your AEO structure before your site ships.",
-      "description": "See what ailk audit checks before your site ships — free, in the Apache 2.0 foundation, running the same schema and structured-data checks enterprise AEO platforms charge to run after launch.",
-      "isPartOf": {
-        "@id": "https://ailaunchkit.ai/#product"
-      },
-      "mainEntity": {
-        "@type": "FAQPage",
-        "@id": "https://ailaunchkit.ai/aeo-audit#faq",
-        "mainEntity": [
-          {
-            "@type": "Question",
-            "name": "Is ailk audit different from a schema markup validator?",
-            "acceptedAnswer": {
-              "@type": "Answer",
-              "text": "Yes. A schema markup validator checks whether existing JSON-LD is syntactically correct. ailk audit checks something upstream of that: whether the right schema exists at all for a given page type, whether it's emitted at build time, and whether the entity behind the page is unambiguous. It's a structural readiness check, not a syntax check."
-            }
-          },
-          {
-            "@type": "Question",
-            "name": "Does ailk audit replace a structured data testing tool?",
-            "acceptedAnswer": {
-              "@type": "Answer",
-              "text": "It complements one. A structured data testing tool validates a single page's markup after the fact. ailk audit runs across the whole site, pre-launch and in CI, against AILK's typed schema registry, so gaps get caught before a page ships rather than found one URL at a time afterward."
-            }
-          },
-          {
-            "@type": "Question",
-            "name": "What does 'AEO scoring' mean in ailk audit's output?",
-            "acceptedAnswer": {
-              "@type": "Answer",
-              "text": "The score reflects structural readiness for AI-mediated discovery: schema presence, entity clarity, and JSON-LD emission per page type. It's not citation volume or ranking position. It answers whether the page is built so a model can read and attribute it, not how often the page is already being cited."
-            }
-          },
-          {
-            "@type": "Question",
-            "name": "Can I run an AI search audit against a site I don't own?",
-            "acceptedAnswer": {
-              "@type": "Answer",
-              "text": "ailk audit is built to run against any AILK site, including this one, since it checks structure that's already public in the rendered page and its JSON-LD. Running it against a non-AILK site isn't the intended use case; the checks are built against AILK's typed schema registry, not a generic crawler."
-            }
-          }
-        ]
-      }
-    }
-  ]
-}