@x12i/docify-docs 1.0.0 → 1.1.1

package/dist/generated/bundle.js

@@ -1,620 +0,0 @@
-/* Auto-generated by scripts/build-knowledge.mjs — do not edit */
-export const catalog = {
-    "roles": [
-        {
-            "id": "developers",
-            "label": "Developers",
-            "tagline": "Wire the platform",
-            "description": "Engineers who depend on @x12i/docify-* packages, ship product docs libraries, and publish knowledge SDKs."
-        },
-        {
-            "id": "builders",
-            "label": "Builders",
-            "tagline": "Author the library",
-            "description": "Content authors who write BOOK.md, site-pages, catalog entries, and use-case paths — without forking theme or web UI."
-        }
-    ],
-    "families": [
-        {
-            "id": "docify",
-            "name": "x12i-docify",
-            "tagline": "Product site + docs + knowledge packs — one design system across monorepos.",
-            "description": "Shared platform packages and this dogfooded docs library that documents them.",
-            "color": "#16324f"
-        }
-    ],
-    "books": [
-        {
-            "id": "00-platform-overview",
-            "familyId": "docify",
-            "audiences": [
-                "developers",
-                "builders"
-            ],
-            "status": "available",
-            "kicker": "CASE FILE · DOC-00",
-            "title": "Platform Overview",
-            "subtitle": "Humans and agents, one library",
-            "blurb": "What x12i-docify is, who it serves, and how product libraries plug in without forking UI.",
-            "tags": [
-                "platform",
-                "start-here",
-                "overview"
-            ],
-            "color": "#16324f",
-            "dir": "00-platform-overview"
-        },
-        {
-            "id": "01-packages",
-            "familyId": "docify",
-            "audiences": [
-                "developers"
-            ],
-            "status": "available",
-            "kicker": "CASE FILE · DOC-01",
-            "title": "Packages",
-            "subtitle": "The @x12i/docify-* map",
-            "blurb": "Core, theme, render, export, SDK, web, and screenshots — what each package owns.",
-            "tags": [
-                "packages",
-                "npm",
-                "platform"
-            ],
-            "color": "#1f6e5c",
-            "dir": "01-packages"
-        },
-        {
-            "id": "02-authoring",
-            "familyId": "docify",
-            "audiences": [
-                "developers",
-                "builders"
-            ],
-            "status": "available",
-            "kicker": "CASE FILE · DOC-02",
-            "title": "Authoring a Library",
-            "subtitle": "Books, data, site-pages, build",
-            "blurb": "Recipe to ship a product docs library: BOOK.md layout, data/*.json, site-pages, and the build pipeline.",
-            "tags": [
-                "authoring",
-                "content",
-                "getting-started"
-            ],
-            "color": "#a5710f",
-            "dir": "02-authoring"
-        },
-        {
-            "id": "03-for-humans",
-            "familyId": "docify",
-            "audiences": [
-                "developers",
-                "builders"
-            ],
-            "status": "available",
-            "kicker": "CASE FILE · DOC-03",
-            "title": "For Humans",
-            "subtitle": "The web app path",
-            "blurb": "How people use @x12i/docify-web — roles, use cases, catalog, chapter reader, downloads.",
-            "tags": [
-                "humans",
-                "web",
-                "reader"
-            ],
-            "color": "#b14a2c",
-            "dir": "03-for-humans",
-            "buildersPrimary": true
-        },
-        {
-            "id": "04-for-agents",
-            "familyId": "docify",
-            "audiences": [
-                "developers"
-            ],
-            "status": "available",
-            "kicker": "CASE FILE · DOC-04",
-            "title": "For Agents",
-            "subtitle": "Markdown + knowledge SDK",
-            "blurb": "MD packs, chapter indexes, agent-manifest.json, and createEbooksSdk — install knowledge as a devDependency.",
-            "tags": [
-                "agents",
-                "sdk",
-                "markdown"
-            ],
-            "color": "#5b3d8f",
-            "dir": "04-for-agents"
-        },
-        {
-            "id": "05-design",
-            "familyId": "docify",
-            "audiences": [
-                "developers",
-                "builders"
-            ],
-            "status": "available",
-            "kicker": "CASE FILE · DOC-05",
-            "title": "Design System",
-            "subtitle": "One look across monorepos",
-            "blurb": "Shared theme tokens and surfaces — products change naming and content only.",
-            "tags": [
-                "design",
-                "theme",
-                "brand"
-            ],
-            "color": "#16324f",
-            "dir": "05-design"
-        }
-    ]
-};
-export const useCases = {
-    "useCases": [
-        {
-            "id": "orient-docify",
-            "title": "Orient on x12i-docify",
-            "goal": "Understand the dual-audience platform and where product libraries fit.",
-            "audiences": [
-                "developers",
-                "builders"
-            ],
-            "tags": [
-                "platform",
-                "start-here"
-            ],
-            "path": [
-                {
-                    "bookId": "00-platform-overview",
-                    "audience": "developers",
-                    "chapters": [
-                        "the-central-idea",
-                        "1-what-x12i-docify-is",
-                        "2-layers",
-                        "4-where-to-go-next"
-                    ]
-                }
-            ],
-            "alsoSee": [
-                "00-platform-overview"
-            ]
-        },
-        {
-            "id": "map-packages",
-            "title": "Map the @x12i/docify-* packages",
-            "goal": "Know which package owns schemas, theme, render, export, SDK, web, and screenshots.",
-            "audiences": [
-                "developers"
-            ],
-            "tags": [
-                "packages",
-                "npm"
-            ],
-            "path": [
-                {
-                    "bookId": "01-packages",
-                    "audience": "developers",
-                    "chapters": [
-                        "1-package-table",
-                        "2-dependency-shape",
-                        "3-publish-and-install"
-                    ]
-                }
-            ],
-            "alsoSee": [
-                "01-packages"
-            ]
-        },
-        {
-            "id": "wire-product-library",
-            "title": "Wire a product docs library",
-            "goal": "Add books, data/*.json, site-pages, and build scripts in another monorepo without forking theme or web.",
-            "audiences": [
-                "developers",
-                "builders"
-            ],
-            "tags": [
-                "authoring",
-                "getting-started"
-            ],
-            "path": [
-                {
-                    "bookId": "02-authoring",
-                    "audience": "developers",
-                    "chapters": [
-                        "1-recipe",
-                        "2-content-layout",
-                        "3-data-contracts",
-                        "4-build-pipeline"
-                    ]
-                }
-            ],
-            "alsoSee": [
-                "02-authoring",
-                "05-design"
-            ]
-        },
-        {
-            "id": "ship-human-site",
-            "title": "Ship the human web app",
-            "goal": "Build and serve dist/web with roles, use cases, catalog, and chapter reader.",
-            "audiences": [
-                "developers",
-                "builders"
-            ],
-            "tags": [
-                "humans",
-                "web"
-            ],
-            "path": [
-                {
-                    "bookId": "03-for-humans",
-                    "audience": "developers",
-                    "chapters": [
-                        "1-best-form-for-humans",
-                        "2-typical-flow",
-                        "3-what-the-bundle-emits"
-                    ]
-                }
-            ],
-            "alsoSee": [
-                "03-for-humans"
-            ]
-        },
-        {
-            "id": "ship-agent-packs",
-            "title": "Ship agent markdown and knowledge SDK",
-            "goal": "Export MD packs, agent-manifest.json, and a product @…-docs package for npm i -D.",
-            "audiences": [
-                "developers"
-            ],
-            "tags": [
-                "agents",
-                "sdk"
-            ],
-            "path": [
-                {
-                    "bookId": "04-for-agents",
-                    "audience": "developers",
-                    "chapters": [
-                        "1-best-form-for-agents",
-                        "2-discovery",
-                        "3-knowledge-sdk",
-                        "4-install-contract"
-                    ]
-                }
-            ],
-            "alsoSee": [
-                "04-for-agents"
-            ]
-        },
-        {
-            "id": "keep-one-design",
-            "title": "Keep one design system",
-            "goal": "Change product naming and content only — never fork theme or invent a competing palette.",
-            "audiences": [
-                "developers",
-                "builders"
-            ],
-            "tags": [
-                "design",
-                "theme"
-            ],
-            "path": [
-                {
-                    "bookId": "05-design",
-                    "audience": "builders",
-                    "chapters": [
-                        "1-principle",
-                        "2-identity",
-                        "3-surfaces",
-                        "4-do-not"
-                    ]
-                }
-            ],
-            "alsoSee": [
-                "05-design"
-            ]
-        }
-    ]
-};
-export const site = {
-    "product": "docify",
-    "brand": "x12i · docify",
-    "brandAccent": "docify",
-    "siteUrl": "https://docs.docify.x12i.com",
-    "knowledgePackage": "@x12i/docify-docs",
-    "footer": "x12i-docify",
-    "accent": "oklch(55% 0.15 260)",
-    "accentAlt": "oklch(60% 0.15 40)",
-    "productUrl": "https://github.com/x12i/memorix-mono-repo/tree/main/x12i-docify",
-    "nav": [
-        {
-            "label": "Getting started",
-            "href": "/getting-started"
-        },
-        {
-            "label": "Use cases",
-            "href": "/use-cases"
-        },
-        {
-            "label": "Catalog",
-            "href": "/catalog"
-        }
-    ],
-    "footerLinks": [
-        {
-            "label": "Docs home",
-            "href": "/docs"
-        },
-        {
-            "label": "Getting started",
-            "href": "/getting-started"
-        },
-        {
-            "label": "Use cases",
-            "href": "/use-cases"
-        },
-        {
-            "label": "Catalog",
-            "href": "/catalog"
-        },
-        {
-            "label": "Agents/SDK",
-            "href": "/agents"
-        },
-        {
-            "label": "Platform README",
-            "href": "https://github.com/x12i/memorix-mono-repo/tree/main/x12i-docify"
-        }
-    ]
-};
-export const manifest = {
-    "version": 1,
-    "product": "docify",
-    "site": "https://docs.docify.x12i.com",
-    "knowledgePackage": "@x12i/docify-docs",
-    "roles": [
-        "developers",
-        "builders"
-    ],
-    "books": [
-        {
-            "id": "00-platform-overview",
-            "audiences": [
-                "developers",
-                "builders"
-            ],
-            "md": {
-                "developers": "downloads/books/00-platform-overview/developers.md",
-                "builders": "downloads/books/00-platform-overview/builders.md"
-            },
-            "pdf": {
-                "developers": null,
-                "builders": null
-            },
-            "chapters": {
-                "developers": "downloads/books/00-platform-overview/developers.chapters.json",
-                "builders": "downloads/books/00-platform-overview/builders.chapters.json"
-            }
-        },
-        {
-            "id": "01-packages",
-            "audiences": [
-                "developers"
-            ],
-            "md": {
-                "developers": "downloads/books/01-packages/developers.md"
-            },
-            "pdf": {
-                "developers": null
-            },
-            "chapters": {
-                "developers": "downloads/books/01-packages/developers.chapters.json"
-            }
-        },
-        {
-            "id": "02-authoring",
-            "audiences": [
-                "developers",
-                "builders"
-            ],
-            "md": {
-                "developers": "downloads/books/02-authoring/developers.md",
-                "builders": "downloads/books/02-authoring/builders.md"
-            },
-            "pdf": {
-                "developers": null,
-                "builders": null
-            },
-            "chapters": {
-                "developers": "downloads/books/02-authoring/developers.chapters.json",
-                "builders": "downloads/books/02-authoring/builders.chapters.json"
-            }
-        },
-        {
-            "id": "03-for-humans",
-            "audiences": [
-                "developers",
-                "builders"
-            ],
-            "md": {
-                "developers": "downloads/books/03-for-humans/developers.md",
-                "builders": "downloads/books/03-for-humans/builders.md"
-            },
-            "pdf": {
-                "developers": null,
-                "builders": null
-            },
-            "chapters": {
-                "developers": "downloads/books/03-for-humans/developers.chapters.json",
-                "builders": "downloads/books/03-for-humans/builders.chapters.json"
-            }
-        },
-        {
-            "id": "04-for-agents",
-            "audiences": [
-                "developers"
-            ],
-            "md": {
-                "developers": "downloads/books/04-for-agents/developers.md"
-            },
-            "pdf": {
-                "developers": null
-            },
-            "chapters": {
-                "developers": "downloads/books/04-for-agents/developers.chapters.json"
-            }
-        },
-        {
-            "id": "05-design",
-            "audiences": [
-                "developers",
-                "builders"
-            ],
-            "md": {
-                "developers": "downloads/books/05-design/developers.md",
-                "builders": "downloads/books/05-design/builders.md"
-            },
-            "pdf": {
-                "developers": null,
-                "builders": null
-            },
-            "chapters": {
-                "developers": "downloads/books/05-design/developers.chapters.json",
-                "builders": "downloads/books/05-design/builders.chapters.json"
-            }
-        }
-    ],
-    "useCases": [
-        {
-            "id": "orient-docify",
-            "title": "Orient on x12i-docify",
-            "md": "downloads/use-cases/orient-docify.md",
-            "path": [
-                {
-                    "bookId": "00-platform-overview",
-                    "audience": "developers",
-                    "chapters": [
-                        "the-central-idea",
-                        "1-what-x12i-docify-is",
-                        "2-layers",
-                        "4-where-to-go-next"
-                    ]
-                }
-            ]
-        },
-        {
-            "id": "map-packages",
-            "title": "Map the @x12i/docify-* packages",
-            "md": "downloads/use-cases/map-packages.md",
-            "path": [
-                {
-                    "bookId": "01-packages",
-                    "audience": "developers",
-                    "chapters": [
-                        "1-package-table",
-                        "2-dependency-shape",
-                        "3-publish-and-install"
-                    ]
-                }
-            ]
-        },
-        {
-            "id": "wire-product-library",
-            "title": "Wire a product docs library",
-            "md": "downloads/use-cases/wire-product-library.md",
-            "path": [
-                {
-                    "bookId": "02-authoring",
-                    "audience": "developers",
-                    "chapters": [
-                        "1-recipe",
-                        "2-content-layout",
-                        "3-data-contracts",
-                        "4-build-pipeline"
-                    ]
-                }
-            ]
-        },
-        {
-            "id": "ship-human-site",
-            "title": "Ship the human web app",
-            "md": "downloads/use-cases/ship-human-site.md",
-            "path": [
-                {
-                    "bookId": "03-for-humans",
-                    "audience": "developers",
-                    "chapters": [
-                        "1-best-form-for-humans",
-                        "2-typical-flow",
-                        "3-what-the-bundle-emits"
-                    ]
-                }
-            ]
-        },
-        {
-            "id": "ship-agent-packs",
-            "title": "Ship agent markdown and knowledge SDK",
-            "md": "downloads/use-cases/ship-agent-packs.md",
-            "path": [
-                {
-                    "bookId": "04-for-agents",
-                    "audience": "developers",
-                    "chapters": [
-                        "1-best-form-for-agents",
-                        "2-discovery",
-                        "3-knowledge-sdk",
-                        "4-install-contract"
-                    ]
-                }
-            ]
-        },
-        {
-            "id": "keep-one-design",
-            "title": "Keep one design system",
-            "md": "downloads/use-cases/keep-one-design.md",
-            "path": [
-                {
-                    "bookId": "05-design",
-                    "audience": "builders",
-                    "chapters": [
-                        "1-principle",
-                        "2-identity",
-                        "3-surfaces",
-                        "4-do-not"
-                    ]
-                }
-            ]
-        }
-    ]
-};
-export const files = {
-    "downloads/books/00-platform-overview/builders.chapters.json": "[\n  {\n    \"slug\": \"preamble\",\n    \"title\": \"Introduction\",\n    \"level\": 2,\n    \"order\": 0\n  },\n  {\n    \"slug\": \"how-to-read-this-guide\",\n    \"title\": \"How to read this guide\",\n    \"level\": 2,\n    \"order\": 1\n  },\n  {\n    \"slug\": \"the-central-idea\",\n    \"title\": \"The central idea\",\n    \"level\": 2,\n    \"order\": 2\n  },\n  {\n    \"slug\": \"1-what-you-own\",\n    \"title\": \"1. What you own\",\n    \"level\": 2,\n    \"order\": 3\n  },\n  {\n    \"slug\": \"2-layers\",\n    \"title\": \"2. Layers\",\n    \"level\": 2,\n    \"order\": 4\n  },\n  {\n    \"slug\": \"3-hard-rules-author-edition\",\n    \"title\": \"3. Hard rules (author edition)\",\n    \"level\": 2,\n    \"order\": 5\n  },\n  {\n    \"slug\": \"4-where-to-go-next\",\n    \"title\": \"4. Where to go next\",\n    \"level\": 2,\n    \"order\": 6\n  }\n]",
-    "downloads/books/00-platform-overview/builders.md": "# x12i-docify Platform Overview — Builders\n\n**Audience:** Content authors writing books and site pages for a product docs library.  \n**Twin:** [Developers version](../developers/BOOK.md)\n\n---\n\n## How to read this guide\n\nFocus on **what you author** and **what readers see**. Leave package wiring details to the developers twin unless you also own the build scripts.\n\n---\n\n## The central idea\n\nYou write **one library of Markdown**. Docify turns it into:\n\n- a **website** people browse (roles → use cases → chapters),\n- **downloadable books** (MD, and PDF when built),\n- **use-case packs** agents can load without scraping HTML.\n\nYou do **not** design a new theme or web app. You fill content contracts.\n\n---\n\n## 1. What you own\n\n| Artifact | Your job |\n|---|---|\n| `NN-slug/{audience}/BOOK.md` | Chapter bodies (H2 = chapter) |\n| `NN-slug/site-pages/landing.md` | Book landing copy |\n| `site-pages/*.md` | Product home, docs hub, getting started, … |\n| `data/catalog.json` | Roles, families, book metadata |\n| `data/use-cases.json` | Task → book + chapter slugs |\n| `data/site.json` | Brand strings, nav, knowledge package name |\n\n---\n\n## 2. Layers\n\nProduct content lives in a **docs library** folder (for Memorix: `memorix-docs/`; for this platform: this tree under `x12i-docify/`). The platform packages under `packages/docify-*` stay shared.\n\n---\n\n## 3. Hard rules (author edition)\n\n1. Prefer **task-first use cases** over dumping entire books into one path.\n2. Chapter slugs come from **H2 titles** — rename headings carefully; update use cases.\n3. Keep **developers** and **builders** twins in sync on shared facts; diverge only on depth and tone.\n4. Never invent a second visual brand that fights the shared design system.\n\n---\n\n## 4. Where to go next\n\n| Goal | Book |\n|---|---|\n| Authoring recipe | [Authoring a Library](../../02-authoring/builders/BOOK.md) |\n| Human navigation | [For Humans](../../03-for-humans/builders/BOOK.md) |\n| Design do / don’t | [Design System](../../05-design/builders/BOOK.md) |\n",
-    "downloads/books/00-platform-overview/developers.chapters.json": "[\n  {\n    \"slug\": \"preamble\",\n    \"title\": \"Introduction\",\n    \"level\": 2,\n    \"order\": 0\n  },\n  {\n    \"slug\": \"how-to-read-this-guide\",\n    \"title\": \"How to read this guide\",\n    \"level\": 2,\n    \"order\": 1\n  },\n  {\n    \"slug\": \"the-central-idea\",\n    \"title\": \"The central idea\",\n    \"level\": 2,\n    \"order\": 2\n  },\n  {\n    \"slug\": \"1-what-x12i-docify-is\",\n    \"title\": \"1. What x12i-docify is\",\n    \"level\": 2,\n    \"order\": 3\n  },\n  {\n    \"slug\": \"2-layers\",\n    \"title\": \"2. Layers\",\n    \"level\": 2,\n    \"order\": 4\n  },\n  {\n    \"slug\": \"3-hard-rules\",\n    \"title\": \"3. Hard rules\",\n    \"level\": 2,\n    \"order\": 5\n  },\n  {\n    \"slug\": \"4-where-to-go-next\",\n    \"title\": \"4. Where to go next\",\n    \"level\": 2,\n    \"order\": 6\n  }\n]",
-    "downloads/books/00-platform-overview/developers.md": "# x12i-docify Platform Overview — Developers\n\n**Audience:** Engineers wiring `@x12i/docify-*` into a monorepo or publishing a product knowledge SDK.  \n**Twin:** [Builders version](../builders/BOOK.md)  \n**Site:** this library’s web app · platform README at `x12i-docify/README.md`\n\n---\n\n## How to read this guide\n\n1. Start with the **central idea** — one content library, two consumption surfaces.\n2. Use **layers** when deciding platform vs product library responsibilities.\n3. Jump to Packages, Authoring, For Humans, or For Agents for depth.\n\n---\n\n## The central idea\n\n**x12i-docify** is the reusable **product site + docs + knowledge packs** platform for x12i monorepos.\n\n> One content library (`BOOK.md` + use cases). Two consumption surfaces. Same design system everywhere — products change naming and content only.\n\n| Audience | Best form | What we ship |\n|---|---|---|\n| **Humans** | Web app | Product home, docs hub, roles, use cases, catalog, book landings, chapter reader, MD/PDF downloads — `@x12i/docify-web` |\n| **AI agents** | Markdown + packages | Per-book MD, use-case packs, chapter indexes, `agent-manifest.json`, `@x12i/docify-sdk` / product `@…-docs` |\n\nKnowledge SDKs are **devDependencies** — documentation for tools and agents, not a production runtime.\n\n---\n\n## 1. What x12i-docify is\n\n### The problem it solves\n\nEvery product monorepo needs:\n\n- a branded docs **site** humans can browse,\n- **ebooks** with stable chapter structure,\n- **task-first use cases** that deep-link into chapters,\n- **agent-friendly** Markdown packs and a discoverable manifest,\n- one **visual system** so products do not invent competing UIs.\n\nDocify answers that with shared packages. Product folders supply content and brand strings only.\n\n### Who uses what\n\n| You are… | Primary surface | Install |\n|---|---|---|\n| Reader (human) | Product `dist/web` | Nothing — open the site |\n| Content author | `BOOK.md` + `site-pages` + `data/*.json` | Platform packages in the monorepo |\n| Integrator / platform engineer | `@x12i/docify-*` | Platform packages; optional product `@…-docs` as `devDependency` |\n| AI agent / tooling | MD downloads + knowledge SDK | `npm i -D @your-scope/<product>-docs` |\n\n---\n\n## 2. Layers\n\n```mermaid\nflowchart TB\n  Platform[x12i-docify platform packages]\n  Product[\"&lt;product&gt;-docs content library\"]\n  Web[dist/web for humans]\n  SDK[\"@…-docs knowledge package\"]\n  Product --> Platform\n  Product --> Web\n  Product --> SDK\n```\n\n| Layer | What it is |\n|---|---|\n| `x12i-docify` | Shared platform (theme, render, web, export, SDK, screenshots) |\n| `<product>-docs/` | Product content: books, site-pages, catalog, use cases |\n| `@x12i/<product>-docs` | Knowledge SDK + MD packs for agents (`npm i -D`) |\n\nMemorix is the large reference implementation: `memorix-docs/` → `@x12i/memorix-docs`.  \n**This library** is the platform documenting itself (dogfood).\n\n---\n\n## 3. Hard rules\n\n1. **Do not fork** `@x12i/docify-theme` or `@x12i/docify-web` per product.\n2. Knowledge packages are **devDependencies**, never production UI runtime.\n3. Markdown (`BOOK.md`) is the **source of truth**; HTML/PDF are derived.\n4. Use-case paths must reference **real chapter slugs** (H2 headings).\n5. Site pages use **YAML front-matter**; the platform renders HTML.\n\n---\n\n## 4. Where to go next\n\n| Goal | Book |\n|---|---|\n| Package map | [Packages](../../01-packages/developers/BOOK.md) |\n| Wire a new library | [Authoring a Library](../../02-authoring/developers/BOOK.md) |\n| Human site behavior | [For Humans](../../03-for-humans/developers/BOOK.md) |\n| Agent / SDK path | [For Agents](../../04-for-agents/developers/BOOK.md) |\n| Theme contract | [Design System](../../05-design/developers/BOOK.md) |\n",
-    "downloads/books/01-packages/developers.chapters.json": "[\n  {\n    \"slug\": \"preamble\",\n    \"title\": \"Introduction\",\n    \"level\": 2,\n    \"order\": 0\n  },\n  {\n    \"slug\": \"1-package-table\",\n    \"title\": \"1. Package table\",\n    \"level\": 2,\n    \"order\": 1\n  },\n  {\n    \"slug\": \"2-dependency-shape\",\n    \"title\": \"2. Dependency shape\",\n    \"level\": 2,\n    \"order\": 2\n  },\n  {\n    \"slug\": \"3-publish-and-install\",\n    \"title\": \"3. Publish and install\",\n    \"level\": 2,\n    \"order\": 3\n  },\n  {\n    \"slug\": \"4-migration-names\",\n    \"title\": \"4. Migration names\",\n    \"level\": 2,\n    \"order\": 4\n  }\n]",
-    "downloads/books/01-packages/developers.md": "# Packages — Developers\n\n**Audience:** Engineers choosing and wiring `@x12i/docify-*` packages.  \n**Related:** [Platform Overview](../../00-platform-overview/developers/BOOK.md) · [Authoring](../../02-authoring/developers/BOOK.md)\n\n---\n\n## 1. Package table\n\n| Folder | npm | Role |\n|---|---|---|\n| `docify-core` | `@x12i/docify-core` | Catalog / use-case / site-page / manifest schemas + loaders |\n| `docify-theme` | `@x12i/docify-theme` | Shared site + reader CSS (tokens, site, book, extras) |\n| `docify-render` | `@x12i/docify-render` | `BOOK.md` + site-pages → HTML; chapter extract / splice |\n| `docify-export` | `@x12i/docify-export` | Content bundle builder (downloads, landings, agent-manifest) |\n| `docify-sdk` | `@x12i/docify-sdk` | `createEbooksSdk(bundle)` knowledge SDK factory |\n| `docify-web` | `@x12i/docify-web` | Shareable static web app + `docify-web serve` |\n| `docify-screenshots` | `@x12i/docify-screenshots` | Shot lists, placeholders, capture helpers |\n\n---\n\n## 2. Dependency shape\n\n```mermaid\nflowchart LR\n  Core[docify-core]\n  Theme[docify-theme]\n  Render[docify-render]\n  Export[docify-export]\n  Sdk[docify-sdk]\n  Web[docify-web]\n  Shots[docify-screenshots]\n  Render --> Core\n  Export --> Core\n  Export --> Render\n  Sdk --> Core\n  Web --> Theme\n  ProductDocs[product-docs build] --> Export\n  ProductDocs --> Web\n  ProductSdk[\"@…-docs\"] --> Sdk\n```\n\n- **Humans** consume `docify-web` + theme assets from the assembled `dist/web`.\n- **Agents** consume MD packs from the bundle and/or a published product knowledge SDK built on `docify-sdk`.\n\n---\n\n## 3. Publish and install\n\nFrom the monorepo (uses root `.npmrc`):\n\n```bash\nbash scripts/publish-docify.sh\n```\n\nTypical product install:\n\n```bash\nnpm i @x12i/docify-core @x12i/docify-theme @x12i/docify-render \\\n      @x12i/docify-export @x12i/docify-sdk @x12i/docify-web\nnpm i -D @x12i/memorix-docs   # example product knowledge SDK\n```\n\nIn this monorepo, product builds usually **import from source** under `x12i-docify/packages/*/dist` rather than resolving published tarballs during local `npm run docs`.\n\n---\n\n## 4. Migration names\n\n| Old | New |\n|---|---|\n| `@x12i/ebooks-*` | `@x12i/docify-*` |\n| `x12i-ebooks/` | `x12i-docify/` |\n| `ebooks-web` CLI | `docify-web` |\n| `@x12i/memorix-ebooks` | `@x12i/memorix-docs` |\n",
-    "downloads/books/02-authoring/builders.chapters.json": "[\n  {\n    \"slug\": \"preamble\",\n    \"title\": \"Introduction\",\n    \"level\": 2,\n    \"order\": 0\n  },\n  {\n    \"slug\": \"1-recipe-content-side\",\n    \"title\": \"1. Recipe (content side)\",\n    \"level\": 2,\n    \"order\": 1\n  },\n  {\n    \"slug\": \"2-content-layout\",\n    \"title\": \"2. Content layout\",\n    \"level\": 2,\n    \"order\": 2\n  },\n  {\n    \"slug\": \"3-data-contracts-what-you-edit\",\n    \"title\": \"3. Data contracts (what you edit)\",\n    \"level\": 2,\n    \"order\": 3\n  },\n  {\n    \"slug\": \"4-build-pipeline-preview\",\n    \"title\": \"4. Build pipeline (preview)\",\n    \"level\": 2,\n    \"order\": 4\n  },\n  {\n    \"slug\": \"5-writing-tips\",\n    \"title\": \"5. Writing tips\",\n    \"level\": 2,\n    \"order\": 5\n  }\n]",
-    "downloads/books/02-authoring/builders.md": "# Authoring a Library — Builders\n\n**Audience:** Content authors filling a product docs library.  \n**Twin:** [Developers version](../developers/BOOK.md)\n\n---\n\n## 1. Recipe (content side)\n\n1. Create `NN-slug/{developers|builders}/BOOK.md` with clear `##` chapter titles.\n2. Add a book landing at `NN-slug/site-pages/landing.md`.\n3. Register the book in `data/catalog.json` (id, audiences, kicker, title, blurb, color, dir).\n4. Add or extend use cases in `data/use-cases.json` with real chapter slugs.\n5. Update site pages when the library story changes (home, getting started, catalog lead).\n\n---\n\n## 2. Content layout\n\nYou mostly live in:\n\n- book folders (`BOOK.md`, diagrams, screenshots, landings),\n- top-level `site-pages/`,\n- `data/catalog.json` and `data/use-cases.json`.\n\nLeave package install and `dist/` assembly to developers unless you run `npm run docs` locally to preview.\n\n---\n\n## 3. Data contracts (what you edit)\n\n**Catalog book entry** — title, subtitle, blurb, tags, color, audiences, status.  \n**Use case** — id, title, goal, tags, and a `path` of `{ bookId, audience, chapters[] }`.\n\nTip: after renaming an H2, search use-cases for the old slug before merging.\n\n---\n\n## 4. Build pipeline (preview)\n\n```bash\nnpm run docs          # build if needed, serve, open browser\nnpm run docs:rebuild  # force rebuild\n```\n\nConfirm landings, chapter sidebar, and use-case deep links before calling content done.\n\n---\n\n## 5. Writing tips\n\n- One job per chapter; keep H2 titles stable once published.\n- Cross-link twins (`developers` ↔ `builders`) at the top of each book.\n- Prefer use cases that assemble **a few** chapters for a task over entire books.\n",
-    "downloads/books/02-authoring/developers.chapters.json": "[\n  {\n    \"slug\": \"preamble\",\n    \"title\": \"Introduction\",\n    \"level\": 2,\n    \"order\": 0\n  },\n  {\n    \"slug\": \"1-recipe\",\n    \"title\": \"1. Recipe\",\n    \"level\": 2,\n    \"order\": 1\n  },\n  {\n    \"slug\": \"2-content-layout\",\n    \"title\": \"2. Content layout\",\n    \"level\": 2,\n    \"order\": 2\n  },\n  {\n    \"slug\": \"3-data-contracts\",\n    \"title\": \"3. Data contracts\",\n    \"level\": 2,\n    \"order\": 3\n  },\n  {\n    \"slug\": \"4-build-pipeline\",\n    \"title\": \"4. Build pipeline\",\n    \"level\": 2,\n    \"order\": 4\n  },\n  {\n    \"slug\": \"5-humans-vs-agents-after-build\",\n    \"title\": \"5. Humans vs agents after build\",\n    \"level\": 2,\n    \"order\": 5\n  }\n]",
-    "downloads/books/02-authoring/developers.md": "# Authoring a Library — Developers\n\n**Audience:** Engineers scaffolding a product docs library on docify.  \n**Twin:** [Builders version](../builders/BOOK.md)  \n**Reference:** `memorix-docs/` in this monorepo · this dogfood tree under `x12i-docify/`\n\n---\n\n## 1. Recipe\n\n1. Depend on `@x12i/docify-{core,theme,render,export,sdk,web}` — do **not** fork theme or web app.\n2. Author books as `NN-slug/{audience}/BOOK.md`.\n3. Add product data:\n   - `data/site.json` — `product`, `brand`, `brandAccent`, `siteUrl`, `knowledgePackage`\n   - `data/catalog.json` — roles, families, books (kickers / colors / titles)\n   - `data/use-cases.json` — task → book + chapter slugs\n4. Add `site-pages/*.md` with YAML front-matter (`product-home`, `docs-home`, …).\n5. Wire build scripts to import platform packages (see `memorix-docs/scripts/` or `x12i-docify/scripts/`).\n6. Publish `@your-scope/<product>-docs` as a **devDependency** knowledge SDK.\n7. Deploy `dist/web` for humans; ship MD + `agent-manifest.json` for agents.\n\n---\n\n## 2. Content layout\n\n```\n<product>-docs/\n  data/{site,catalog,use-cases}.json\n  site-pages/*.md\n  NN-slug/\n    developers/BOOK.md\n    builders/BOOK.md          # optional twin\n    site-pages/landing.md\n    diagrams/ … screenshots/\n  packages/<product>-docs/    # published knowledge SDK\n  scripts/build-bundle.mjs\n  scripts/build-knowledge.mjs\n  scripts/docs.mjs\n```\n\n---\n\n## 3. Data contracts\n\n| File | Owns |\n|---|---|\n| `site.json` | Brand chrome, accent CSS colors, nav, knowledge package name |\n| `catalog.json` | Roles (`developers` \\| `builders`), families, book metadata |\n| `use-cases.json` | Stable use-case ids + reading paths (bookId, audience, chapter slugs) |\n\nChapter slugs are produced by slugifying `##` headings in `BOOK.md`. Broken use-case paths **fail the bundle build**.\n\n---\n\n## 4. Build pipeline\n\nTypical scripts:\n\n| Script | Job |\n|---|---|\n| `build-bundle.mjs` | `buildContentBundle` → `dist/bundle` + assemble `dist/web` |\n| `build-knowledge.mjs` | Embed downloads + JSON into `packages/<sdk>/src/generated/bundle.ts` |\n| `docs.mjs` | Build if needed, `docify-web serve dist/web`, open browser |\n\nEnv: set `EBOOKS_PDF=0` or `DOCIFY_PDF=0` to skip PDF when `wkhtmltopdf` is unavailable.\n\n---\n\n## 5. Humans vs agents after build\n\n| Output | Audience |\n|---|---|\n| `dist/web` static app | Humans |\n| `downloads/*.md`, chapter JSON, `agent-manifest.json` | Agents |\n| Published `@…-docs` package | Agents / tooling (`npm i -D`) |\n",
-    "downloads/books/03-for-humans/builders.chapters.json": "[\n  {\n    \"slug\": \"preamble\",\n    \"title\": \"Introduction\",\n    \"level\": 2,\n    \"order\": 0\n  },\n  {\n    \"slug\": \"1-best-form-for-humans\",\n    \"title\": \"1. Best form for humans\",\n    \"level\": 2,\n    \"order\": 1\n  },\n  {\n    \"slug\": \"2-typical-flow\",\n    \"title\": \"2. Typical flow\",\n    \"level\": 2,\n    \"order\": 2\n  },\n  {\n    \"slug\": \"3-what-the-bundle-emits\",\n    \"title\": \"3. What the bundle emits\",\n    \"level\": 2,\n    \"order\": 3\n  },\n  {\n    \"slug\": \"4-writing-for-the-site\",\n    \"title\": \"4. Writing for the site\",\n    \"level\": 2,\n    \"order\": 4\n  }\n]",
-    "downloads/books/03-for-humans/builders.md": "# For Humans — Builders\n\n**Audience:** Authors shaping how people navigate the library.  \n**Twin:** [Developers version](../developers/BOOK.md)\n\n---\n\n## 1. Best form for humans\n\nReaders land on the **web app**: choose a role, pick a use case or browse the catalog, then read chapters. Your job is clear titles, short blurbs, and use cases that match real tasks.\n\n---\n\n## 2. Typical flow\n\nThink about the path a first-time reader takes:\n\n1. Product home → audience chooser  \n2. Getting started tracks (developers vs builders)  \n3. A featured use case or book  \n4. Chapter reading with a sensible next chapter  \n\nIf that path feels broken, fix catalog blurbs and use-case paths before adding more books.\n\n---\n\n## 3. What the bundle emits\n\nYou preview via `npm run docs`. Confirm:\n\n- home and docs heroes read correctly,\n- catalog cards show your kickers and colors,\n- use cases deep-link into the intended chapters,\n- downloads appear on book landings.\n\n---\n\n## 4. Writing for the site\n\n- One headline job per site-page section.\n- Keep CTAs to role / getting started / use cases / catalog.\n- Book landings: short lead + related books — catalog stays authoritative for metadata.\n",
-    "downloads/books/03-for-humans/developers.chapters.json": "[\n  {\n    \"slug\": \"preamble\",\n    \"title\": \"Introduction\",\n    \"level\": 2,\n    \"order\": 0\n  },\n  {\n    \"slug\": \"1-best-form-for-humans\",\n    \"title\": \"1. Best form for humans\",\n    \"level\": 2,\n    \"order\": 1\n  },\n  {\n    \"slug\": \"2-typical-flow\",\n    \"title\": \"2. Typical flow\",\n    \"level\": 2,\n    \"order\": 2\n  },\n  {\n    \"slug\": \"3-what-the-bundle-emits\",\n    \"title\": \"3. What the bundle emits\",\n    \"level\": 2,\n    \"order\": 3\n  },\n  {\n    \"slug\": \"4-product-libraries\",\n    \"title\": \"4. Product libraries\",\n    \"level\": 2,\n    \"order\": 4\n  }\n]",
-    "downloads/books/03-for-humans/developers.md": "# For Humans — Developers\n\n**Audience:** Engineers shipping `dist/web` for human readers.  \n**Twin:** [Builders version](../builders/BOOK.md)\n\n---\n\n## 1. Best form for humans\n\nThe **web app** (`@x12i/docify-web`) is the human surface: case-file UI, role chooser, use-case routing, chapter reader, and download buttons.\n\nHumans should not be asked to scrape Markdown repos as their primary path. Deploy the static tree.\n\n---\n\n## 2. Typical flow\n\n1. **Role** — pick developers / builders (or product-defined roles)\n2. **Use cases** — task-first entry; opens the right book + chapter\n3. **Catalog** — browse books by family\n4. **Reader** — chapter HTML in the shared book theme\n5. **Downloads** — MD (and PDF when built) for offline reading\n\nProduct home (`/`) and docs hub (`/docs`) are authored as site-pages with YAML front-matter.\n\n---\n\n## 3. What the bundle emits\n\n| Path | Role |\n|---|---|\n| `index.html`, `docs.html`, … | Marketing / docs chrome from site-pages |\n| `books/<id>.html` | Book landings |\n| `read.html` + chapter HTML | Reader shell |\n| `catalog.json`, `use-cases.json`, `site.json` | Client data |\n| `downloads/` | MD / PDF / chapter indexes |\n| `agent-manifest.json` | Also useful for humans’ tooling links |\n\nAssemble with `buildContentBundle`, then overlay `docify-web/public` runtime assets (`app.js`, `read.html`, `agents.html`).\n\n---\n\n## 4. Product libraries\n\nEach monorepo ships its own library (e.g. Memorix at `memorix-docs/`) with brand strings and books. The platform does not fork a separate UI per product.\n",
-    "downloads/books/04-for-agents/developers.chapters.json": "[\n  {\n    \"slug\": \"preamble\",\n    \"title\": \"Introduction\",\n    \"level\": 2,\n    \"order\": 0\n  },\n  {\n    \"slug\": \"1-best-form-for-agents\",\n    \"title\": \"1. Best form for agents\",\n    \"level\": 2,\n    \"order\": 1\n  },\n  {\n    \"slug\": \"2-discovery\",\n    \"title\": \"2. Discovery\",\n    \"level\": 2,\n    \"order\": 2\n  },\n  {\n    \"slug\": \"3-knowledge-sdk\",\n    \"title\": \"3. Knowledge SDK\",\n    \"level\": 2,\n    \"order\": 3\n  },\n  {\n    \"slug\": \"4-install-contract\",\n    \"title\": \"4. Install contract\",\n    \"level\": 2,\n    \"order\": 4\n  }\n]",
-    "downloads/books/04-for-agents/developers.md": "# For Agents — Developers\n\n**Audience:** Engineers shipping agent-consumable knowledge.  \n**Related:** [Packages](../../01-packages/developers/BOOK.md) · [Authoring](../../02-authoring/developers/BOOK.md)\n\n---\n\n## 1. Best form for agents\n\nAgents should use **structured Markdown** and **packages**, not the HTML reader:\n\n| Artifact | Role |\n|---|---|\n| Per-book `.md` | Full `BOOK.md` export |\n| Use-case packs | Assembled MD for a task |\n| `.chapters.json` | Chapter slug → title index |\n| `agent-manifest.json` | Discovery map of all downloads |\n| Knowledge SDK | `listUseCases`, `getUseCaseMarkdown`, `getBookMarkdown` |\n\n---\n\n## 2. Discovery\n\nWithout the SDK:\n\n1. Open `/agent-manifest.json` on the deployed web app\n2. Follow `downloads/` paths for MD packs\n3. Prefer chapter indexes when slicing context\n\nWith the SDK: install the product knowledge package and call the typed helpers.\n\n---\n\n## 3. Knowledge SDK\n\nPlatform factory: `@x12i/docify-sdk` → `createEbooksSdk(bundle)`.\n\nProduct packages pre-wire a bundle (catalog, use cases, site, manifest, embedded files). Example:\n\n```ts\nimport { memorixDocs } from \"@x12i/memorix-docs\";\n\nconst pack = memorixDocs.getUseCaseMarkdown(\"client-first-read-write\");\nconst book = memorixDocs.getBookMarkdown(\"02-runtime-data-client\", \"developers\");\nconst hits = memorixDocs.listUseCases({ audience: \"developers\", tag: \"http\" });\n```\n\nThis platform’s own package is `@x12i/docify-docs` (`docifyDocs`).\n\n---\n\n## 4. Install contract\n\nKnowledge packages document the product for tools and agents. They are **not** a production runtime dependency.\n\n```bash\nnpm i -D @x12i/docify-docs    # this platform\nnpm i -D @x12i/memorix-docs   # Memorix product example\n```\n\nExport pipeline (`@x12i/docify-export`) emits MD + manifest alongside the web bundle. Stable use-case IDs keep agent prompts reproducible.\n",
-    "downloads/books/05-design/builders.chapters.json": "[\n  {\n    \"slug\": \"preamble\",\n    \"title\": \"Introduction\",\n    \"level\": 2,\n    \"order\": 0\n  },\n  {\n    \"slug\": \"1-principle\",\n    \"title\": \"1. Principle\",\n    \"level\": 2,\n    \"order\": 1\n  },\n  {\n    \"slug\": \"2-identity\",\n    \"title\": \"2. Identity\",\n    \"level\": 2,\n    \"order\": 2\n  },\n  {\n    \"slug\": \"3-surfaces\",\n    \"title\": \"3. Surfaces\",\n    \"level\": 2,\n    \"order\": 3\n  },\n  {\n    \"slug\": \"4-do-not\",\n    \"title\": \"4. Do not\",\n    \"level\": 2,\n    \"order\": 4\n  }\n]",
-    "downloads/books/05-design/builders.md": "# Design System — Builders\n\n**Audience:** Authors staying inside the shared visual system.  \n**Twin:** [Developers version](../developers/BOOK.md)\n\n---\n\n## 1. Principle\n\n**One design system.** You change **words, books, and brand strings** — not layout, cards chrome, or a new palette.\n\n---\n\n## 2. Identity\n\nThe site already carries IBM Plex, neutral surfaces, and a primary + builders accent. Catalog **book colors** are case-file accents inside that system, not a free-for-all.\n\n---\n\n## 3. Surfaces\n\n| Surface | What you influence |\n|---|---|\n| Product / docs chrome | Site-page copy, CTAs, featured book ids |\n| Chapter reader | Markdown structure and diagrams inside books |\n| Catalog cards | Title, blurb, kicker, color field in `catalog.json` |\n\n---\n\n## 4. Do not\n\n- Ask engineering to fork theme CSS “just for this product”\n- Overload the first viewport with secondary marketing blocks (follow product-home patterns)\n- Treat screenshots as decoration without a shot-list purpose\n",
-    "downloads/books/05-design/developers.chapters.json": "[\n  {\n    \"slug\": \"preamble\",\n    \"title\": \"Introduction\",\n    \"level\": 2,\n    \"order\": 0\n  },\n  {\n    \"slug\": \"1-principle\",\n    \"title\": \"1. Principle\",\n    \"level\": 2,\n    \"order\": 1\n  },\n  {\n    \"slug\": \"2-identity\",\n    \"title\": \"2. Identity\",\n    \"level\": 2,\n    \"order\": 2\n  },\n  {\n    \"slug\": \"3-surfaces\",\n    \"title\": \"3. Surfaces\",\n    \"level\": 2,\n    \"order\": 3\n  },\n  {\n    \"slug\": \"4-do-not\",\n    \"title\": \"4. Do not\",\n    \"level\": 2,\n    \"order\": 4\n  }\n]",
-    "downloads/books/05-design/developers.md": "# Design System — Developers\n\n**Audience:** Engineers integrating theme assets into a product build.  \n**Twin:** [Builders version](../builders/BOOK.md)\n\n---\n\n## 1. Principle\n\n**One design system.** Product libraries change **naming and content only** — not layout, palette, or component chrome.\n\nWire CSS from `@x12i/docify-theme` (or the monorepo `packages/docify-theme` path) into the content bundle. Do not copy-fork stylesheets into the product folder.\n\n---\n\n## 2. Identity\n\n- IBM Plex Sans / Mono\n- Neutral near-white surface, single blue accent + warm builders accent (`--accent`, `--accent-alt`)\n- Site chrome for product home, docs hub, catalog, use cases\n- Book bodies for chapter reading (screen-tuned; print stays PDF-safe)\n\nProduct `data/site.json` may set `accent` / `accentAlt` CSS colors within the shared system — not a second brand language.\n\n---\n\n## 3. Surfaces\n\n| Surface | Stylesheet | Notes |\n|---|---|---|\n| Web app shell | `site.css`, `extras.css` | Product/docs chrome |\n| Chapter reader | `book.css` | Screen column + print rules |\n| Tokens | `tokens.css` | Shared variables |\n\n---\n\n## 4. Do not\n\n- Fork a second theme per product\n- Invent a new brand palette that fights the shared system\n- Treat the knowledge SDK as a production UI dependency\n- Hand-author HTML for marketing routes — use site-page Markdown + front-matter\n",
-    "downloads/use-cases/keep-one-design.md": "# Keep one design system\n\n> **Use case id:** `keep-one-design`\n> **Goal:** Change product naming and content only — never fork theme or invent a competing palette.\n> **Audiences:** developers, builders\n> **Tags:** design, theme\n\n## Reading path\n\n1. **Design System** (builders) → chapters: `1-principle`, `2-identity`, `3-surfaces`, `4-do-not`\n\n## From: Design System — 1. Principle\n\n**One design system.** You change **words, books, and brand strings** — not layout, cards chrome, or a new palette.\n\n---\n\n## From: Design System — 2. Identity\n\nThe site already carries IBM Plex, neutral surfaces, and a primary + builders accent. Catalog **book colors** are case-file accents inside that system, not a free-for-all.\n\n---\n\n## From: Design System — 3. Surfaces\n\n| Surface | What you influence |\n|---|---|\n| Product / docs chrome | Site-page copy, CTAs, featured book ids |\n| Chapter reader | Markdown structure and diagrams inside books |\n| Catalog cards | Title, blurb, kicker, color field in `catalog.json` |\n\n---\n\n## From: Design System — 4. Do not\n\n- Ask engineering to fork theme CSS “just for this product”\n- Overload the first viewport with secondary marketing blocks (follow product-home patterns)\n- Treat screenshots as decoration without a shot-list purpose\n\n## Also see\n\n- **Design System** (`05-design`) — Shared theme tokens and surfaces — products change naming and content only.\n\n---\n\n_Generated use-case pack for agents and humans. See `agent-manifest.json` for discovery._\n",
-    "downloads/use-cases/map-packages.md": "# Map the @x12i/docify-* packages\n\n> **Use case id:** `map-packages`\n> **Goal:** Know which package owns schemas, theme, render, export, SDK, web, and screenshots.\n> **Audiences:** developers\n> **Tags:** packages, npm\n\n## Reading path\n\n1. **Packages** (developers) → chapters: `1-package-table`, `2-dependency-shape`, `3-publish-and-install`\n\n## From: Packages — 1. Package table\n\n| Folder | npm | Role |\n|---|---|---|\n| `docify-core` | `@x12i/docify-core` | Catalog / use-case / site-page / manifest schemas + loaders |\n| `docify-theme` | `@x12i/docify-theme` | Shared site + reader CSS (tokens, site, book, extras) |\n| `docify-render` | `@x12i/docify-render` | `BOOK.md` + site-pages → HTML; chapter extract / splice |\n| `docify-export` | `@x12i/docify-export` | Content bundle builder (downloads, landings, agent-manifest) |\n| `docify-sdk` | `@x12i/docify-sdk` | `createEbooksSdk(bundle)` knowledge SDK factory |\n| `docify-web` | `@x12i/docify-web` | Shareable static web app + `docify-web serve` |\n| `docify-screenshots` | `@x12i/docify-screenshots` | Shot lists, placeholders, capture helpers |\n\n---\n\n## From: Packages — 2. Dependency shape\n\n```mermaid\nflowchart LR\n  Core[docify-core]\n  Theme[docify-theme]\n  Render[docify-render]\n  Export[docify-export]\n  Sdk[docify-sdk]\n  Web[docify-web]\n  Shots[docify-screenshots]\n  Render --> Core\n  Export --> Core\n  Export --> Render\n  Sdk --> Core\n  Web --> Theme\n  ProductDocs[product-docs build] --> Export\n  ProductDocs --> Web\n  ProductSdk[\"@…-docs\"] --> Sdk\n```\n\n- **Humans** consume `docify-web` + theme assets from the assembled `dist/web`.\n- **Agents** consume MD packs from the bundle and/or a published product knowledge SDK built on `docify-sdk`.\n\n---\n\n## From: Packages — 3. Publish and install\n\nFrom the monorepo (uses root `.npmrc`):\n\n```bash\nbash scripts/publish-docify.sh\n```\n\nTypical product install:\n\n```bash\nnpm i @x12i/docify-core @x12i/docify-theme @x12i/docify-render \\\n      @x12i/docify-export @x12i/docify-sdk @x12i/docify-web\nnpm i -D @x12i/memorix-docs   # example product knowledge SDK\n```\n\nIn this monorepo, product builds usually **import from source** under `x12i-docify/packages/*/dist` rather than resolving published tarballs during local `npm run docs`.\n\n---\n\n## Also see\n\n- **Packages** (`01-packages`) — Core, theme, render, export, SDK, web, and screenshots — what each package owns.\n\n---\n\n_Generated use-case pack for agents and humans. See `agent-manifest.json` for discovery._\n",
-    "downloads/use-cases/orient-docify.md": "# Orient on x12i-docify\n\n> **Use case id:** `orient-docify`\n> **Goal:** Understand the dual-audience platform and where product libraries fit.\n> **Audiences:** developers, builders\n> **Tags:** platform, start-here\n\n## Reading path\n\n1. **Platform Overview** (developers) → chapters: `the-central-idea`, `1-what-x12i-docify-is`, `2-layers`, `4-where-to-go-next`\n\n## From: Platform Overview — The central idea\n\n**x12i-docify** is the reusable **product site + docs + knowledge packs** platform for x12i monorepos.\n\n> One content library (`BOOK.md` + use cases). Two consumption surfaces. Same design system everywhere — products change naming and content only.\n\n| Audience | Best form | What we ship |\n|---|---|---|\n| **Humans** | Web app | Product home, docs hub, roles, use cases, catalog, book landings, chapter reader, MD/PDF downloads — `@x12i/docify-web` |\n| **AI agents** | Markdown + packages | Per-book MD, use-case packs, chapter indexes, `agent-manifest.json`, `@x12i/docify-sdk` / product `@…-docs` |\n\nKnowledge SDKs are **devDependencies** — documentation for tools and agents, not a production runtime.\n\n---\n\n## From: Platform Overview — 1. What x12i-docify is\n\n### The problem it solves\n\nEvery product monorepo needs:\n\n- a branded docs **site** humans can browse,\n- **ebooks** with stable chapter structure,\n- **task-first use cases** that deep-link into chapters,\n- **agent-friendly** Markdown packs and a discoverable manifest,\n- one **visual system** so products do not invent competing UIs.\n\nDocify answers that with shared packages. Product folders supply content and brand strings only.\n\n### Who uses what\n\n| You are… | Primary surface | Install |\n|---|---|---|\n| Reader (human) | Product `dist/web` | Nothing — open the site |\n| Content author | `BOOK.md` + `site-pages` + `data/*.json` | Platform packages in the monorepo |\n| Integrator / platform engineer | `@x12i/docify-*` | Platform packages; optional product `@…-docs` as `devDependency` |\n| AI agent / tooling | MD downloads + knowledge SDK | `npm i -D @your-scope/<product>-docs` |\n\n---\n\n## From: Platform Overview — 2. Layers\n\n```mermaid\nflowchart TB\n  Platform[x12i-docify platform packages]\n  Product[\"&lt;product&gt;-docs content library\"]\n  Web[dist/web for humans]\n  SDK[\"@…-docs knowledge package\"]\n  Product --> Platform\n  Product --> Web\n  Product --> SDK\n```\n\n| Layer | What it is |\n|---|---|\n| `x12i-docify` | Shared platform (theme, render, web, export, SDK, screenshots) |\n| `<product>-docs/` | Product content: books, site-pages, catalog, use cases |\n| `@x12i/<product>-docs` | Knowledge SDK + MD packs for agents (`npm i -D`) |\n\nMemorix is the large reference implementation: `memorix-docs/` → `@x12i/memorix-docs`.  \n**This library** is the platform documenting itself (dogfood).\n\n---\n\n## From: Platform Overview — 4. Where to go next\n\n| Goal | Book |\n|---|---|\n| Package map | [Packages](../../01-packages/developers/BOOK.md) |\n| Wire a new library | [Authoring a Library](../../02-authoring/developers/BOOK.md) |\n| Human site behavior | [For Humans](../../03-for-humans/developers/BOOK.md) |\n| Agent / SDK path | [For Agents](../../04-for-agents/developers/BOOK.md) |\n| Theme contract | [Design System](../../05-design/developers/BOOK.md) |\n\n## Also see\n\n- **Platform Overview** (`00-platform-overview`) — What x12i-docify is, who it serves, and how product libraries plug in without forking UI.\n\n---\n\n_Generated use-case pack for agents and humans. See `agent-manifest.json` for discovery._\n",
-    "downloads/use-cases/ship-agent-packs.md": "# Ship agent markdown and knowledge SDK\n\n> **Use case id:** `ship-agent-packs`\n> **Goal:** Export MD packs, agent-manifest.json, and a product @…-docs package for npm i -D.\n> **Audiences:** developers\n> **Tags:** agents, sdk\n\n## Reading path\n\n1. **For Agents** (developers) → chapters: `1-best-form-for-agents`, `2-discovery`, `3-knowledge-sdk`, `4-install-contract`\n\n## From: For Agents — 1. Best form for agents\n\nAgents should use **structured Markdown** and **packages**, not the HTML reader:\n\n| Artifact | Role |\n|---|---|\n| Per-book `.md` | Full `BOOK.md` export |\n| Use-case packs | Assembled MD for a task |\n| `.chapters.json` | Chapter slug → title index |\n| `agent-manifest.json` | Discovery map of all downloads |\n| Knowledge SDK | `listUseCases`, `getUseCaseMarkdown`, `getBookMarkdown` |\n\n---\n\n## From: For Agents — 2. Discovery\n\nWithout the SDK:\n\n1. Open `/agent-manifest.json` on the deployed web app\n2. Follow `downloads/` paths for MD packs\n3. Prefer chapter indexes when slicing context\n\nWith the SDK: install the product knowledge package and call the typed helpers.\n\n---\n\n## From: For Agents — 3. Knowledge SDK\n\nPlatform factory: `@x12i/docify-sdk` → `createEbooksSdk(bundle)`.\n\nProduct packages pre-wire a bundle (catalog, use cases, site, manifest, embedded files). Example:\n\n```ts\nimport { memorixDocs } from \"@x12i/memorix-docs\";\n\nconst pack = memorixDocs.getUseCaseMarkdown(\"client-first-read-write\");\nconst book = memorixDocs.getBookMarkdown(\"02-runtime-data-client\", \"developers\");\nconst hits = memorixDocs.listUseCases({ audience: \"developers\", tag: \"http\" });\n```\n\nThis platform’s own package is `@x12i/docify-docs` (`docifyDocs`).\n\n---\n\n## From: For Agents — 4. Install contract\n\nKnowledge packages document the product for tools and agents. They are **not** a production runtime dependency.\n\n```bash\nnpm i -D @x12i/docify-docs    # this platform\nnpm i -D @x12i/memorix-docs   # Memorix product example\n```\n\nExport pipeline (`@x12i/docify-export`) emits MD + manifest alongside the web bundle. Stable use-case IDs keep agent prompts reproducible.\n\n## Also see\n\n- **For Agents** (`04-for-agents`) — MD packs, chapter indexes, agent-manifest.json, and createEbooksSdk — install knowledge as a devDependency.\n\n---\n\n_Generated use-case pack for agents and humans. See `agent-manifest.json` for discovery._\n",
-    "downloads/use-cases/ship-human-site.md": "# Ship the human web app\n\n> **Use case id:** `ship-human-site`\n> **Goal:** Build and serve dist/web with roles, use cases, catalog, and chapter reader.\n> **Audiences:** developers, builders\n> **Tags:** humans, web\n\n## Reading path\n\n1. **For Humans** (developers) → chapters: `1-best-form-for-humans`, `2-typical-flow`, `3-what-the-bundle-emits`\n\n## From: For Humans — 1. Best form for humans\n\nThe **web app** (`@x12i/docify-web`) is the human surface: case-file UI, role chooser, use-case routing, chapter reader, and download buttons.\n\nHumans should not be asked to scrape Markdown repos as their primary path. Deploy the static tree.\n\n---\n\n## From: For Humans — 2. Typical flow\n\n1. **Role** — pick developers / builders (or product-defined roles)\n2. **Use cases** — task-first entry; opens the right book + chapter\n3. **Catalog** — browse books by family\n4. **Reader** — chapter HTML in the shared book theme\n5. **Downloads** — MD (and PDF when built) for offline reading\n\nProduct home (`/`) and docs hub (`/docs`) are authored as site-pages with YAML front-matter.\n\n---\n\n## From: For Humans — 3. What the bundle emits\n\n| Path | Role |\n|---|---|\n| `index.html`, `docs.html`, … | Marketing / docs chrome from site-pages |\n| `books/<id>.html` | Book landings |\n| `read.html` + chapter HTML | Reader shell |\n| `catalog.json`, `use-cases.json`, `site.json` | Client data |\n| `downloads/` | MD / PDF / chapter indexes |\n| `agent-manifest.json` | Also useful for humans’ tooling links |\n\nAssemble with `buildContentBundle`, then overlay `docify-web/public` runtime assets (`app.js`, `read.html`, `agents.html`).\n\n---\n\n## Also see\n\n- **For Humans** (`03-for-humans`) — How people use @x12i/docify-web — roles, use cases, catalog, chapter reader, downloads.\n\n---\n\n_Generated use-case pack for agents and humans. See `agent-manifest.json` for discovery._\n",
-    "downloads/use-cases/wire-product-library.md": "# Wire a product docs library\n\n> **Use case id:** `wire-product-library`\n> **Goal:** Add books, data/*.json, site-pages, and build scripts in another monorepo without forking theme or web.\n> **Audiences:** developers, builders\n> **Tags:** authoring, getting-started\n\n## Reading path\n\n1. **Authoring a Library** (developers) → chapters: `1-recipe`, `2-content-layout`, `3-data-contracts`, `4-build-pipeline`\n\n## From: Authoring a Library — 1. Recipe\n\n1. Depend on `@x12i/docify-{core,theme,render,export,sdk,web}` — do **not** fork theme or web app.\n2. Author books as `NN-slug/{audience}/BOOK.md`.\n3. Add product data:\n   - `data/site.json` — `product`, `brand`, `brandAccent`, `siteUrl`, `knowledgePackage`\n   - `data/catalog.json` — roles, families, books (kickers / colors / titles)\n   - `data/use-cases.json` — task → book + chapter slugs\n4. Add `site-pages/*.md` with YAML front-matter (`product-home`, `docs-home`, …).\n5. Wire build scripts to import platform packages (see `memorix-docs/scripts/` or `x12i-docify/scripts/`).\n6. Publish `@your-scope/<product>-docs` as a **devDependency** knowledge SDK.\n7. Deploy `dist/web` for humans; ship MD + `agent-manifest.json` for agents.\n\n---\n\n## From: Authoring a Library — 2. Content layout\n\n```\n<product>-docs/\n  data/{site,catalog,use-cases}.json\n  site-pages/*.md\n  NN-slug/\n    developers/BOOK.md\n    builders/BOOK.md          # optional twin\n    site-pages/landing.md\n    diagrams/ … screenshots/\n  packages/<product>-docs/    # published knowledge SDK\n  scripts/build-bundle.mjs\n  scripts/build-knowledge.mjs\n  scripts/docs.mjs\n```\n\n---\n\n## From: Authoring a Library — 3. Data contracts\n\n| File | Owns |\n|---|---|\n| `site.json` | Brand chrome, accent CSS colors, nav, knowledge package name |\n| `catalog.json` | Roles (`developers` \\| `builders`), families, book metadata |\n| `use-cases.json` | Stable use-case ids + reading paths (bookId, audience, chapter slugs) |\n\nChapter slugs are produced by slugifying `##` headings in `BOOK.md`. Broken use-case paths **fail the bundle build**.\n\n---\n\n## From: Authoring a Library — 4. Build pipeline\n\nTypical scripts:\n\n| Script | Job |\n|---|---|\n| `build-bundle.mjs` | `buildContentBundle` → `dist/bundle` + assemble `dist/web` |\n| `build-knowledge.mjs` | Embed downloads + JSON into `packages/<sdk>/src/generated/bundle.ts` |\n| `docs.mjs` | Build if needed, `docify-web serve dist/web`, open browser |\n\nEnv: set `EBOOKS_PDF=0` or `DOCIFY_PDF=0` to skip PDF when `wkhtmltopdf` is unavailable.\n\n---\n\n## Also see\n\n- **Authoring a Library** (`02-authoring`) — Recipe to ship a product docs library: BOOK.md layout, data/*.json, site-pages, and the build pipeline.\n- **Design System** (`05-design`) — Shared theme tokens and surfaces — products change naming and content only.\n\n---\n\n_Generated use-case pack for agents and humans. See `agent-manifest.json` for discovery._\n",
-    "catalog.json": "{\"roles\":[{\"id\":\"developers\",\"label\":\"Developers\",\"tagline\":\"Wire the platform\",\"description\":\"Engineers who depend on @x12i/docify-* packages, ship product docs libraries, and publish knowledge SDKs.\"},{\"id\":\"builders\",\"label\":\"Builders\",\"tagline\":\"Author the library\",\"description\":\"Content authors who write BOOK.md, site-pages, catalog entries, and use-case paths — without forking theme or web UI.\"}],\"families\":[{\"id\":\"docify\",\"name\":\"x12i-docify\",\"tagline\":\"Product site + docs + knowledge packs — one design system across monorepos.\",\"description\":\"Shared platform packages and this dogfooded docs library that documents them.\",\"color\":\"#16324f\"}],\"books\":[{\"id\":\"00-platform-overview\",\"familyId\":\"docify\",\"audiences\":[\"developers\",\"builders\"],\"status\":\"available\",\"kicker\":\"CASE FILE · DOC-00\",\"title\":\"Platform Overview\",\"subtitle\":\"Humans and agents, one library\",\"blurb\":\"What x12i-docify is, who it serves, and how product libraries plug in without forking UI.\",\"tags\":[\"platform\",\"start-here\",\"overview\"],\"color\":\"#16324f\",\"dir\":\"00-platform-overview\"},{\"id\":\"01-packages\",\"familyId\":\"docify\",\"audiences\":[\"developers\"],\"status\":\"available\",\"kicker\":\"CASE FILE · DOC-01\",\"title\":\"Packages\",\"subtitle\":\"The @x12i/docify-* map\",\"blurb\":\"Core, theme, render, export, SDK, web, and screenshots — what each package owns.\",\"tags\":[\"packages\",\"npm\",\"platform\"],\"color\":\"#1f6e5c\",\"dir\":\"01-packages\"},{\"id\":\"02-authoring\",\"familyId\":\"docify\",\"audiences\":[\"developers\",\"builders\"],\"status\":\"available\",\"kicker\":\"CASE FILE · DOC-02\",\"title\":\"Authoring a Library\",\"subtitle\":\"Books, data, site-pages, build\",\"blurb\":\"Recipe to ship a product docs library: BOOK.md layout, data/*.json, site-pages, and the build pipeline.\",\"tags\":[\"authoring\",\"content\",\"getting-started\"],\"color\":\"#a5710f\",\"dir\":\"02-authoring\"},{\"id\":\"03-for-humans\",\"familyId\":\"docify\",\"audiences\":[\"developers\",\"builders\"],\"status\":\"available\",\"kicker\":\"CASE FILE · DOC-03\",\"title\":\"For Humans\",\"subtitle\":\"The web app path\",\"blurb\":\"How people use @x12i/docify-web — roles, use cases, catalog, chapter reader, downloads.\",\"tags\":[\"humans\",\"web\",\"reader\"],\"color\":\"#b14a2c\",\"dir\":\"03-for-humans\",\"buildersPrimary\":true},{\"id\":\"04-for-agents\",\"familyId\":\"docify\",\"audiences\":[\"developers\"],\"status\":\"available\",\"kicker\":\"CASE FILE · DOC-04\",\"title\":\"For Agents\",\"subtitle\":\"Markdown + knowledge SDK\",\"blurb\":\"MD packs, chapter indexes, agent-manifest.json, and createEbooksSdk — install knowledge as a devDependency.\",\"tags\":[\"agents\",\"sdk\",\"markdown\"],\"color\":\"#5b3d8f\",\"dir\":\"04-for-agents\"},{\"id\":\"05-design\",\"familyId\":\"docify\",\"audiences\":[\"developers\",\"builders\"],\"status\":\"available\",\"kicker\":\"CASE FILE · DOC-05\",\"title\":\"Design System\",\"subtitle\":\"One look across monorepos\",\"blurb\":\"Shared theme tokens and surfaces — products change naming and content only.\",\"tags\":[\"design\",\"theme\",\"brand\"],\"color\":\"#16324f\",\"dir\":\"05-design\"}]}",
-    "use-cases.json": "{\"useCases\":[{\"id\":\"orient-docify\",\"title\":\"Orient on x12i-docify\",\"goal\":\"Understand the dual-audience platform and where product libraries fit.\",\"audiences\":[\"developers\",\"builders\"],\"tags\":[\"platform\",\"start-here\"],\"path\":[{\"bookId\":\"00-platform-overview\",\"audience\":\"developers\",\"chapters\":[\"the-central-idea\",\"1-what-x12i-docify-is\",\"2-layers\",\"4-where-to-go-next\"]}],\"alsoSee\":[\"00-platform-overview\"]},{\"id\":\"map-packages\",\"title\":\"Map the @x12i/docify-* packages\",\"goal\":\"Know which package owns schemas, theme, render, export, SDK, web, and screenshots.\",\"audiences\":[\"developers\"],\"tags\":[\"packages\",\"npm\"],\"path\":[{\"bookId\":\"01-packages\",\"audience\":\"developers\",\"chapters\":[\"1-package-table\",\"2-dependency-shape\",\"3-publish-and-install\"]}],\"alsoSee\":[\"01-packages\"]},{\"id\":\"wire-product-library\",\"title\":\"Wire a product docs library\",\"goal\":\"Add books, data/*.json, site-pages, and build scripts in another monorepo without forking theme or web.\",\"audiences\":[\"developers\",\"builders\"],\"tags\":[\"authoring\",\"getting-started\"],\"path\":[{\"bookId\":\"02-authoring\",\"audience\":\"developers\",\"chapters\":[\"1-recipe\",\"2-content-layout\",\"3-data-contracts\",\"4-build-pipeline\"]}],\"alsoSee\":[\"02-authoring\",\"05-design\"]},{\"id\":\"ship-human-site\",\"title\":\"Ship the human web app\",\"goal\":\"Build and serve dist/web with roles, use cases, catalog, and chapter reader.\",\"audiences\":[\"developers\",\"builders\"],\"tags\":[\"humans\",\"web\"],\"path\":[{\"bookId\":\"03-for-humans\",\"audience\":\"developers\",\"chapters\":[\"1-best-form-for-humans\",\"2-typical-flow\",\"3-what-the-bundle-emits\"]}],\"alsoSee\":[\"03-for-humans\"]},{\"id\":\"ship-agent-packs\",\"title\":\"Ship agent markdown and knowledge SDK\",\"goal\":\"Export MD packs, agent-manifest.json, and a product @…-docs package for npm i -D.\",\"audiences\":[\"developers\"],\"tags\":[\"agents\",\"sdk\"],\"path\":[{\"bookId\":\"04-for-agents\",\"audience\":\"developers\",\"chapters\":[\"1-best-form-for-agents\",\"2-discovery\",\"3-knowledge-sdk\",\"4-install-contract\"]}],\"alsoSee\":[\"04-for-agents\"]},{\"id\":\"keep-one-design\",\"title\":\"Keep one design system\",\"goal\":\"Change product naming and content only — never fork theme or invent a competing palette.\",\"audiences\":[\"developers\",\"builders\"],\"tags\":[\"design\",\"theme\"],\"path\":[{\"bookId\":\"05-design\",\"audience\":\"builders\",\"chapters\":[\"1-principle\",\"2-identity\",\"3-surfaces\",\"4-do-not\"]}],\"alsoSee\":[\"05-design\"]}]}",
-    "site.json": "{\"product\":\"docify\",\"brand\":\"x12i · docify\",\"brandAccent\":\"docify\",\"siteUrl\":\"https://docs.docify.x12i.com\",\"knowledgePackage\":\"@x12i/docify-docs\",\"footer\":\"x12i-docify\",\"accent\":\"oklch(55% 0.15 260)\",\"accentAlt\":\"oklch(60% 0.15 40)\",\"productUrl\":\"https://github.com/x12i/memorix-mono-repo/tree/main/x12i-docify\",\"nav\":[{\"label\":\"Getting started\",\"href\":\"/getting-started\"},{\"label\":\"Use cases\",\"href\":\"/use-cases\"},{\"label\":\"Catalog\",\"href\":\"/catalog\"}],\"footerLinks\":[{\"label\":\"Docs home\",\"href\":\"/docs\"},{\"label\":\"Getting started\",\"href\":\"/getting-started\"},{\"label\":\"Use cases\",\"href\":\"/use-cases\"},{\"label\":\"Catalog\",\"href\":\"/catalog\"},{\"label\":\"Agents/SDK\",\"href\":\"/agents\"},{\"label\":\"Platform README\",\"href\":\"https://github.com/x12i/memorix-mono-repo/tree/main/x12i-docify\"}]}",
-    "agent-manifest.json": "{\"version\":1,\"product\":\"docify\",\"site\":\"https://docs.docify.x12i.com\",\"knowledgePackage\":\"@x12i/docify-docs\",\"roles\":[\"developers\",\"builders\"],\"books\":[{\"id\":\"00-platform-overview\",\"audiences\":[\"developers\",\"builders\"],\"md\":{\"developers\":\"downloads/books/00-platform-overview/developers.md\",\"builders\":\"downloads/books/00-platform-overview/builders.md\"},\"pdf\":{\"developers\":null,\"builders\":null},\"chapters\":{\"developers\":\"downloads/books/00-platform-overview/developers.chapters.json\",\"builders\":\"downloads/books/00-platform-overview/builders.chapters.json\"}},{\"id\":\"01-packages\",\"audiences\":[\"developers\"],\"md\":{\"developers\":\"downloads/books/01-packages/developers.md\"},\"pdf\":{\"developers\":null},\"chapters\":{\"developers\":\"downloads/books/01-packages/developers.chapters.json\"}},{\"id\":\"02-authoring\",\"audiences\":[\"developers\",\"builders\"],\"md\":{\"developers\":\"downloads/books/02-authoring/developers.md\",\"builders\":\"downloads/books/02-authoring/builders.md\"},\"pdf\":{\"developers\":null,\"builders\":null},\"chapters\":{\"developers\":\"downloads/books/02-authoring/developers.chapters.json\",\"builders\":\"downloads/books/02-authoring/builders.chapters.json\"}},{\"id\":\"03-for-humans\",\"audiences\":[\"developers\",\"builders\"],\"md\":{\"developers\":\"downloads/books/03-for-humans/developers.md\",\"builders\":\"downloads/books/03-for-humans/builders.md\"},\"pdf\":{\"developers\":null,\"builders\":null},\"chapters\":{\"developers\":\"downloads/books/03-for-humans/developers.chapters.json\",\"builders\":\"downloads/books/03-for-humans/builders.chapters.json\"}},{\"id\":\"04-for-agents\",\"audiences\":[\"developers\"],\"md\":{\"developers\":\"downloads/books/04-for-agents/developers.md\"},\"pdf\":{\"developers\":null},\"chapters\":{\"developers\":\"downloads/books/04-for-agents/developers.chapters.json\"}},{\"id\":\"05-design\",\"audiences\":[\"developers\",\"builders\"],\"md\":{\"developers\":\"downloads/books/05-design/developers.md\",\"builders\":\"downloads/books/05-design/builders.md\"},\"pdf\":{\"developers\":null,\"builders\":null},\"chapters\":{\"developers\":\"downloads/books/05-design/developers.chapters.json\",\"builders\":\"downloads/books/05-design/builders.chapters.json\"}}],\"useCases\":[{\"id\":\"orient-docify\",\"title\":\"Orient on x12i-docify\",\"md\":\"downloads/use-cases/orient-docify.md\",\"path\":[{\"bookId\":\"00-platform-overview\",\"audience\":\"developers\",\"chapters\":[\"the-central-idea\",\"1-what-x12i-docify-is\",\"2-layers\",\"4-where-to-go-next\"]}]},{\"id\":\"map-packages\",\"title\":\"Map the @x12i/docify-* packages\",\"md\":\"downloads/use-cases/map-packages.md\",\"path\":[{\"bookId\":\"01-packages\",\"audience\":\"developers\",\"chapters\":[\"1-package-table\",\"2-dependency-shape\",\"3-publish-and-install\"]}]},{\"id\":\"wire-product-library\",\"title\":\"Wire a product docs library\",\"md\":\"downloads/use-cases/wire-product-library.md\",\"path\":[{\"bookId\":\"02-authoring\",\"audience\":\"developers\",\"chapters\":[\"1-recipe\",\"2-content-layout\",\"3-data-contracts\",\"4-build-pipeline\"]}]},{\"id\":\"ship-human-site\",\"title\":\"Ship the human web app\",\"md\":\"downloads/use-cases/ship-human-site.md\",\"path\":[{\"bookId\":\"03-for-humans\",\"audience\":\"developers\",\"chapters\":[\"1-best-form-for-humans\",\"2-typical-flow\",\"3-what-the-bundle-emits\"]}]},{\"id\":\"ship-agent-packs\",\"title\":\"Ship agent markdown and knowledge SDK\",\"md\":\"downloads/use-cases/ship-agent-packs.md\",\"path\":[{\"bookId\":\"04-for-agents\",\"audience\":\"developers\",\"chapters\":[\"1-best-form-for-agents\",\"2-discovery\",\"3-knowledge-sdk\",\"4-install-contract\"]}]},{\"id\":\"keep-one-design\",\"title\":\"Keep one design system\",\"md\":\"downloads/use-cases/keep-one-design.md\",\"path\":[{\"bookId\":\"05-design\",\"audience\":\"builders\",\"chapters\":[\"1-principle\",\"2-identity\",\"3-surfaces\",\"4-do-not\"]}]}]}"
-};
-//# sourceMappingURL=bundle.js.map