@bendyline/gilde 0.1.38 → 0.1.39

package/data/craftbook-templates/ti/tileset-batch/versions/1.0.2/craftbook.json

@@ -0,0 +1,172 @@
+{
+  "id": "tileset-batch",
+  "name": "Tileset Batch",
+  "description": "Produce a style-locked batch of tiles and account for every one: named to the convention, sized to spec, generated against the library's style anchor, and appended to the manifest with tags — an asset library a game engine can trust, not a folder of maybes. Locks the tile list and the naming convention FIRST, then generates the batch in the house style, then writes the manifest records and the batch summary. Use for tile batches, 'we need forest tiles', growing a game's asset library, style-consistent tilesets, and keeping the asset manifest honest.\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. Lock the batch (assetsmid) — tile list, naming convention, size spec, style anchor → gated on artifact `{{workPath}}/scope.md` (markdown-notes)\n2. Generate the tiles (image-generator) — the batch, named to the convention, in the house style → gated on `assets/tiles` (image-set)\n3. Write the manifest records (data-analyst) — one record per new tile, appended, ids unique\n4. Write the batch summary (copywriter) — what was made, how it is named, what the library now holds → gated on artifact `{{workPath}}/report.md` (markdown-report)\n\nThe gates never advance with an unmet criterion, and loop back to the\nowning phase to fix named gaps.\n",
+  "entryStepId": "scope",
+  "triggers": [
+    "make a batch of tiles",
+    "we need more tiles for the game",
+    "tileset for the platformer",
+    "generate the tile batch",
+    "grow the asset library"
+  ],
+  "steps": [
+    {
+      "id": "scope",
+      "name": "Lock the batch",
+      "description": "tile list, naming convention, size spec, style anchor",
+      "prompt": "Lock the batch before generating a tile. Step 1: read assets/manifest.json from the workspace — the library's existing records — and the style notes in assets/ (the palette, tile size, outline and shading rules that make the library one family). Step 2: write the tile list from the ask — every tile the batch needs, including the unglamorous edges and corners that make a set usable, at least eight. Step 3: lock the conventions — file names as assets/tiles/tile-<terrain>-<variant>.png, the size spec from the style notes, and the tags each tile will carry. Step 4: write an acceptance-criteria checklist ('every listed tile generated at spec size in the house style', 'every file named to the convention', 'every new tile appended to the manifest with id, file, size, and tags', 'the manifest stays valid JSON and lists only files that exist'). Call write_task_note with the tile list + checklist and write {{workPath}}/scope.md.\n\nThe deliverable `{{workPath}}/scope.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": "assetsmid",
+      "advanceWhen": {
+        "file": "{{workPath}}/scope.md",
+        "minBytes": 1,
+        "sniff": "nonempty",
+        "artifact": true
+      },
+      "gate": {
+        "at": "completion",
+        "checks": [
+          {
+            "kind": "minBytes",
+            "file": "{{workPath}}/scope.md",
+            "bytes": 120,
+            "artifact": true
+          },
+          {
+            "kind": "sniff",
+            "file": "{{workPath}}/scope.md",
+            "sniff": "nonempty",
+            "artifact": true
+          }
+        ],
+        "onReject": "scope",
+        "maxAttempts": 3
+      },
+      "next": "generate"
+    },
+    {
+      "id": "generate",
+      "name": "Generate the tiles",
+      "description": "the batch, named to the convention, in the house style",
+      "prompt": "Generate the batch into assets/tiles/. Step 1: work the locked tile list one tile at a time through the project's image capabilities — every prompt built from the style anchor (palette, outline, shading) so the batch reads as one hand's work, saved under the locked naming convention. Step 2: keep the set complete — the edge and corner variants from the list matter more to a level builder than another hero tile. Step 3: after generating, re-list assets/tiles/ against the tile list and fill any gap before completing. Call write_task_note with the count generated and the names.",
+      "suggestedRole": "image-generator",
+      "advanceWhen": {
+        "file": "assets/tiles",
+        "minBytes": 1,
+        "sniff": "nonempty"
+      },
+      "gate": {
+        "at": "completion",
+        "checks": [
+          {
+            "kind": "fileCount",
+            "ext": [
+              "png",
+              "jpg",
+              "jpeg",
+              "svg",
+              "webp"
+            ],
+            "min": 3,
+            "dir": "assets/tiles"
+          },
+          {
+            "kind": "fileCount",
+            "ext": [
+              "png"
+            ],
+            "min": 8,
+            "dir": "assets/tiles"
+          }
+        ],
+        "onReject": "generate",
+        "maxAttempts": 3
+      },
+      "next": "manifest"
+    },
+    {
+      "id": "manifest",
+      "name": "Write the manifest records",
+      "description": "one record per new tile, appended, ids unique",
+      "prompt": "Account for every tile in assets/manifest.json. Step 1: append one record per new tile to the top-level JSON array, keeping the existing records untouched. Step 2: each record carries exactly these fields: \"id\" (unique, e.g. tile-grass-01), \"file\" (the workspace-relative path, e.g. assets/tiles/tile-grass-01.png), \"size\" (the pixel spec, e.g. 32x32), and \"tags\" (an array like [\"forest\", \"ground\"]) — plus \"seed\" and \"prompt\" where the generation gave you them, so a tile can be re-made in-style later. Step 3: re-read the whole file after writing — it must parse as JSON, ids must stay unique, and every recorded file must exist on disk; a manifest that lists a tile that is not there is worse than no manifest. Call write_task_note with the record count before and after.",
+      "suggestedRole": "data-analyst",
+      "consumes": [
+        {
+          "file": "assets/tiles"
+        }
+      ],
+      "next": "report"
+    },
+    {
+      "id": "report",
+      "name": "Write the batch summary",
+      "description": "what was made, how it is named, what the library now holds",
+      "prompt": "Write the batch summary at {{workPath}}/report.md. Step 1: the headline — how many tiles this batch added and what terrain they cover, in one plain sentence. Step 2: the batch list — each tile's id, file, and tags, one line each. Step 3: note the conventions used (naming, size, style anchor) so the next batch starts from the same page, and name anything from the ask that was skipped and why. Step 4: close with the library's new total. Keep it under a page. Write {{workPath}}/report.md and call write_task_note with the report path and the new total.\n\nThe deliverable `{{workPath}}/report.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}}/report.md",
+        "minBytes": 1,
+        "sniff": "nonempty",
+        "artifact": true
+      },
+      "gate": {
+        "at": "completion",
+        "checks": [
+          {
+            "kind": "minBytes",
+            "file": "{{workPath}}/report.md",
+            "bytes": 600,
+            "artifact": true
+          },
+          {
+            "kind": "contains",
+            "file": "{{workPath}}/report.md",
+            "pattern": "(?:^|\\n)#{1,3}\\s+\\S",
+            "flags": "i",
+            "label": "at least one markdown heading",
+            "artifact": true
+          }
+        ],
+        "onReject": "report",
+        "maxAttempts": 4
+      },
+      "next": "evaluate"
+    },
+    {
+      "id": "evaluate",
+      "name": "Evaluate",
+      "description": "Grade the deliverable against every acceptance criterion. All pass → finish; any fail → loop back and fix the gap.",
+      "prompt": "Open assets/manifest.json, the assets/tiles/ listing, {{workPath}}/scope.md, and {{workPath}}/report.md and verify every criterion: every tile on the locked list exists at the convention name — the missing corner variant is the classic failure; every new tile has a manifest record with id, file, size, and tags, ids unique, and every recorded path resolves to a real file — check both directions; the batch reads as one style family against the anchor notes; and the report's counts match the manifest. Write PASS/FAIL per criterion; on any failure, name the tile or record and loop back to generate.\n\nThe deliverable lives in the project's artifacts drawer — open `{{workPath}}/report.md` with `read_artifact`, not `read_file`.\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: \"generate\" })` 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": "{{workPath}}/report.md",
+          "artifact": true
+        }
+      ],
+      "next": "generate"
+    },
+    {
+      "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
+    }
+  ],
+  "version": "1.0.2",
+  "releasedAt": "2026-08-21T00:00:00Z",
+  "paramSchema": {
+    "type": "object",
+    "properties": {
+      "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}}"
+      }
+    }
+  },
+  "minGezelVersion": "1.26233"
+}

