npm - @bendyline/gilde - Versions diffs - 0.1.55 → 0.1.56 - Mend

@bendyline/gilde 0.1.55 → 0.1.56

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.

Files changed (185) hide show

package/data/craftbook-templates/de/design-system-consultation/versions/2.0.8/test.json ADDED Viewed

@@ -0,0 +1,201 @@
+{
+  "schemaVersion": 1,
+  "title": "Design System Consultation — Harbor Ops dashboard",
+  "objective": "Exercise the Design System Consultation craftbook on a seeded operations dashboard and require a grounded, accessible DESIGN.md plus a complete HTML state preview.",
+  "tags": [
+    "workflow",
+    "design-system",
+    "html-page",
+    "accessibility"
+  ],
+  "prompt": "Use the Design System Consultation craftbook for the Harbor Ops dashboard. This is an unattended evaluation: the product and taste decisions in `source/design-brief.md` are authoritative, so proceed without asking questions and label any remaining assumptions. Audit the supplied interface, preserve its useful density, then produce the workflow artifacts, `DESIGN.md`, and `previews/design-system.html`. The preview must be self-contained and show navigation, typography, controls, data cards, table content, empty/loading/error/success states, keyboard focus, disabled controls, and responsive behavior. Use no external assets or live research.",
+  "setup": {
+    "projectName": "Harbor Ops design system",
+    "about": "Harbor Ops is a desktop-first operations dashboard for coordinators monitoring time-sensitive berth assignments. The fixture is complete and must be handled without live research.",
+    "missionObjectives": "Run the Design System Consultation craftbook as a real task. Ground every design decision in the seeded brief and current interface, then deliver DESIGN.md and the self-contained preview.",
+    "files": [
+      {
+        "path": "README.md",
+        "content": "# Harbor Ops\n\nHarbor Ops helps port coordinators scan berth conflicts, assign an owner, and clear exceptions during a shift. It is dense desktop software used in bright control rooms; the core job is spotting the one item that needs action now.\n"
+      },
+      {
+        "path": "source/design-brief.md",
+        "content": "# Locked design brief\n\nAudience: experienced port coordinators working 8-hour shifts on desktop, with occasional tablet use.\n\nMemorable intent: **calm command under pressure**. The interface should feel serious and precise, never playful or luxurious.\n\nPreserve: dense scan-friendly tables, the navy header, status labels, and explicit timestamps.\n\nChange: inconsistent spacing, low-contrast muted text, color-only severity, invisible keyboard focus, and one-off button styles.\n\nBrand constraints: deep navy `#10233f`; signal amber `#d97706`; off-white canvas. Do not use pure black.\n\nAccessibility: WCAG AA text contrast, visible `:focus-visible`, shape/text in addition to status color, 44px primary touch targets on tablet, reduced-motion support.\n\nProduct states that must be designed: normal, loading, empty, permission error, delayed-data warning, success acknowledgement, selected row, disabled action.\n\nTaste: compact Swiss/industrial typography, restrained motion, square-to-soft corners (4-8px), clear dividers. Avoid gradients, glass effects, giant hero type, and decorative illustrations.\n"
+      },
+      {
+        "path": "src/dashboard.html",
+        "content": "<!doctype html><html lang=\"en\"><head><meta charset=\"utf-8\"><title>Harbor Ops</title><link rel=\"stylesheet\" href=\"styles.css\"></head><body><header>Harbor Ops <small>Shift A · 07:42 UTC</small></header><main><aside><button>Overview</button><button>Berths</button><button>Exceptions</button></aside><section><h1>Berth exceptions</h1><button class=\"primary\">Assign owner</button><table><tr><th>Vessel</th><th>Berth</th><th>Status</th><th>Updated</th></tr><tr><td>MV Juniper</td><td>B-14</td><td><span class=\"status\">Delayed</span></td><td>07:38 UTC</td></tr></table></section></main></body></html>\n"
+      },
+      {
+        "path": "src/styles.css",
+        "content": ":root{--navy:#10233f;--amber:#d97706}body{margin:0;font:14px Arial;background:#f7f5ef;color:#27364a}header{background:var(--navy);color:white;padding:13px 18px}header small{color:#7e8aa0}main{display:flex}aside{width:190px;padding:12px}section{flex:1;padding:19px}button{border:0;padding:7px;margin:3px}.primary{background:var(--amber);color:white}.status{color:#d97706}table{width:100%;border-collapse:collapse}td,th{text-align:left;border-bottom:1px solid #ddd;padding:9px}button:focus{outline:none}\n"
+      }
+    ]
+  },
+  "mocks": [],
+  "success": {
+    "summary": "The real craftbook produces a grounded design audit and brief, an accessible token specification, a valid multi-state preview, and terminal review evidence.",
+    "deliverables": [
+      {
+        "path": "design/current-state-audit.md",
+        "kind": "markdown-report",
+        "minBytes": 750,
+        "checks": [
+          {
+            "kind": "contains",
+            "file": "design/current-state-audit.md",
+            "pattern": "^#{1,3}\\s+Product and users\\b[\\s\\S]*^#{1,3}\\s+Existing language\\b[\\s\\S]*^#{1,3}\\s+Accessibility\\b",
+            "flags": "im",
+            "label": "grounded current-state audit"
+          },
+          {
+            "kind": "citationsResolve",
+            "file": "design/current-state-audit.md",
+            "minCitations": 2
+          }
+        ]
+      },
+      {
+        "path": "DESIGN.md",
+        "kind": "markdown-doc",
+        "minBytes": 1800,
+        "checks": [
+          {
+            "kind": "contains",
+            "file": "DESIGN.md",
+            "pattern": "^#{1,3}\\s+Design intent\\b[\\s\\S]*^#{1,3}\\s+Tokens\\b[\\s\\S]*^#{1,3}\\s+Typography\\b[\\s\\S]*^#{1,3}\\s+Color\\b[\\s\\S]*^#{1,3}\\s+Components and states\\b[\\s\\S]*^#{1,3}\\s+Accessibility\\b[\\s\\S]*^#{1,3}\\s+Adoption\\b",
+            "flags": "im",
+            "label": "complete design-system specification"
+          },
+          {
+            "kind": "valueGrounding",
+            "file": "DESIGN.md",
+            "facts": [
+              {
+                "id": "intent",
+                "label": "memorable intent",
+                "required": [
+                  "calm command under pressure"
+                ]
+              },
+              {
+                "id": "brand-navy",
+                "label": "locked navy",
+                "required": [
+                  "#10233f"
+                ]
+              },
+              {
+                "id": "brand-amber",
+                "label": "locked signal amber",
+                "required": [
+                  "#d97706"
+                ]
+              },
+              {
+                "id": "keyboard-focus",
+                "label": "visible keyboard focus",
+                "required": [
+                  "focus-visible"
+                ]
+              },
+              {
+                "id": "reduced-motion",
+                "label": "reduced-motion behavior",
+                "required": [
+                  "reduced-motion|prefers-reduced-motion"
+                ]
+              },
+              {
+                "id": "touch-target",
+                "label": "tablet touch target",
+                "required": [
+                  "44\\s*(?:px|pixel)"
+                ]
+              }
+            ]
+          }
+        ]
+      },
+      {
+        "path": "previews/design-system.html",
+        "kind": "html-page",
+        "minBytes": 3000,
+        "checks": [
+          {
+            "kind": "htmlLint",
+            "file": "previews/design-system.html"
+          },
+          {
+            "kind": "cssMinBytes",
+            "bytes": 900,
+            "file": "previews/design-system.html"
+          },
+          {
+            "kind": "contains",
+            "file": "previews/design-system.html",
+            "pattern": "loading[\\s\\S]*empty[\\s\\S]*(error|permission)[\\s\\S]*(success|acknowledge)[\\s\\S]*disabled",
+            "flags": "i",
+            "label": "representative application states"
+          },
+          {
+            "kind": "contains",
+            "file": "previews/design-system.html",
+            "pattern": "focus-visible|prefers-reduced-motion",
+            "flags": "i",
+            "label": "keyboard focus and reduced motion"
+          }
+        ]
+      }
+    ],
+    "taskNotes": {
+      "minBytes": 180,
+      "checks": [
+        {
+          "kind": "contains",
+          "file": "task-notes.md",
+          "pattern": "\\bDONE\\b[\\s\\S]*DESIGN\\.md[\\s\\S]*previews/design-system\\.html",
+          "flags": "i",
+          "label": "terminal note records both design deliverables"
+        }
+      ],
+      "requireCraftbookTask": true
+    },
+    "taskGraph": {
+      "requireCraftbookTask": true,
+      "requireTerminalStep": true
+    },
+    "unchangedFixtures": [
+      "README.md",
+      "source/design-brief.md",
+      "src/dashboard.html",
+      "src/styles.css"
+    ]
+  },
+  "rubric": {
+    "artifact": {
+      "path": "DESIGN.md",
+      "kind": "markdown"
+    },
+    "axes": [
+      {
+        "name": "Product fit",
+        "description": "The system reinforces calm command under pressure and the actual coordinator workflows rather than generic visual taste."
+      },
+      {
+        "name": "System coherence",
+        "description": "Tokens, typography, color, density, components, states, and motion form a reusable system with explicit rationale."
+      },
+      {
+        "name": "Accessibility and preview",
+        "description": "The specification and preview cover contrast, focus, non-color status, touch size, reduced motion, responsiveness, and real application states."
+      }
+    ],
+    "contextNote": "Judge against the seeded brief and current dashboard; decorative novelty that violates the locked taste is a defect."
+  },
+  "qualityFocus": [
+    "Preserve useful density while correcting current accessibility failures",
+    "Use exact reusable tokens with reasons",
+    "Preview representative responsive and interaction states without external assets"
+  ]
+}

