@bendyline/gilde 0.1.70 → 0.1.72

package/data/craftbook-templates/co/content-accuracy-review/versions/1.1.0/test.json

@@ -0,0 +1,167 @@
+{
+  "schemaVersion": 1,
+  "title": "Claim-level accuracy review from evidence pack",
+  "objective": "Measure whether the content-accuracy-review craftbook extracts checkable claims and writes sourced true/false/misleading/unverifiable verdicts.",
+  "tags": [
+    "corpus"
+  ],
+  "prompt": "In the `Content Accuracy Review Eval` project, read only `source/article.md` and `source/evidence-pack.md`, then write `tasks/eval/accuracy-review.md`. Extract the six checkable claims in the article, rate each true/false/misleading/unverifiable, cite the evidence pack, give corrections, and include an overall trust rating. Do not add claims, companies, sources, or metrics beyond the seeded article and evidence pack.",
+  "setup": {
+    "projectName": "Content Accuracy Review Eval",
+    "about": "Self-contained eval project for content-accuracy-review. The draft article and evidence pack are seeded in workspace/source.",
+    "missionObjectives": "Produce a claim-by-claim accuracy review with verdicts, corrections, sources, and a trust rating.",
+    "files": [
+      {
+        "path": "source/article.md",
+        "content": "# Draft article\n\nHarborCRM launched guided returns intake in February 2026. The pilot covered all SKUs and reduced median first response from 18 hours to 4 hours. Refund leakage fell from 14.2% to 8.9%. Support escalations dropped 21% after agents received recommended resolution scripts. The company guarantees national rollout in July.\n"
+      },
+      {
+        "path": "source/evidence-pack.md",
+        "content": "# Evidence pack\n\n- Launch memo: guided returns intake pilot launched in March 2026, not February.\n- Pilot scope: 18 home-office accessory SKUs, not all SKUs.\n- Metrics dashboard: median first response improved from 18 hours to 6 hours.\n- Metrics dashboard: refund leakage fell from 14.2% to 8.9%.\n- Support report: escalations dropped 21% after recommended resolution scripts were added.\n- Roadmap note: national rollout is proposed for July but not guaranteed.\n"
+      }
+    ],
+    "worker": {
+      "name": "Kiki",
+      "role": "Fact Checker"
+    },
+    "craftbookParams": {
+      "workPath": "tasks/eval",
+      "source": "source/article.md"
+    }
+  },
+  "mocks": [],
+  "success": {
+    "summary": "workspace/accuracy-review.md extracts seeded claims, assigns verdicts, cites evidence, corrects false/misleading claims, and gives an overall trust rating.",
+    "deliverables": [
+      {
+        "path": "tasks/eval/accuracy-review.md",
+        "kind": "markdown-report",
+        "minBytes": 1600,
+        "checks": [
+          {
+            "kind": "contains",
+            "file": "tasks/eval/accuracy-review.md",
+            "pattern": "(?:^|\\n)#{1,3}\\s+\\S",
+            "flags": "i",
+            "artifact": true
+          },
+          {
+            "kind": "contains",
+            "file": "tasks/eval/accuracy-review.md",
+            "pattern": "TRUE|FALSE|MISLEADING|UNVERIFIABLE|trust rating",
+            "flags": "i",
+            "artifact": true
+          },
+          {
+            "kind": "contains",
+            "file": "tasks/eval/accuracy-review.md",
+            "pattern": "February|March|all SKUs|18 home-office",
+            "flags": "i",
+            "artifact": true
+          },
+          {
+            "kind": "contains",
+            "file": "tasks/eval/accuracy-review.md",
+            "pattern": "18\\s*hours|4\\s*hours|6\\s*hours|14\\.2%|8\\.9%|21%",
+            "flags": "i",
+            "artifact": true
+          },
+          {
+            "kind": "contains",
+            "file": "tasks/eval/accuracy-review.md",
+            "pattern": "correction|correct statement|source|evidence",
+            "flags": "i",
+            "artifact": true
+          },
+          {
+            "kind": "contains",
+            "file": "tasks/eval/accuracy-review.md",
+            "pattern": "guarantees national rollout|proposed for July",
+            "flags": "i",
+            "artifact": true
+          },
+          {
+            "kind": "contains",
+            "file": "tasks/eval/accuracy-review.md",
+            "pattern": "February[\\s\\S]{0,250}False|False[\\s\\S]{0,250}February",
+            "flags": "i",
+            "artifact": true
+          },
+          {
+            "kind": "contains",
+            "file": "tasks/eval/accuracy-review.md",
+            "pattern": "all SKUs[\\s\\S]{0,250}False|False[\\s\\S]{0,250}all SKUs",
+            "flags": "i",
+            "artifact": true
+          },
+          {
+            "kind": "contains",
+            "file": "tasks/eval/accuracy-review.md",
+            "pattern": "4\\s*hours[\\s\\S]{0,250}(False|Misleading)|(False|Misleading)[\\s\\S]{0,250}4\\s*hours",
+            "flags": "i",
+            "artifact": true
+          },
+          {
+            "kind": "contains",
+            "file": "tasks/eval/accuracy-review.md",
+            "pattern": "14\\.2%[\\s\\S]{0,250}True|8\\.9%[\\s\\S]{0,250}True|True[\\s\\S]{0,250}14\\.2%",
+            "flags": "i",
+            "artifact": true
+          },
+          {
+            "kind": "contains",
+            "file": "tasks/eval/accuracy-review.md",
+            "pattern": "21%[\\s\\S]{0,250}True|True[\\s\\S]{0,250}21%",
+            "flags": "i",
+            "artifact": true
+          },
+          {
+            "kind": "contains",
+            "file": "tasks/eval/accuracy-review.md",
+            "pattern": "guarantees[\\s\\S]{0,300}(False|Misleading)|(False|Misleading)[\\s\\S]{0,300}guarantees",
+            "flags": "i",
+            "artifact": true
+          },
+          {
+            "kind": "notContains",
+            "file": "tasks/eval/accuracy-review.md",
+            "pattern": "Q3|AlphaCorp|enterprise software|cash reserve|dominant market|CEO announced|RESTful API|stress tests",
+            "flags": "i",
+            "label": "do not invent review claims or evidence beyond the seeded article",
+            "artifact": true
+          }
+        ],
+        "artifact": true
+      }
+    ]
+  },
+  "rubric": {
+    "artifact": {
+      "path": "tasks/eval/accuracy-review.md",
+      "kind": "markdown"
+    },
+    "axes": [
+      {
+        "name": "grounding",
+        "description": "Seeded facts appear faithfully and the source is cited."
+      },
+      {
+        "name": "structure",
+        "description": "Sections progress logically for the artifact class."
+      },
+      {
+        "name": "completeness",
+        "description": "Required elements (risks, next actions, scope) are all present."
+      },
+      {
+        "name": "tone",
+        "description": "The register fits the audience and artifact class."
+      }
+    ]
+  },
+  "qualityFocus": [
+    "claim extraction",
+    "evidence-backed verdicts",
+    "corrections"
+  ]
+}