package/data/craftbook-templates/ti/tileset-batch/versions/1.0.2/test.json

@@ -0,0 +1,162 @@
+{
+  "schemaVersion": 1,
+  "title": "Tileset Batch — forest tiles, accounted for",
+  "objective": "Measure whether the tileset-batch craftbook produces a style-locked batch of forest tiles named to the library convention and appends an honest manifest record for every one — ids unique, every recorded file real.",
+  "tags": [
+    "data"
+  ],
+  "prompt": "need a batch of forest tiles for the platformer — grass, dirt, water edges, that kind of thing. keep the manifst updated",
+  "setup": {
+    "projectName": "Foxglove Platformer Assets",
+    "about": "Asset foundry project. The library's records live at workspace/assets/manifest.json (a JSON array, one record per asset) and the style anchor at workspace/assets/style.md. Tiles land in workspace/assets/tiles; the batch summary goes to workspace/report.md.",
+    "missionObjectives": "An asset library a game engine can trust: tiles at spec size in the house style, named to the convention, every one recorded in the manifest and no record pointing at a file that is not there. No live services, no real credentials.",
+    "files": [
+      {
+        "path": "assets/style.md",
+        "content": "# Asset library style anchor\n\n- Tile size: 32x32 pixels, no partial tiles.\n- Palette: moss green #4c7a3f, loam brown #6b4a2e, slate gray #5a6472,\n  water blue #3f6d8e, highlight cream #e8dcb8.\n- Look: chunky 2px dark outlines (#22201c), flat interior shading, one\n  highlight edge top-left. No gradients, no anti-aliased edges.\n- Naming: assets/tiles/tile-<terrain>-<variant>.png (e.g. tile-grass-01,\n  tile-water-edge-n).\n- Every shipped asset gets a manifest record: id, file, size, tags —\n  plus seed and prompt when generation provides them.\n"
+      },
+      {
+        "path": "assets/manifest.json",
+        "content": "[\n  {\n    \"id\": \"tile-stone-01\",\n    \"file\": \"assets/tiles/tile-stone-01.png\",\n    \"size\": \"32x32\",\n    \"tags\": [\n      \"stone\",\n      \"ground\"\n    ]\n  },\n  {\n    \"id\": \"tile-stone-02\",\n    \"file\": \"assets/tiles/tile-stone-02.png\",\n    \"size\": \"32x32\",\n    \"tags\": [\n      \"stone\",\n      \"ground\",\n      \"variant\"\n    ]\n  }\n]\n"
+      },
+      {
+        "path": "assets/tiles/tile-stone-01.png",
+        "content": "placeholder tile image: stone ground\n"
+      },
+      {
+        "path": "assets/tiles/tile-stone-02.png",
+        "content": "placeholder tile image: stone ground variant\n"
+      }
+    ],
+    "worker": {
+      "name": "Bram",
+      "role": "Assetsmid"
+    },
+    "craftbookParams": {
+      "workPath": "tasks/eval"
+    }
+  },
+  "mocks": [],
+  "success": {
+    "summary": "assets/tiles holds the forest batch named to the convention; assets/manifest.json accounts for every tile with unique ids and real paths; tasks/eval/report.md summarizes the batch.",
+    "checks": [
+      {
+        "kind": "fileCount",
+        "ext": [
+          "png"
+        ],
+        "min": 8,
+        "dir": "assets/tiles"
+      }
+    ],
+    "deliverables": [
+      {
+        "path": "assets/manifest.json",
+        "kind": "json",
+        "minBytes": 400,
+        "checks": [
+          {
+            "kind": "sniff",
+            "file": "assets/manifest.json",
+            "sniff": "json-valid"
+          },
+          {
+            "kind": "recordSchema",
+            "file": "assets/manifest.json",
+            "fields": [
+              {
+                "name": "id",
+                "type": "nonempty"
+              },
+              {
+                "name": "file",
+                "type": "nonempty"
+              },
+              {
+                "name": "size",
+                "required": false
+              },
+              {
+                "name": "tags",
+                "required": false
+              },
+              {
+                "name": "seed",
+                "required": false
+              },
+              {
+                "name": "prompt",
+                "required": false
+              }
+            ],
+            "minRows": 8,
+            "uniqueBy": "id"
+          },
+          {
+            "kind": "citationsResolve",
+            "file": "assets/manifest.json",
+            "pattern": "\"file\"\\s*:\\s*\"([^\"]+)\"",
+            "minCitations": 8,
+            "label": "every recorded file exists on disk"
+          },
+          {
+            "kind": "contains",
+            "file": "assets/manifest.json",
+            "pattern": "grass|dirt|water",
+            "flags": "i",
+            "label": "the asked-for terrain made the batch"
+          }
+        ]
+      },
+      {
+        "path": "tasks/eval/report.md",
+        "kind": "markdown-report",
+        "minBytes": 600,
+        "checks": [
+          {
+            "kind": "contains",
+            "file": "tasks/eval/report.md",
+            "pattern": "(?:^|\\n)#{1,3}\\s+\\S",
+            "flags": "i"
+          },
+          {
+            "kind": "contains",
+            "file": "tasks/eval/report.md",
+            "pattern": "tile",
+            "flags": "i",
+            "label": "the batch is summarized"
+          }
+        ]
+      }
+    ]
+  },
+  "rubric": {
+    "artifact": {
+      "path": "tasks/eval/report.md",
+      "kind": "markdown"
+    },
+    "axes": [
+      {
+        "name": "style consistency",
+        "description": "The batch reads as one hand's work against the style anchor — palette, outlines, and shading held across every tile."
+      },
+      {
+        "name": "naming discipline",
+        "description": "Every file follows tile-<terrain>-<variant>.png; the unglamorous edge and corner variants are there."
+      },
+      {
+        "name": "coverage",
+        "description": "The batch covers what was asked — grass, dirt, water edges — as a usable set, not eight hero tiles."
+      },
+      {
+        "name": "manifest quality",
+        "description": "Records are complete and honest: unique ids, real paths, useful tags, existing records untouched."
+      }
+    ]
+  },
+  "qualityFocus": [
+    "manifest honesty",
+    "naming convention",
+    "style lock"
+  ]
+}

