@bendyline/gilde 0.2.4 → 0.2.6

package/data/craftbook-templates/mo/moodboard/versions/1.0.5/craftbook.json

@@ -0,0 +1,219 @@
+{
+  "id": "moodboard",
+  "name": "Visual Moodboard",
+  "description": "Compose a visual moodboard that captures a direction — palette, textures, type vibe, imagery, and reference tiles — from a written brief, so a team can align on a look before any production work begins. Lock the brief and the explicit dimensions of the mood (e.g. 'warm/editorial/handmade' vs 'cool/technical/precise') FIRST, then assemble a coherent grid of generated or sourced tiles plus a swatch strip and keyword callouts. Covers moodboards, style boards, visual direction, design inspiration, brand mood, and look-and-feel exploration.\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. Moodboard brief (visual-designer) — lock the mood dimensions, palette, and tile plan → gated on artifact `{{workPath}}/brief.md` (markdown-notes)\n2. Assemble the board (image-generator) — compose the coherent tile grid into one deliverable → 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": "brief",
+  "triggers": [
+    "make a moodboard",
+    "create a style board",
+    "visual direction board",
+    "design inspiration board",
+    "look and feel board"
+  ],
+  "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}}"
+      }
+    }
+  },
+  "steps": [
+    {
+      "id": "brief",
+      "name": "Moodboard brief",
+      "description": "lock the mood dimensions, palette, and tile plan",
+      "prompt": "1) Distill the direction into 3-5 mood keywords (e.g. warm, editorial, handmade, calm). 2) Lock a palette with hex swatches and the type vibe (serif/sans, weight, feeling). 3) Plan the tile grid: enumerate the tiles you'll include — e.g. 2-3 imagery tiles, a texture tile, a typography specimen tile, a palette strip — and what each should evoke. 4) Note explicit anti-references (what this is NOT) so the board has a point of view. 5) Write an acceptance-criteria checklist: 'board expresses the 3-5 keywords', 'palette swatches show exact hex', 'a typography specimen is present', 'tiles are cohesive (one direction, not a scrapbook)', 'at least 6 tiles'. 6) Record brief + checklist via write_task_note AND to {{workPath}}/brief.md. No assembly yet.\n\nThe deliverable `{{workPath}}/brief.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": "visual-designer",
+      "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"
+        ]
+      },
+      "advanceWhen": {
+        "file": "{{workPath}}/brief.md",
+        "minBytes": 1,
+        "sniff": "nonempty",
+        "artifact": true
+      },
+      "gate": {
+        "at": "completion",
+        "checks": [
+          {
+            "kind": "minBytes",
+            "file": "{{workPath}}/brief.md",
+            "bytes": 120,
+            "artifact": true
+          },
+          {
+            "kind": "sniff",
+            "file": "{{workPath}}/brief.md",
+            "sniff": "nonempty",
+            "artifact": true
+          }
+        ],
+        "onReject": "brief",
+        "maxAttempts": 3
+      },
+      "next": "assemble"
+    },
+    {
+      "id": "assemble",
+      "name": "Assemble the board",
+      "description": "compose the coherent tile grid into one deliverable",
+      "prompt": "1) Read brief.md. 2) Generate or compose each planned tile to express the locked keywords and palette — imagery tiles via the image-generation capability (or curated solid/gradient/texture blocks if no image model is available), a swatch strip rendering the exact hex values, and a type specimen tile showing the chosen pairing with sample words. 3) Assemble everything into ONE deliverable: a single index.html grid (preferred — easy to render and tweak) laying out at least 6 cohesive tiles with the keyword list as a caption. 4) Keep the direction tight: every tile should feel like the same world. 5) Reference any generated files from assets/ if produced. 6) write_task_note the board path and tile count. Good looks like: someone could brief a designer from this board alone.",
+      "suggestedRole": "image-generator",
+      "toolPolicy": {
+        "disallowBuiltinToolsets": [
+          "ai-apps",
+          "archives",
+          "audio",
+          "browser-automation",
+          "code-execution",
+          "craftbooks",
+          "data-tables",
+          "entity-intel",
+          "git",
+          "image-intel",
+          "role-delegation",
+          "role-delegation-escalation",
+          "security-intel",
+          "team-management",
+          "videos",
+          "web"
+        ],
+        "outputMedium": "workspace",
+        "additionalOutputMedia": [
+          "task-note"
+        ]
+      },
+      "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": "assemble",
+        "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": "1) Open index.html and confirm it renders a grid of at least 6 tiles (PASS/FAIL). 2) Check it expresses the 3-5 mood keywords from brief.md — is the direction legible and cohesive, not a random scrapbook (PASS/FAIL)? 3) Confirm a palette swatch strip shows the exact hex values and a typography specimen is present. 4) Verify any referenced image files actually load. 5) Write PASS/FAIL per criterion. Incoherent/off-brief → loop back to assemble.\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: \"assemble\" })` 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",
+      "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"
+      },
+      "consumes": [
+        {
+          "file": "index.html"
+        }
+      ],
+      "next": "assemble"
+    },
+    {
+      "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",
+      "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"
+      },
+      "terminal": true
+    }
+  ],
+  "version": "1.0.5",
+  "releasedAt": "2026-10-19T00:00:00Z",
+  "minGezelVersion": "1.26233"
+}