package/data/craftbook-templates/eb/ebook-compile/versions/1.1.0/craftbook.json

@@ -0,0 +1,332 @@
+{
+  "id": "ebook-compile",
+  "name": "Ebook Compile",
+  "description": "Compile a collection of notes, articles, or chapter drafts into a coherent, readable ebook — with a title page, table of contents, consistently formatted chapters, and front/back matter — output as a single navigable HTML book. Outlines the chapter structure and through-line FIRST (so disparate notes become a real book, not a pile), writes/edits each chapter to a consistent voice and adds connective tissue, then builds the compiled HTML with a linked TOC and chapter navigation. Use for turning a blog backlog, course notes, or drafts into a downloadable ebook.\n\nIt works on the source material you choose when you launch it: a folder in this project, read where it is, or notes you pick from your computer.\n\nA gallery craftbook generated from an archetype spec. It runs\n`phase → (per-phase gate) → … → evaluate → (loop) → finish`. Each build\nphase that produces a checkable artifact is followed by a **runtime\ngate-checkpoint** — the runtime verifies the artifact and routes with no\nmodel turn, looping back to redo the phase on a miss. The final `evaluate`\nstep holds a static deliverable gate plus a reviewer QA pass. What it adds\nover the generic `build-loop`: a specialist role per phase, a\ndomain-correct ordering, and a concrete per-phase quality bar.\n\nDeliverables marked \"artifact\" land in the project's artifacts drawer (`write_artifact` / `read_artifact`), not the shipped workspace — review output is not product source.\n\nPhases:\n\n1. Outline the book (planner) — chapter order, through-line, and front/back matter → gated on artifact `{{workPath}}/outline.md` (markdown-notes)\n2. Write and edit chapters (copywriter) — edit each chapter to one voice + add connective transitions → gated on artifact `{{workPath}}/write.md` (markdown-notes)\n3. Build the ebook (developer) — compile index.html: title page, linked TOC, chapter nav → gated on `index.html` (html-page)\n\nThe gates never advance with an unmet criterion, and loop back to the\nowning phase to fix named gaps.\n",
+  "entryStepId": "outline",
+  "triggers": [
+    "compile an ebook",
+    "make an ebook",
+    "turn my notes into a book",
+    "ebook from articles",
+    "build a book",
+    "create an ebook"
+  ],
+  "paramSchema": {
+    "type": "object",
+    "required": [
+      "source"
+    ],
+    "properties": {
+      "source": {
+        "type": "string",
+        "title": "Source content",
+        "description": "The notes, articles, or chapter drafts to compile. A folder in this project, or one you pick from your computer.",
+        "input": {
+          "kind": "folder",
+          "accept": [
+            ".md",
+            ".markdown",
+            ".txt",
+            ".html",
+            ".htm",
+            ".docx",
+            ".pdf"
+          ]
+        }
+      },
+      "workPath": {
+        "type": "string",
+        "title": "Working folder",
+        "description": "Per-task working folder in the artifacts drawer. Defaults to this task's own folder so runs never collide; override with a stable name when you deliberately want runs to share files.",
+        "default": "{{task.dir}}"
+      }
+    }
+  },
+  "steps": [
+    {
+      "id": "outline",
+      "name": "Outline the book",
+      "description": "chapter order, through-line, and front/back matter",
+      "prompt": "Turn the raw material into a book structure. Step 1: read EVERY file of the `source` input. Its complete file list is `{{task.dir}}/inputs/source.json`, and the invocation parameters above say where the files are and how to open them. Identify the central through-line or argument that will make them cohere. Step 2: group and order the material into chapters/parts that build logically; cut or merge redundant pieces. Step 3: plan the front matter (title page, optional preface/intro, table of contents) and back matter (conclusion, about, resources). Step 4: for each chapter note its title, the source files it draws from (by their exact paths from the file list), and the transition that links it to the next. Name any source file you deliberately cut, and why. Step 5: write an acceptance-criteria checklist ('has a title page + linked table of contents', 'chapters are ordered to a clear through-line', 'each chapter opens and closes cleanly with transitions', 'consistent heading levels throughout', 'front and back matter present'). Write the chapter map + checklist via write_task_note AND to {{workPath}}/outline.md. No chapter prose or HTML yet.\n\nThe deliverable `{{workPath}}/outline.md` lands in the project's artifacts drawer — write it with `write_artifact` and read it back with `read_artifact`; the shipped workspace stays untouched.",
+      "suggestedRole": "planner",
+      "advanceWhen": {
+        "file": "{{workPath}}/outline.md",
+        "minBytes": 1,
+        "sniff": "nonempty",
+        "artifact": true
+      },
+      "gate": {
+        "at": "completion",
+        "checks": [
+          {
+            "kind": "minBytes",
+            "file": "{{workPath}}/outline.md",
+            "bytes": 120,
+            "artifact": true
+          },
+          {
+            "kind": "sniff",
+            "file": "{{workPath}}/outline.md",
+            "sniff": "nonempty",
+            "artifact": true
+          }
+        ],
+        "onReject": "outline",
+        "maxAttempts": 3
+      },
+      "next": "write",
+      "toolPolicy": {
+        "disallowBuiltinToolsets": [
+          "ai-apps",
+          "archives",
+          "audio",
+          "browser-automation",
+          "code-execution",
+          "craftbooks",
+          "data-tables",
+          "entity-intel",
+          "git",
+          "image-intel",
+          "images",
+          "role-delegation",
+          "role-delegation-escalation",
+          "security-intel",
+          "team-management",
+          "videos",
+          "web",
+          "workspace-fs-write"
+        ],
+        "outputMedium": "artifact",
+        "additionalOutputMedia": [
+          "task-note"
+        ]
+      },
+      "consumes": [
+        {
+          "file": "{{task.dir}}/inputs/source.json",
+          "artifact": true
+        }
+      ]
+    },
+    {
+      "id": "write",
+      "name": "Write and edit chapters",
+      "description": "edit each chapter to one voice + add connective transitions",
+      "prompt": "Write/edit the chapters so the book reads as one work. Step 1: for each chapter in the outline, in order, re-read the source files it draws from (the outline names their paths) and shape that material into clean prose with a consistent voice, tense, and terminology (disparate notes often clash — unify them). Step 2: give each chapter a clear opening that orients the reader and a close that lands the point and transitions to the next chapter. Step 3: write the preface/intro that sets up the through-line and the conclusion that ties it together. Step 4: standardize formatting decisions — heading levels, how lists/quotes/code appear — so they are uniform across chapters. Step 5: keep the reader's journey in mind: no chapter should feel like an orphaned blog post. Write the per-chapter edited text + front/back matter via write_task_note AND to {{workPath}}/write.md.\n\nThe deliverable `{{workPath}}/write.md` lands in the project's artifacts drawer — write it with `write_artifact` and read it back with `read_artifact`; the shipped workspace stays untouched.",
+      "suggestedRole": "copywriter",
+      "advanceWhen": {
+        "file": "{{workPath}}/write.md",
+        "minBytes": 1,
+        "sniff": "nonempty",
+        "artifact": true
+      },
+      "gate": {
+        "at": "completion",
+        "checks": [
+          {
+            "kind": "minBytes",
+            "file": "{{workPath}}/write.md",
+            "bytes": 120,
+            "artifact": true
+          },
+          {
+            "kind": "sniff",
+            "file": "{{workPath}}/write.md",
+            "sniff": "nonempty",
+            "artifact": true
+          }
+        ],
+        "onReject": "write",
+        "maxAttempts": 3
+      },
+      "next": "build",
+      "toolPolicy": {
+        "disallowBuiltinToolsets": [
+          "ai-apps",
+          "archives",
+          "audio",
+          "browser-automation",
+          "code-execution",
+          "craftbooks",
+          "data-tables",
+          "entity-intel",
+          "git",
+          "image-intel",
+          "images",
+          "role-delegation",
+          "role-delegation-escalation",
+          "security-intel",
+          "team-management",
+          "videos",
+          "web",
+          "workspace-fs-write"
+        ],
+        "outputMedium": "artifact",
+        "additionalOutputMedia": [
+          "task-note"
+        ]
+      },
+      "consumes": [
+        {
+          "file": "{{workPath}}/outline.md",
+          "artifact": true
+        },
+        {
+          "file": "{{task.dir}}/inputs/source.json",
+          "artifact": true
+        }
+      ]
+    },
+    {
+      "id": "build",
+      "name": "Build the ebook",
+      "description": "compile index.html: title page, linked TOC, chapter nav",
+      "prompt": "First open `{{workPath}}/write.md`, `{{workPath}}/outline.md` with `read_artifact`: they are the earlier work this step builds on. Compile the book as a single self-contained index.html (inline CSS, no external assets). Step 1: build a title page (title, subtitle, author) as the opening screen. Step 2: build a Table of Contents with in-page anchor links to every chapter. Step 3: render each chapter in order with a stable id, consistent heading hierarchy, comfortable reading width and line-height, and the unified formatting from the edit phase. Step 4: add chapter navigation — previous/next links and a back-to-TOC link at each chapter boundary — and use page-break-before per chapter so it also prints/exports as a clean book. Step 5: include the front matter (preface) and back matter (conclusion, about/resources). Drop in the edited prose from `{{workPath}}/write.md` verbatim; do not re-edit the voice here. On a loop-back, fix ONLY the named gaps. Write the path + chapter count via write_task_note.",
+      "suggestedRole": "developer",
+      "advanceWhen": {
+        "file": "index.html",
+        "minBytes": 1,
+        "sniff": "html-complete"
+      },
+      "gate": {
+        "at": "completion",
+        "checks": [
+          {
+            "kind": "minBytes",
+            "file": "index.html",
+            "bytes": 800
+          },
+          {
+            "kind": "htmlLint",
+            "file": "index.html"
+          }
+        ],
+        "scripts": [
+          {
+            "name": "checkHtmlComplete",
+            "scope": "standard",
+            "inputs": {
+              "file": "index.html"
+            }
+          }
+        ],
+        "onReject": "build",
+        "maxAttempts": 4
+      },
+      "next": "evaluate",
+      "toolPolicy": {
+        "disallowBuiltinToolsets": [
+          "ai-apps",
+          "archives",
+          "audio",
+          "browser-automation",
+          "craftbooks",
+          "data-tables",
+          "entity-intel",
+          "git",
+          "image-intel",
+          "images",
+          "role-delegation",
+          "role-delegation-escalation",
+          "security-intel",
+          "team-management",
+          "videos",
+          "web"
+        ],
+        "outputMedium": "workspace",
+        "additionalOutputMedia": [
+          "task-note"
+        ]
+      },
+      "consumes": [
+        {
+          "file": "{{workPath}}/write.md",
+          "artifact": true
+        },
+        {
+          "file": "{{workPath}}/outline.md",
+          "artifact": true
+        }
+      ]
+    },
+    {
+      "id": "evaluate",
+      "name": "Evaluate",
+      "description": "Grade the deliverable against every acceptance criterion. All pass → finish; any fail → loop back and fix the gap.",
+      "prompt": "First open `{{workPath}}/outline.md`, `{{task.dir}}/inputs/source.json` with `read_artifact`: they are the earlier work this step builds on. QA the ebook against the locked criteria. Step 1: open/render index.html and click through the TOC links and chapter navigation. Step 2: check EACH acceptance criterion in the outline: title page present, a linked table of contents whose links all resolve to the right chapters, chapters ordered to the through-line, each chapter opens/closes with transitions, heading levels and formatting are consistent across chapters, and front + back matter are present. Step 3: read two non-adjacent chapters and confirm the voice is unified (not obviously stitched from clashing sources). Step 4: confirm chapter page-breaks work for print/export. Step 5: confirm every file in the source file list is represented in some chapter, or was cut on purpose in the outline — a dropped source is a FAIL. Write PASS/FAIL per criterion with the offending chapter on any FAIL.\n\nThen route — this is the whole point of the loop:\n\n- **Every criterion PASSES →** call `advance_task_step({ ref, stepId: \"evaluate\", next: \"finish\" })`.\n- **Any criterion FAILS →** write the specific gaps to notes, then call `advance_task_step({ ref, stepId: \"evaluate\", next: \"build\" })` to loop back. The builder fixes exactly those gaps.\n\nNever route to `finish` while any criterion is unmet. The build phase's completion gate already blocked a grossly-incomplete deliverable; your job is the judgment an automated check cannot make (does it actually work, read well, look right). After ~3 unproductive loops, stop and report DONE_WITH_CONCERNS so the user can step in.",
+      "suggestedRole": "reviewer",
+      "consumes": [
+        {
+          "file": "index.html"
+        },
+        {
+          "file": "{{workPath}}/outline.md",
+          "artifact": true
+        },
+        {
+          "file": "{{task.dir}}/inputs/source.json",
+          "artifact": true
+        }
+      ],
+      "next": "build",
+      "toolPolicy": {
+        "disallowBuiltinToolsets": [
+          "ai-apps",
+          "archives",
+          "audio",
+          "browser-automation",
+          "code-execution",
+          "craftbooks",
+          "data-tables",
+          "entity-intel",
+          "git",
+          "image-intel",
+          "images",
+          "role-delegation",
+          "role-delegation-escalation",
+          "security-intel",
+          "team-management",
+          "videos",
+          "web",
+          "workspace-fs-write"
+        ],
+        "outputMedium": "task-note"
+      }
+    },
+    {
+      "id": "finish",
+      "name": "Finish",
+      "description": "All acceptance criteria met. Stamp a short summary and report DONE.",
+      "prompt": "Every acceptance criterion passed. Write a one-paragraph DONE summary to task notes via `write_task_note`: what was built, the deliverable path(s), and a one-line confirmation that each criterion is met. Then report DONE.",
+      "suggestedRole": "developer",
+      "terminal": true,
+      "toolPolicy": {
+        "disallowBuiltinToolsets": [
+          "ai-apps",
+          "archives",
+          "artifacts",
+          "audio",
+          "browser-automation",
+          "code-execution",
+          "craftbooks",
+          "data-tables",
+          "entity-intel",
+          "git",
+          "image-intel",
+          "images",
+          "role-delegation",
+          "role-delegation-escalation",
+          "security-intel",
+          "team-management",
+          "videos",
+          "web",
+          "workspace-fs-write"
+        ],
+        "outputMedium": "task-note"
+      }
+    }
+  ],
+  "version": "1.1.0",
+  "releasedAt": "2026-09-24T12:00:00Z",
+  "minGezelVersion": "1.26267"
+}