package/data/craftbook-templates/to/tone-rewrite/versions/1.0.2/craftbook.json

@@ -0,0 +1,119 @@
+{
+  "id": "tone-rewrite",
+  "name": "Brand Tone Rewrite",
+  "description": "Re-voice existing content to a specific brand tone while preserving every fact and the original structure: it first codifies the target voice into a concrete style guide — adjectives, do's and don'ts, banned and preferred words, sentence-length feel, point of view — then rewrites the content line by line to that voice without changing what it says. Covers tone of voice rewrite, rebranding copy, voice and tone, brand voice, re-voice content, and style adaptation. Codifying the voice into checkable rules before rewriting is the point: a small model that has explicit do/don't rules applies the tone consistently, instead of a vague 'make it friendlier' that drifts paragraph to paragraph.\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. Voice scope (planner) — codify the target tone into a concrete, checkable style guide → gated on artifact `{{workPath}}/voice-scope.md` (markdown-notes)\n2. Rewrite to voice (copywriter) — re-voice the content to the style guide, preserving meaning → gated on `tone-rewrite.md` (markdown-doc)\n\nThe gates never advance with an unmet criterion, and loop back to the\nowning phase to fix named gaps.\n",
+  "entryStepId": "voice-scope",
+  "triggers": [
+    "rewrite in our brand tone",
+    "change the voice",
+    "re-voice this content",
+    "match brand voice",
+    "tone of voice"
+  ],
+  "steps": [
+    {
+      "id": "voice-scope",
+      "name": "Voice scope",
+      "description": "codify the target tone into a concrete, checkable style guide",
+      "prompt": "1) Define the target voice in 3-5 adjectives (e.g. 'confident, warm, plain-spoken'). 2) Translate each adjective into 1-2 concrete rules (e.g. 'confident → no hedging words like maybe/perhaps'; 'plain-spoken → grade-8 reading level, no jargon'). 3) List banned words/phrases and preferred replacements. 4) Set point of view (first/second person), contraction policy, sentence-length feel, and how to handle CTAs. 5) Write or pick one before/after example sentence showing the transformation. Crucially, note what must NOT change: facts, claims, structure, and meaning. Write an acceptance-criteria checklist (e.g. 'every banned word removed'; 'POV/contractions consistent'; 'reading level on target'; 'no fact or section changed'; 'reads as one consistent voice'). Use write_task_note for the style guide + checklist, and write the same to the produces path. No rewrite yet.\n\nThe deliverable `{{workPath}}/voice-scope.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}}/voice-scope.md",
+        "minBytes": 1,
+        "sniff": "nonempty",
+        "artifact": true
+      },
+      "gate": {
+        "at": "completion",
+        "checks": [
+          {
+            "kind": "minBytes",
+            "file": "{{workPath}}/voice-scope.md",
+            "bytes": 120,
+            "artifact": true
+          },
+          {
+            "kind": "sniff",
+            "file": "{{workPath}}/voice-scope.md",
+            "sniff": "nonempty",
+            "artifact": true
+          }
+        ],
+        "onReject": "voice-scope",
+        "maxAttempts": 3
+      },
+      "next": "rewrite"
+    },
+    {
+      "id": "rewrite",
+      "name": "Rewrite to voice",
+      "description": "re-voice the content to the style guide, preserving meaning",
+      "prompt": "Rewrite the content to the locked style guide. 1) Go section by section, preserving the original structure and headings exactly. 2) Apply every voice rule: remove banned words, use the specified POV and contraction policy, hit the target sentence feel and reading level. 3) Change HOW it reads, never WHAT it says — every fact, number, claim, and instruction must survive unchanged. 4) Keep the voice identical across the whole piece; no drift. 5) Output the rewritten content in the same format/markdown as the source. Save to the produces path and note which style rules you applied and confirm no facts changed.",
+      "suggestedRole": "copywriter",
+      "advanceWhen": {
+        "file": "tone-rewrite.md",
+        "minBytes": 1,
+        "sniff": "nonempty"
+      },
+      "gate": {
+        "at": "completion",
+        "checks": [
+          {
+            "kind": "minBytes",
+            "file": "tone-rewrite.md",
+            "bytes": 500
+          }
+        ],
+        "scripts": [
+          {
+            "name": "checkContains",
+            "scope": "standard",
+            "inputs": {
+              "file": "tone-rewrite.md",
+              "pattern": "(?:^|\\n)#{1,3}\\s+\\S",
+              "flags": "i"
+            }
+          }
+        ],
+        "onReject": "rewrite",
+        "maxAttempts": 4
+      },
+      "next": "evaluate"
+    },
+    {
+      "id": "evaluate",
+      "name": "Evaluate",
+      "description": "Grade the deliverable against every acceptance criterion. All pass → finish; any fail → loop back and fix the gap.",
+      "prompt": "Compare tone-rewrite.md to the source and the style guide. Check EACH criterion and write PASS/FAIL: (a) every banned word/phrase is gone and preferred terms used; (b) POV, contraction policy, and reading level match the guide; (c) NO fact, number, claim, or section was changed or dropped (diff the meaning carefully — this is critical); (d) structure/headings preserved; (e) reads as one consistent voice with no drift. A rewrite that nails the tone but altered a fact FAILS — loop back to rewrite.\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: \"rewrite\" })` 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": "tone-rewrite.md"
+        }
+      ],
+      "next": "rewrite"
+    },
+    {
+      "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
+    }
+  ],
+  "version": "1.0.2",
+  "releasedAt": "2026-08-21T00:00:00Z",
+  "paramSchema": {
+    "type": "object",
+    "properties": {
+      "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}}"
+      }
+    }
+  },
+  "minGezelVersion": "1.26233"
+}