package/data/craftbook-templates/mo/moodboard/versions/1.0.5/test.json

@@ -0,0 +1,89 @@
+{
+  "schemaVersion": 1,
+  "mode": "workflow",
+  "title": "Visual Moodboard workflow processability",
+  "objective": "Prove that a medium local model can parse and execute the Visual Moodboard craftbook, satisfy its declared runtime gates, and reach a terminal step using only local fixtures.",
+  "tags": [
+    "media"
+  ],
+  "prompt": "Use the `moodboard` (Visual Moodboard) craftbook for this self-contained local evaluation. Open `source/craftbook-eval-brief.md` first, then follow the craftbook's actual steps and gates through its terminal step. Complete this request: Compose a visual moodboard that captures a direction — palette, textures, type vibe, imagery, and reference tiles — from a written brief, so a team can align on a look before any production work begins. Lock the brief and the explicit dimensions of the mood (e.g. 'warm/editorial/handmade' vs 'cool/technical/precise') FIRST, then assemble a coherent grid of generated or sourced tiles plus a swatch strip and keyword callouts. Covers moodboards, style boards, visual direction, design inspiration, brand mood, and look-and-feel exploration.\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. Moodboard brief (visual-designer) — lock the mood dimensions, palette, and tile plan → gated on artifact `{{workPath}}/brief.md` (markdown-notes)\n2. Assemble the board (image-generator) — compose the coherent tile grid into one deliverable → 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 Produce `brief.md` in this task's artifact working folder, `index.html`. Use only seeded project files and installed local simulators. Do not call a real external service, fetch live data, or claim an external side effect occurred; an explicit dry-run record is the correct result when a dependency is unavailable.",
+  "setup": {
+    "projectName": "Visual Moodboard Workflow Eval",
+    "about": "A hermetic workflow evaluation for the Visual Moodboard craftbook. No live dependency or external network is authorized.",
+    "missionObjectives": "Run the Visual Moodboard craftbook end to end, use the local evaluation brief and fixtures as truth, produce its declared outputs, and reach a terminal step without fabricating external effects.",
+    "managedWorkspaceWritePolicy": "allow",
+    "files": [
+      {
+        "path": "source/craftbook-eval-brief.md",
+        "content": "# Visual Moodboard — local evaluation brief\n\nThis is a hermetic processability evaluation of the `moodboard` craftbook.\nDo not contact real services, use real credentials, or fetch live data. Treat\nthe project fixtures and installed local simulators as authoritative. If a\ndependency is intentionally unavailable, document an honest dry run instead\nof claiming a real side effect.\n\n## Request\n\nCompose a visual moodboard that captures a direction — palette, textures, type vibe, imagery, and reference tiles — from a written brief, so a team can align on a look before any production work begins. Lock the brief and the explicit dimensions of the mood (e.g. 'warm/editorial/handmade' vs 'cool/technical/precise') FIRST, then assemble a coherent grid of generated or sourced tiles plus a swatch strip and keyword callouts. Covers moodboards, style boards, visual direction, design inspiration, brand mood, and look-and-feel exploration.\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. Moodboard brief (visual-designer) — lock the mood dimensions, palette, and tile plan → gated on artifact `{{workPath}}/brief.md` (markdown-notes)\n2. Assemble the board (image-generator) — compose the coherent tile grid into one deliverable → 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\n\n## Required workflow\n\n1. Moodboard brief\n2. Assemble the board\n3. Evaluate\n4. Finish (terminal)\n\n## Declared outputs\n\n- `brief.md` in this task's artifact working folder\n- `index.html`\n"
+      },
+      {
+        "path": "source/brief.md",
+        "content": "# Visual Moodboard 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: moodboard - Visual Moodboard.\n"
+      },
+      {
+        "path": "source/media-index.csv",
+        "content": "filename,type,duration_or_size,notes\npilot-interview.wav,audio,00:02:15,mentions response time and status silence\nreturns-desk.png,image,1600x900,shows intake form and photo evidence step\nlaunch-clip.mp4,video,00:01:05,shows barcode exception handling\n"
+      }
+    ],
+    "worker": {
+      "name": "Craftbook Runner",
+      "role": "Workflow Operator",
+      "about": "Execute the assigned craftbook exactly. Read local fixtures, satisfy each runtime gate, record honest dry-run evidence for unavailable dependencies, and continue until a terminal step is active or the task is complete."
+    }
+  },
+  "mocks": [],
+  "success": {
+    "summary": "The attributed moodboard task satisfied its own gates, produced its declared outputs, and reached a terminal step without using external services.",
+    "deliverables": [
+      {
+        "path": "{{task.dir}}/brief.md",
+        "kind": "markdown-report",
+        "artifact": true,
+        "minBytes": 120
+      },
+      {
+        "path": "index.html",
+        "kind": "html-page",
+        "minBytes": 800
+      }
+    ],
+    "taskGraph": {
+      "requireCraftbookTask": true,
+      "requireTerminalStep": true
+    }
+  },
+  "rubric": {
+    "artifact": {
+      "path": "{{task.dir}}/brief.md",
+      "kind": "markdown"
+    },
+    "axes": [
+      {
+        "name": "workflow fidelity",
+        "description": "The result reflects the named craftbook sequence and its declared acceptance gates rather than a freehand substitute."
+      },
+      {
+        "name": "usefulness",
+        "description": "The deliverable is coherent, actionable, and suitable for the craftbook purpose stated in the local brief."
+      }
+    ],
+    "contextNote": "Advisory only. Deterministic pass/fail comes from the craftbook runtime gates, deliverable existence, attribution, and terminal progress."
+  },
+  "qualityFocus": [
+    "real moodboard craftbook task attribution",
+    "declared runtime gate satisfaction",
+    "terminal workflow progress",
+    "offline fixture and simulator discipline"
+  ],
+  "extensions": {
+    "legacySimulators": [
+      {
+        "id": "moodboard-media-fixtures",
+        "kind": "data-source",
+        "status": "implemented",
+        "description": "Seeded local media index replacing real audio, video, image generation, and external media metadata services."
+      }
+    ]
+  }
+}