package/data/craftbook-templates/eb/ebook-compile/versions/1.1.0/test.json

@@ -0,0 +1,111 @@
+{
+  "schemaVersion": 1,
+  "title": "Ebook Compile smoke eval",
+  "objective": "Compile a seeded folder of three chapter drafts, passed as the book's source input, into one navigable HTML ebook that draws on every draft.",
+  "tags": [
+    "html-page",
+    "craftbook-input"
+  ],
+  "prompt": "Can you turn my drafts into a little ebook? They're the notes in the drafts folder — keep my facts, just make it read like one book. One index.html is all we need.",
+  "setup": {
+    "projectName": "Ebook Compile Eval",
+    "about": "Self-contained eval project for ebook-compile. The source drafts are under workspace/drafts and are passed as the craftbook's source input; the final deliverable is workspace/index.html.",
+    "missionObjectives": "Use the Ebook Compile craftbook, read every draft in the source input, and write index.html without network calls, real credentials, or live services.",
+    "files": [
+      {
+        "path": "drafts/01-why-returns-matter.md",
+        "content": "# Why returns matter\n\nBoreal Desk sells home-office accessories. Our returns desk pilot covered 18 SKUs.\n\nMost customers who return something are not angry about the product. They are angry about silence: the top unresolved complaint is status silence after photo submission.\n"
+      },
+      {
+        "path": "drafts/02-what-the-pilot-changed.md",
+        "content": "# What the pilot changed\n\nMedian first response improved from 18 hours to 6 hours.\nPreventable refund leakage fell from 14.2% to 8.9%.\n\nThe biggest single win was answering first, even when the answer was only \"we have your photos\".\n"
+      },
+      {
+        "path": "drafts/03-next-steps.md",
+        "content": "# Next steps\n\nThree things come next: automated status emails, barcode-exception training, and a weekly Finance exception export.\n\nNone of them is expensive. All of them are about telling people what is happening.\n"
+      },
+      {
+        "path": "drafts/cover-sketch.png",
+        "content": "not really an image"
+      }
+    ],
+    "craftbookParams": {
+      "source": "drafts"
+    },
+    "worker": {
+      "name": "Jules",
+      "role": "Developer"
+    }
+  },
+  "mocks": [],
+  "success": {
+    "summary": "index.html is a self-contained ebook with a title page, a linked table of contents, and a chapter for the material of every draft.",
+    "deliverables": [
+      {
+        "path": "index.html",
+        "kind": "html-page",
+        "minBytes": 3000,
+        "checks": [
+          {
+            "kind": "cssMinBytes",
+            "bytes": 400,
+            "file": "index.html"
+          },
+          {
+            "kind": "contains",
+            "file": "index.html",
+            "pattern": "href=\"#",
+            "flags": "i"
+          },
+          {
+            "kind": "contains",
+            "file": "index.html",
+            "pattern": "status silence",
+            "flags": "i"
+          },
+          {
+            "kind": "contains",
+            "file": "index.html",
+            "pattern": "18\\s*hours[^<]{0,40}6\\s*hours|14\\.2%[^<]{0,40}8\\.9%",
+            "flags": "i"
+          },
+          {
+            "kind": "contains",
+            "file": "index.html",
+            "pattern": "barcode[- ]exception",
+            "flags": "i"
+          }
+        ]
+      }
+    ]
+  },
+  "rubric": {
+    "artifact": {
+      "path": "index.html",
+      "kind": "html"
+    },
+    "axes": [
+      {
+        "name": "structure",
+        "description": "A title page, a table of contents whose links resolve, and chapters ordered to one through-line."
+      },
+      {
+        "name": "grounding",
+        "description": "Every draft's facts appear, unchanged; nothing is invented and no draft is dropped."
+      },
+      {
+        "name": "voice",
+        "description": "The chapters read as one book, with transitions, not three stitched posts."
+      },
+      {
+        "name": "polish",
+        "description": "Comfortable reading width and consistent headings; chapters break cleanly for print."
+      }
+    ]
+  },
+  "qualityFocus": [
+    "source coverage",
+    "linked table of contents",
+    "unified voice"
+  ]
+}