package/data/craftbook-templates/to/tone-rewrite/versions/1.0.2/test.json

@@ -0,0 +1,113 @@
+{
+  "schemaVersion": 1,
+  "title": "Brand Tone Rewrite smoke eval",
+  "objective": "Self-contained smoke eval for the Brand Tone Rewrite craftbook using the corpus generic harness.",
+  "tags": [
+    "corpus"
+  ],
+  "prompt": "We need a brand tone rewrite for the returns-desk work. The backgound info is in source/brief.md — have a look and write it up in report.md.",
+  "setup": {
+    "projectName": "Brand Tone Rewrite Eval",
+    "about": "Self-contained eval project for tone-rewrite. Seeded inputs are under workspace/source or workspace/fixtures; final deliverable is workspace/report.md.",
+    "missionObjectives": "Use the Brand Tone Rewrite craftbook/template, read the seeded local fixtures, and write report.md without network calls, real credentials, or live services.",
+    "files": [
+      {
+        "path": "source/brief.md",
+        "content": "# Brand Tone Rewrite Eval Brief\n\nClient: Boreal Desk, a home-office accessories company.\nAudience: operations leads who need an artifact they can use this week.\n\nFixed source facts for grounding:\n- The returns desk pilot covered 18 SKUs.\n- Median first response improved from 18 hours to 6 hours.\n- Preventable refund leakage fell from 14.2% to 8.9%.\n- The top unresolved complaint is status silence after photo submission.\n- Required next actions are automated status emails, barcode-exception training, and a weekly Finance exception export.\n\nUse these facts when the task asks for prose, analysis, copy, UI content, or test data. Do not use live web services, real credentials, or current outside data.\n\nCraftbook under test: tone-rewrite - Brand Tone Rewrite.\n"
+      }
+    ],
+    "worker": {
+      "name": "Jules",
+      "role": "Writer"
+    },
+    "craftbookParams": {
+      "workPath": "tasks/eval"
+    }
+  },
+  "mocks": [],
+  "success": {
+    "summary": "report.md is a source-grounded markdown artifact with required facts and actions.",
+    "deliverables": [
+      {
+        "path": "report.md",
+        "kind": "markdown-report",
+        "minBytes": 1000,
+        "checks": [
+          {
+            "kind": "contains",
+            "file": "report.md",
+            "pattern": "(?:^|\\n)#{1,3}\\s+\\S",
+            "flags": "i"
+          },
+          {
+            "kind": "contains",
+            "file": "report.md",
+            "pattern": "source/brief\\.md|Brief",
+            "flags": "i",
+            "label": "cite or name the seeded source"
+          },
+          {
+            "kind": "contains",
+            "file": "report.md",
+            "pattern": "18\\b[\\s\\S]{0,30}\\bSKUs",
+            "flags": "i",
+            "label": "include the 18-SKU pilot scope"
+          },
+          {
+            "kind": "contains",
+            "file": "report.md",
+            "pattern": "18\\s*hours|6\\s*hours",
+            "flags": "i"
+          },
+          {
+            "kind": "contains",
+            "file": "report.md",
+            "pattern": "14\\.2%|8\\.9%",
+            "flags": "i"
+          },
+          {
+            "kind": "contains",
+            "file": "report.md",
+            "pattern": "status silence|photo submission",
+            "flags": "i"
+          },
+          {
+            "kind": "contains",
+            "file": "report.md",
+            "pattern": "automated status emails|barcode|Finance",
+            "flags": "i"
+          }
+        ]
+      }
+    ]
+  },
+  "rubric": {
+    "artifact": {
+      "path": "report.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": [
+    "source-grounded prose",
+    "section structure",
+    "next-action clarity"
+  ]
+}