package/data/craftbook-templates/mo/morning-brief/art.json

@@ -1,13 +1,17 @@
 {
   "schemaVersion": 1,
-  "promptVersion": "workshop-mark-1910-v2",
-  "periodCue": "circa-1910-subtle",
-  "family": "analyze-measure",
-  "accents": [
-    "muted indigo",
-    "ochre",
-    "sage"
-  ],
+  "promptVersion": "workshop-mark-cutout-v3",
+  "subject": "a sunrise behind a folded newspaper",
   "sourceSummary": "Be informed without the doomscroll: this morning's items per watched topic, each with its source named, rumor separated from reporting, and yesterday's noise skipped — five minutes that replace an hour of feeds.",
-  "styleReference": "accessibility-audit-1910"
+  "styleReference": "wikipedia-astronomy",
+  "setReference": "data-dictionary-cutout-v3",
+  "sheet": "s34",
+  "cell": 2,
+  "fill": 0.88,
+  "shadow": {
+    "color": "#1c120a",
+    "opacity": 0.38,
+    "blur": 0.035,
+    "offsetY": 0.025
+  }
 }

package/data/craftbook-templates/mo/morning-report/art.json

@@ -1,13 +1,17 @@
 {
   "schemaVersion": 1,
-  "promptVersion": "workshop-mark-1910-v2",
-  "periodCue": "circa-1910-subtle",
-  "family": "communicate-market",
-  "accents": [
-    "muted terracotta",
-    "dusty rose",
-    "sage"
-  ],
+  "promptVersion": "workshop-mark-cutout-v3",
+  "subject": "a small house with a rising sun behind it",
   "sourceSummary": "The house says good morning properly: every zone's state read through the device tools, anything unusual surfaced first with one suggested action apiece, and the boring rest compressed to a line or two — glanceable before the first coffee.",
-  "styleReference": "accessibility-audit-1910"
+  "styleReference": "wikipedia-astronomy",
+  "setReference": "data-dictionary-cutout-v3",
+  "sheet": "s29",
+  "cell": 5,
+  "fill": 0.88,
+  "shadow": {
+    "color": "#1c120a",
+    "opacity": 0.38,
+    "blur": 0.035,
+    "offsetY": 0.025
+  }
 }