package/data/craftbook-templates/do/doc-intake-pipeline/versions/1.0.4/craftbook.json ADDED Viewed

@@ -0,0 +1,285 @@
+{
+  "id": "doc-intake-pipeline",
+  "name": "Classify and Route Incoming Documents",
+  "description": "Build a document-intake pipeline that classifies each incoming file (invoice, contract, resume, receipt, ID, support ticket, other) into a fixed type set, extracts a few key fields per type, and routes it to the right destination folder with a normalized filename. Locks the document-type taxonomy, per-type extraction fields, and the routing/naming rules FIRST, then builds the classify-extract-route loop, then verifies every input file was handled, classifications are in-set with an 'other' fallback, and routing is deterministic. Taxonomy-and-routing-before-build prevents files from silently vanishing or piling into a misc bucket.\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. Scope the pipeline (planner) — doc-type taxonomy, per-type fields, routing rules → gated on artifact `{{workPath}}/scope.md` (markdown-notes)\n2. Build the pipeline (developer) — classify, extract key fields, route + rename, log → gated on `intake.py` (code-module)\n3. Verify the pipeline (reviewer) — coverage, in-set types, deterministic routing → gated on artifact `{{workPath}}/verify.md` (markdown-notes)\n\nThe gates never advance with an unmet criterion, and loop back to the\nowning phase to fix named gaps.\n",
+  "entryStepId": "scope",
+  "triggers": [
+    "sort incoming documents",
+    "classify and file documents",
+    "auto-route a folder of files",
+    "document intake pipeline",
+    "organize a dump of files"
+  ],
+  "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": "scope",
+      "name": "Scope the pipeline",
+      "description": "doc-type taxonomy, per-type fields, routing rules",
+      "prompt": "Define the intake contract before building. Step 1: identify the inbox/source folder and the file types present (PDF, image, docx, email). Step 2: define the closed document-type taxonomy (e.g. invoice, contract, receipt, resume, id-document, support-ticket, other) — every file lands in exactly one, with 'other' as the explicit fallback. Step 3: for each type, list the few key fields to extract (e.g. invoice → vendor, date, total, invoice_no) and the classification signals (keywords, layout cues). Step 4: define routing and naming: destination folder per type and a normalized filename template (e.g. {type}/{date}_{vendor}_{id}.pdf), plus the dedup rule for name collisions. Step 5: write an acceptance-criteria checklist ('every input file classified into exactly one in-set type', 'an other bucket exists and is used not abused', 'per-type key fields extracted', 'each file routed and renamed deterministically', 'no file lost or overwritten', 'an intake manifest logs every file with source→destination'). Call write_task_note with taxonomy + fields + routing + checklist and write {{workPath}}/scope.md. No build yet.\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": "planner",
+      "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}}/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": "build"
+    },
+    {
+      "id": "build",
+      "name": "Build the pipeline",
+      "description": "classify, extract key fields, route + rename, log",
+      "prompt": "Implement the intake pipeline to the locked contract. Step 1: enumerate every file in the source folder. Step 2: classify each into exactly one taxonomy type using the agreed signals; when confidence is low, route to 'other' rather than guessing a specific type. Step 3: extract the per-type key fields and capture them in the manifest. Step 4: route the file to its destination folder and rename it per the template, applying the collision/dedup rule so nothing is overwritten. Step 5: append an intake-manifest row per file (source path, type, extracted fields, destination path, status) and write the manifest. Make it a runnable module and write it; confirm the manifest parses. Call write_task_note with the module path, the manifest path, and per-type counts.",
+      "suggestedRole": "developer",
+      "toolPolicy": {
+        "disallowBuiltinToolsets": [
+          "ai-apps",
+          "archives",
+          "artifacts",
+          "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"
+        ]
+      },
+      "advanceWhen": {
+        "file": "intake.py",
+        "minBytes": 1,
+        "sniff": "nonempty"
+      },
+      "gate": {
+        "at": "completion",
+        "checks": [
+          {
+            "kind": "minBytes",
+            "file": "intake.py",
+            "bytes": 200
+          },
+          {
+            "kind": "sniff",
+            "file": "intake.py",
+            "sniff": "nonempty"
+          },
+          {
+            "kind": "esmImports",
+            "file": "intake.py"
+          },
+          {
+            "kind": "sourceParses",
+            "file": "intake.py"
+          }
+        ],
+        "onReject": "build",
+        "maxAttempts": 3
+      },
+      "next": "verify"
+    },
+    {
+      "id": "verify",
+      "name": "Verify the pipeline",
+      "description": "coverage, in-set types, deterministic routing",
+      "prompt": "Verify the pipeline against scope. Step 1: confirm it runs and produces an intake manifest. Step 2: check coverage — the manifest has one row per source file and the count of routed files equals the count of input files (nothing lost). Step 3: confirm every classification is an in-set type and that 'other' is used for genuinely ambiguous files but not as a dumping ground for everything. Step 4: confirm routing is deterministic and collision-safe — re-running classifies the same file identically and no destination file was overwritten. Step 5: spot-check 5 files: correct type, extracted fields match the document, filename matches the template. Write PASS/FAIL per criterion to {{workPath}}/verify.md and task notes; on failure, name the files and loop back to build.\n\nThe deliverable `{{workPath}}/verify.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": "reviewer",
+      "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}}/verify.md",
+        "minBytes": 1,
+        "sniff": "nonempty",
+        "artifact": true
+      },
+      "gate": {
+        "at": "completion",
+        "checks": [
+          {
+            "kind": "minBytes",
+            "file": "intake.py",
+            "bytes": 200
+          },
+          {
+            "kind": "sniff",
+            "file": "intake.py",
+            "sniff": "nonempty"
+          },
+          {
+            "kind": "esmImports",
+            "file": "intake.py"
+          },
+          {
+            "kind": "sourceParses",
+            "file": "intake.py"
+          }
+        ],
+        "onReject": "verify",
+        "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": "Run intake.py (or trace it) and verify every criterion from {{workPath}}/scope.md against the intake manifest. Confirm: one manifest row per source file with routed count equal to input count (no files lost or overwritten), every classification is in-set with 'other' used appropriately, per-type key fields are extracted, filenames follow the template, and routing is deterministic on re-run. Spot-check 5 files. Write PASS/FAIL per criterion; on any failure, name the files and loop back to build.\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",
+      "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": "intake.py"
+        }
+      ],
+      "next": "build"
+    },
+    {
+      "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.4",
+  "releasedAt": "2026-09-05T03:30:00Z",
+  "minGezelVersion": "1.26233"
+}