package/data/craftbook-templates/mu/music-metadata-tag/art.json

@@ -1,13 +1,17 @@
 {
   "schemaVersion": 1,
-  "promptVersion": "workshop-mark-1910-v2",
-  "periodCue": "circa-1910-subtle",
-  "family": "design-media",
-  "accents": [
-    "muted terracotta",
-    "sage",
-    "muted indigo"
-  ],
+  "promptVersion": "workshop-mark-cutout-v3",
+  "subject": "a vinyl record with a small paper tag tied to it",
   "sourceSummary": "Tag and organize a folder of audio files with consistent, correct metadata — title, artist, album, track number, year, genre — so the library is clean, sortable, and player-friendly.",
-  "styleReference": "accessibility-audit-1910"
+  "styleReference": "wikipedia-astronomy",
+  "setReference": "data-dictionary-cutout-v3",
+  "sheet": "s26",
+  "cell": 3,
+  "fill": 0.88,
+  "shadow": {
+    "color": "#1c120a",
+    "opacity": 0.38,
+    "blur": 0.035,
+    "offsetY": 0.025
+  }
 }

package/data/craftbook-templates/na/narrated-slideshow/art.json

@@ -1,13 +1,17 @@
 {
   "schemaVersion": 1,
-  "promptVersion": "workshop-mark-1910-v2",
-  "periodCue": "circa-1910-subtle",
-  "family": "design-media",
-  "accents": [
-    "muted terracotta",
-    "sage",
-    "muted indigo"
-  ],
-  "sourceSummary": "Build a self-playing narrated slideshow — slides that auto-advance in sync with spoken narration, delivered as a single playable HTML page (slides + per-slide audio + timed auto-advance).",
-  "styleReference": "accessibility-audit-1910"
+  "promptVersion": "workshop-mark-cutout-v3",
+  "subject": "a slide projector casting a beam of light",
+  "sourceSummary": "Turn written content into a real MP4 video and animated GIF with DocBlocks.",
+  "styleReference": "wikipedia-astronomy",
+  "setReference": "data-dictionary-cutout-v3",
+  "sheet": "s26",
+  "cell": 4,
+  "fill": 0.88,
+  "shadow": {
+    "color": "#1c120a",
+    "opacity": 0.38,
+    "blur": 0.035,
+    "offsetY": 0.025
+  }
 }

package/data/craftbook-templates/ne/newsletter-issue/art.json

@@ -1,13 +1,17 @@
 {
   "schemaVersion": 1,
-  "promptVersion": "workshop-mark-1910-v2",
-  "periodCue": "circa-1910-subtle",
-  "family": "build-code",
-  "accents": [
-    "muted indigo",
-    "terracotta",
-    "sage"
-  ],
+  "promptVersion": "workshop-mark-cutout-v3",
+  "subject": "a rolled newspaper tied with string",
   "sourceSummary": "Produce a single polished, email-client-safe newsletter issue — intro, a few curated stories with links, a featured section, and a CTA — that renders correctly across email clients.",
-  "styleReference": "accessibility-audit-1910"
+  "styleReference": "wikipedia-astronomy",
+  "setReference": "data-dictionary-cutout-v3",
+  "sheet": "s22",
+  "cell": 6,
+  "fill": 0.88,
+  "shadow": {
+    "color": "#1c120a",
+    "opacity": 0.38,
+    "blur": 0.035,
+    "offsetY": 0.025
+  }
 }

package/data/craftbook-templates/ni/nightly-fix-sweep/art.json

@@ -1,12 +1,17 @@
 {
   "schemaVersion": 1,
-  "promptVersion": "workshop-mark-1910-v2",
-  "periodCue": "circa-1910-subtle",
-  "family": "build-repair",
-  "accents": [
-    "deep indigo",
-    "brass"
-  ],
-  "sourceSummary": "Overnight triage of open code findings into clustered, reviewable change proposals; the tree itself is never touched.",
-  "styleReference": "bug-fix-tdd"
+  "promptVersion": "workshop-mark-cutout-v3",
+  "subject": "a toolbox with a crescent moon above it",
+  "sourceSummary": "Turn a night's open code findings into reviewable change proposals: triage the leads, cluster what belongs together, and draft one focused proposal per cluster for the user to read and apply in the morning.",
+  "styleReference": "wikipedia-astronomy",
+  "setReference": "data-dictionary-cutout-v3",
+  "sheet": "s16",
+  "cell": 7,
+  "fill": 0.88,
+  "shadow": {
+    "color": "#1c120a",
+    "opacity": 0.38,
+    "blur": 0.035,
+    "offsetY": 0.025
+  }
 }

package/data/craftbook-templates/no/notification-router/art.json

@@ -1,13 +1,17 @@
 {
   "schemaVersion": 1,
-  "promptVersion": "workshop-mark-1910-v2",
-  "periodCue": "circa-1910-subtle",
-  "family": "build-code",
-  "accents": [
-    "muted indigo",
-    "terracotta",
-    "sage"
-  ],
+  "promptVersion": "workshop-mark-cutout-v3",
+  "subject": "a hand bell with three envelopes fanning out from it",
   "sourceSummary": "Build an event-to-channel notification router: a small module that takes incoming events and routes each to the right destination (Slack channel, email, PagerDuty, webhook) based on type, severity, and quiet-hours rules — with dedupe, throttling, and a fallback channel.",
-  "styleReference": "accessibility-audit-1910"
+  "styleReference": "wikipedia-astronomy",
+  "setReference": "data-dictionary-cutout-v3",
+  "sheet": "s10",
+  "cell": 1,
+  "fill": 0.88,
+  "shadow": {
+    "color": "#1c120a",
+    "opacity": 0.38,
+    "blur": 0.035,
+    "offsetY": 0.025
+  }
 }