package/data/craftbook-templates/do/doc-intake-pipeline/versions/1.0.4/test.json ADDED Viewed

@@ -0,0 +1,104 @@
+{
+  "schemaVersion": 1,
+  "title": "Classify and Route Incoming Documents smoke eval",
+  "objective": "Self-contained smoke eval for the Classify and Route Incoming Documents craftbook using the data generic harness.",
+  "tags": [
+    "data"
+  ],
+  "prompt": "I dropped our numbers in source/records.csv. Can you look at the data, analyze it, and put togehter some results in analysis.md?",
+  "setup": {
+    "projectName": "Classify and Route Incoming Documents Eval",
+    "about": "Self-contained eval project for doc-intake-pipeline. Seeded inputs are under workspace/source or workspace/fixtures; final deliverable is workspace/analysis.md.",
+    "missionObjectives": "Use the Classify and Route Incoming Documents craftbook/template, read the seeded local fixtures, and write analysis.md without network calls, real credentials, or live services.",
+    "files": [
+      {
+        "path": "source/brief.md",
+        "content": "# Classify and Route Incoming Documents 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: doc-intake-pipeline - Classify and Route Incoming Documents.\n"
+      },
+      {
+        "path": "source/records.csv",
+        "content": "customer,region,orders,revenue_usd,churn_risk\nAster,North,12,1440,low\nBoreal,South,8,720,medium\nCedar,West,15,2100,high\nDune,North,5,500,low\n"
+      }
+    ],
+    "worker": {
+      "name": "Jules",
+      "role": "Data Analyst"
+    }
+  },
+  "mocks": [],
+  "success": {
+    "summary": "analysis.md is a seeded-data analysis with deterministic computed facts.",
+    "deliverables": [
+      {
+        "path": "analysis.md",
+        "kind": "markdown-report",
+        "minBytes": 900,
+        "checks": [
+          {
+            "kind": "contains",
+            "file": "analysis.md",
+            "pattern": "(?:^|\\n)#{1,3}\\s+\\S",
+            "flags": "i"
+          },
+          {
+            "kind": "contains",
+            "file": "analysis.md",
+            "pattern": "40\\b",
+            "flags": "i",
+            "label": "include total orders of 40"
+          },
+          {
+            "kind": "contains",
+            "file": "analysis.md",
+            "pattern": "\\$?4,?760\\b",
+            "flags": "i",
+            "label": "include total revenue of 4760"
+          },
+          {
+            "kind": "contains",
+            "file": "analysis.md",
+            "pattern": "Cedar",
+            "flags": "i",
+            "label": "identify Cedar as top revenue and high risk"
+          },
+          {
+            "kind": "contains",
+            "file": "analysis.md",
+            "pattern": "high",
+            "flags": "i",
+            "label": "include churn-risk finding"
+          }
+        ]
+      }
+    ]
+  },
+  "rubric": {
+    "artifact": {
+      "path": "analysis.md",
+      "kind": "markdown"
+    },
+    "axes": [
+      {
+        "name": "accuracy",
+        "description": "Computed figures are correct against the seeded records."
+      },
+      {
+        "name": "grounding",
+        "description": "Every claim traces to the seeded data — nothing invented."
+      },
+      {
+        "name": "structure",
+        "description": "Tables and sections make the analysis checkable at a glance."
+      },
+      {
+        "name": "actionability",
+        "description": "Recommendations follow from the findings and are concretely doable."
+      }
+    ]
+  },
+  "qualityFocus": [
+    "seeded data reading",
+    "computed facts",
+    "recommendation grounding"
+  ]
+}