package/data/craftbook-templates/oc/ocr-extract/art.json

@@ -1,13 +1,17 @@
 {
   "schemaVersion": 1,
-  "promptVersion": "workshop-mark-1910-v2",
-  "periodCue": "circa-1910-subtle",
-  "family": "design-media",
-  "accents": [
-    "muted terracotta",
-    "sage",
-    "muted indigo"
-  ],
+  "promptVersion": "workshop-mark-cutout-v3",
+  "subject": "a flatbed scanner with its lid open and a page on the glass",
   "sourceSummary": "Extract the text from a folder of scanned documents or photographed pages into clean, structured text — preserving reading order, paragraph breaks, and per-file provenance — then verify the extraction against the source images.",
-  "styleReference": "accessibility-audit-1910"
+  "styleReference": "wikipedia-astronomy",
+  "setReference": "data-dictionary-cutout-v3",
+  "sheet": "s26",
+  "cell": 5,
+  "fill": 0.88,
+  "shadow": {
+    "color": "#1c120a",
+    "opacity": 0.38,
+    "blur": 0.035,
+    "offsetY": 0.025
+  }
 }

package/data/craftbook-templates/of/offer-compare/art.json

@@ -1,13 +1,17 @@
 {
   "schemaVersion": 1,
-  "promptVersion": "workshop-mark-1910-v2",
-  "periodCue": "circa-1910-subtle",
-  "family": "people-events-growth",
-  "accents": [
-    "dusty rose",
-    "sage",
-    "muted terracotta"
-  ],
-  "sourceSummary": "Turn competing job offers into one honest decision sheet — every offer normalized into the same fact grid (comp, equity with vesting caveats, benefits, level, location, growth, deadlines), unknowns marked UNKNOWN instead of guessed, computed year-1 and 4-year views under stated assumptions, a weighted read against the…",
-  "styleReference": "accessibility-audit-1910"
+  "promptVersion": "workshop-mark-cutout-v3",
+  "subject": "a balance scale weighing two envelopes",
+  "sourceSummary": "Turn competing job offers into one honest decision sheet — every offer normalized into the same fact grid (comp, equity with vesting caveats, benefits, level, location, growth, deadlines), unknowns marked UNKNOWN instead of guessed, computed year-1 and 4-year views under stated assumptions, a weighted read against the candidate's OWN priorities, and a recommendation that separates arithmetic from judgment.",
+  "styleReference": "wikipedia-astronomy",
+  "setReference": "data-dictionary-cutout-v3",
+  "sheet": "s05",
+  "cell": 5,
+  "fill": 0.88,
+  "shadow": {
+    "color": "#1c120a",
+    "opacity": 0.38,
+    "blur": 0.035,
+    "offsetY": 0.025
+  }
 }

package/data/craftbook-templates/of/office-hours/art.json

@@ -1,12 +1,17 @@
 {
   "schemaVersion": 1,
-  "promptVersion": "workshop-mark-1910-v2",
-  "periodCue": "circa-1910-subtle",
-  "family": "inspect-review",
-  "accents": [
-    "muted terracotta",
-    "sage"
-  ],
+  "promptVersion": "workshop-mark-cutout-v3",
+  "subject": "two armchairs facing each other",
   "sourceSummary": "YC-style office-hours diagnostic.",
-  "styleReference": "accessibility-audit-1910"
+  "styleReference": "wikipedia-astronomy",
+  "setReference": "data-dictionary-cutout-v3",
+  "sheet": "s31",
+  "cell": 8,
+  "fill": 0.88,
+  "shadow": {
+    "color": "#1c120a",
+    "opacity": 0.38,
+    "blur": 0.035,
+    "offsetY": 0.025
+  }
 }