@bendyline/gilde 0.1.92 → 0.1.94

package/data/craftbook-templates/re/research-report/versions/1.0.4/craftbook.json

@@ -0,0 +1,286 @@
+{
+  "id": "research-report",
+  "name": "Cited Research Report",
+  "description": "Produce a rigorously cited research report that answers a specific question end to end: a planner first decomposes the question into sub-questions and locks the scope, then a researcher gathers and logs primary and secondary sources with inline citations, then a copywriter writes a structured markdown report (executive summary, findings, evidence, limitations, references). The ordering matters because a small model that writes before scoping rambles and a model that writes without a source log fabricates citations; locking sub-questions and a source table first turns the report into a fill-in-the-evidence exercise. Use this for literature-backed analysis, deep dives, investigative write-ups, background research, and any 'find out and write it up with sources' task where every claim must trace to a citation.\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. Question scope (planner) — decompose the question into sub-questions + lock scope → gated on artifact `{{workPath}}/question-scope.md` (markdown-notes)\n2. Research & source log (researcher) — gather sources, log each with a citation key + key facts → gated on artifact `{{workPath}}/sources.md` (markdown-notes)\n3. Write the report (copywriter) — write the cited markdown report to the locked structure → 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": "question-scope",
+  "triggers": [
+    "write a research report",
+    "research this question with sources",
+    "cited report",
+    "deep dive on a topic",
+    "investigate and write it up"
+  ],
+  "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}}",
+        "askUser": false
+      },
+      "topic": {
+        "type": "string",
+        "title": "Topic",
+        "description": "The subject, audience, and any details you want the crew to include.",
+        "fromMessage": true
+      }
+    }
+  },
+  "steps": [
+    {
+      "id": "question-scope",
+      "name": "Question scope",
+      "description": "decompose the question into sub-questions + lock scope",
+      "prompt": "1. Restate the research question in one precise sentence; if it is vague, narrow it to something answerable (define the entity, timeframe, geography, and metric). 2. Decompose it into 3-6 sub-questions that, answered together, fully answer the main question. 3. Decide the report structure: executive summary, one section per sub-question, a limitations section, and a references list. 4. Decide source standards: how many independent sources minimum (aim 5+), what counts as authoritative for this topic, and the recency window. 5. Write an acceptance-criteria checklist (e.g. 'every sub-question has a dedicated section', 'every factual claim has an inline citation [n]', 'at least 5 distinct sources in references', 'an explicit limitations/uncertainty section exists', 'executive summary is <=150 words and states the bottom line'). Good looks like a checklist a grader could mechanically apply. 6. Record key decisions (the narrowed question, the sub-questions, the recency window). Call write_task_note with the sub-questions + checklist + decisions, and also write the same content to {{workPath}}/question-scope.md.\n\nThe deliverable `{{workPath}}/question-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}}/question-scope.md",
+        "minBytes": 1,
+        "sniff": "nonempty",
+        "artifact": true
+      },
+      "gate": {
+        "at": "completion",
+        "checks": [
+          {
+            "kind": "minBytes",
+            "file": "{{workPath}}/question-scope.md",
+            "bytes": 120,
+            "artifact": true
+          },
+          {
+            "kind": "sniff",
+            "file": "{{workPath}}/question-scope.md",
+            "sniff": "nonempty",
+            "artifact": true
+          }
+        ],
+        "onReject": "question-scope",
+        "maxAttempts": 3
+      },
+      "next": "research",
+      "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"
+        ]
+      }
+    },
+    {
+      "id": "research",
+      "name": "Research & source log",
+      "description": "gather sources, log each with a citation key + key facts",
+      "prompt": "1. For each sub-question from the scope, find authoritative sources (prefer primary sources, official data, and reputable secondary sources within the recency window). 2. For every source, append an entry to {{workPath}}/sources.md with: a citation key [n], title, author/publisher, date, URL or locator, and 1-3 bullet facts you extracted with the exact figure or quote. 3. Cross-check any surprising or load-bearing fact against a second independent source and note the agreement or conflict. 4. Flag every claim you could NOT verify as UNVERIFIED so the writer does not state it as fact. 5. Aim to exceed the minimum source count and cover every sub-question; do not pad with low-quality sources. Good looks like a source log dense enough that the writer never needs to invent a fact. Keep {{workPath}}/sources.md as the single source of truth; do not write prose yet.\n\nThe deliverable `{{workPath}}/sources.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": "researcher",
+      "advanceWhen": {
+        "file": "{{workPath}}/sources.md",
+        "minBytes": 1,
+        "sniff": "nonempty",
+        "artifact": true
+      },
+      "gate": {
+        "at": "completion",
+        "checks": [
+          {
+            "kind": "minBytes",
+            "file": "{{workPath}}/sources.md",
+            "bytes": 120,
+            "artifact": true
+          },
+          {
+            "kind": "sniff",
+            "file": "{{workPath}}/sources.md",
+            "sniff": "nonempty",
+            "artifact": true
+          }
+        ],
+        "onReject": "research",
+        "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",
+          "workspace-fs-write"
+        ],
+        "outputMedium": "artifact"
+      }
+    },
+    {
+      "id": "write",
+      "name": "Write the report",
+      "description": "write the cited markdown report to the locked structure",
+      "prompt": "1. Write {{workPath}}/report.md following the locked structure exactly: title, an executive summary <=150 words that states the bottom-line answer, one section per sub-question, a limitations section, and a numbered References list. 2. Every factual claim gets an inline citation [n] keyed to the references; do NOT state any UNVERIFIED claim as fact (hedge it or drop it). 3. Build the References list directly from {{workPath}}/sources.md so every [n] resolves and no citation is invented. 4. Lead each section with the answer, then the evidence; keep prose tight and skimmable with subheadings. 5. On a loop-back, fix only the gaps the reviewer named and do not regress sections that already passed. 6. Call write_task_note with the report path and which criteria now pass.\n\nBefore working, open the artifact input `{{workPath}}/sources.md` with `read_artifact`; do not look for it in the workspace.\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",
+      "consumes": [
+        {
+          "file": "{{workPath}}/sources.md",
+          "artifact": true
+        }
+      ],
+      "advanceWhen": {
+        "file": "{{workPath}}/report.md",
+        "minBytes": 1,
+        "sniff": "nonempty",
+        "artifact": true
+      },
+      "gate": {
+        "at": "completion",
+        "checks": [
+          {
+            "kind": "minBytes",
+            "file": "{{workPath}}/report.md",
+            "bytes": 1500,
+            "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": "write",
+        "maxAttempts": 4
+      },
+      "next": "evaluate",
+      "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"
+        ]
+      }
+    },
+    {
+      "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 {{workPath}}/report.md and check EACH acceptance criterion, writing PASS/FAIL per criterion: (1) every sub-question from {{workPath}}/question-scope.md has a dedicated section; (2) every factual claim carries an inline citation [n] and every [n] resolves to a References entry; (3) there are at least the minimum distinct sources and they meet the authority/recency bar; (4) an explicit limitations/uncertainty section exists; (5) the executive summary is <=150 words and states the bottom line; (6) spot-check 3 citations against {{workPath}}/sources.md to confirm the claim matches the logged fact and nothing was fabricated. A report that reads well but invents or mismatches a citation FAILS.\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: \"write\" })` 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": "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": "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.0.4",
+  "releasedAt": "2026-10-08T20:00:00.000Z",
+  "minGezelVersion": "1.26233"
+}

package/data/craftbook-templates/re/research-report/versions/1.0.4/test.json

@@ -0,0 +1,183 @@
+{
+  "schemaVersion": 1,
+  "title": "Cited Research Report workflow eval",
+  "objective": "Run the complete cited-research workflow using a local packet of independently authored operational records; check faithful metrics, citations, final artifact, and terminal task.",
+  "tags": [
+    "corpus"
+  ],
+  "prompt": "Use the Cited Research Report plan to assess the Boreal Desk returns pilot for operations leads. Read source/brief.md and the five linked records in source/. Save the cited report to the artifacts drawer at tasks/eval/report.md.",
+  "setup": {
+    "projectName": "Cited Research Report Eval",
+    "about": "The local source packet contains a client brief plus five independently authored pilot records. All are synthetic fixtures. Deliver the cited report in the artifacts drawer at tasks/eval/report.md.",
+    "missionObjectives": "Use the Cited Research Report craftbook/template, read the seeded local fixtures, and write tasks/eval/report.md without network calls, real credentials, or live services.",
+    "files": [
+      {
+        "path": "source/brief.md",
+        "content": "# Cited Research Report 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: research-report - Cited Research Report.\n\n## Source packet\nRead and cite these available records as independent sources; all dates refer to the same completed pilot window:\n- source/pilot-scope.md — Operations planning\n- source/response-log.md — Support analytics\n- source/refund-audit.md — Finance\n- source/complaint-review.md — Customer experience\n- source/action-register.md — Operations steering group\n"
+      },
+      {
+        "path": "source/pilot-scope.md",
+        "content": "# Pilot scope record\nAuthor: Operations planning\nDate: 2026-09-28\nThe Boreal Desk returns pilot covered 18 SKUs in the home-office accessories range. The pilot compared a baseline observation window with the pilot window. Both windows used the same SKU set. The packet contains no order counts, so avoid claims of statistical significance or extrapolation to the full range.\n"
+      },
+      {
+        "path": "source/response-log.md",
+        "content": "# First-response monitoring log\nAuthor: Support analytics\nDate: 2026-09-29\nFor the 18-SKU returns pilot, median first response time moved from 18 hours in the baseline to 6 hours during the pilot. This measures the first reply, not resolution time. The operational log has no case counts or variance; it supports a descriptive comparison only.\n"
+      },
+      {
+        "path": "source/refund-audit.md",
+        "content": "# Preventable refund leakage audit\nAuthor: Finance\nDate: 2026-09-30\nPreventable refund leakage was 14.2% in the baseline and 8.9% in the Boreal Desk pilot window. This is a 5.3-percentage-point decline. The same preventable-leakage definition was used in both windows. No refund totals were supplied, so do not convert these rates into cash savings. Finance requests a weekly exception export.\n"
+      },
+      {
+        "path": "source/complaint-review.md",
+        "content": "# Customer complaint review\nAuthor: Customer experience\nDate: 2026-09-30\nThe top unresolved complaint after the Boreal Desk returns pilot is status silence after photo submission. A faster first reply does not guarantee later progress updates. Reviewers recommend automated status emails after evidence arrives. The review gives an ordinal ranking but no complaint counts.\n"
+      },
+      {
+        "path": "source/action-register.md",
+        "content": "# Approved operations action register\nAuthor: Operations steering group\nDate: 2026-10-01\nThe next actions approved after the pilot are automated status emails, barcode-exception training, and a weekly Finance exception export. Support operations owns the emails, training operations owns barcode exceptions, and Finance owns the exception review. Timing and targets still need agreement; do not present invented deadlines as commitments.\n"
+      }
+    ],
+    "craftbookParams": {
+      "workPath": "tasks/eval",
+      "topic": "Boreal Desk Returns Pilot for operations leaders; use source/brief.md."
+    }
+  },
+  "mocks": [],
+  "success": {
+    "summary": "tasks/eval/report.md is a source-grounded markdown artifact with required facts and actions.",
+    "deliverables": [
+      {
+        "path": "tasks/eval/report.md",
+        "kind": "markdown-report",
+        "minBytes": 1000,
+        "checks": [
+          {
+            "kind": "contains",
+            "file": "tasks/eval/report.md",
+            "pattern": "(?:^|\\n)#{1,3}\\s+\\S",
+            "flags": "i",
+            "artifact": true
+          },
+          {
+            "kind": "contains",
+            "file": "tasks/eval/report.md",
+            "pattern": "source/brief\\.md|Brief",
+            "flags": "i",
+            "label": "cite or name the seeded source",
+            "artifact": true
+          },
+          {
+            "kind": "contains",
+            "file": "tasks/eval/report.md",
+            "pattern": "18\\b[\\s\\S]{0,30}\\bSKUs",
+            "flags": "i",
+            "label": "include the 18-SKU pilot scope",
+            "artifact": true
+          },
+          {
+            "kind": "contains",
+            "file": "tasks/eval/report.md",
+            "pattern": "18\\s*hours|6\\s*hours",
+            "flags": "i",
+            "artifact": true
+          },
+          {
+            "kind": "contains",
+            "file": "tasks/eval/report.md",
+            "pattern": "14\\.2%|8\\.9%",
+            "flags": "i",
+            "artifact": true
+          },
+          {
+            "kind": "contains",
+            "file": "tasks/eval/report.md",
+            "pattern": "status silence|photo submission",
+            "flags": "i",
+            "artifact": true
+          },
+          {
+            "kind": "contains",
+            "file": "tasks/eval/report.md",
+            "pattern": "automated status emails|barcode|Finance",
+            "flags": "i",
+            "artifact": true
+          },
+          {
+            "kind": "contains",
+            "file": "tasks/eval/report.md",
+            "pattern": "source/pilot-scope\\.md",
+            "flags": "i",
+            "label": "cite the supplied pilot-scope.md",
+            "artifact": true
+          },
+          {
+            "kind": "contains",
+            "file": "tasks/eval/report.md",
+            "pattern": "source/response-log\\.md",
+            "flags": "i",
+            "label": "cite the supplied response-log.md",
+            "artifact": true
+          },
+          {
+            "kind": "contains",
+            "file": "tasks/eval/report.md",
+            "pattern": "source/refund-audit\\.md",
+            "flags": "i",
+            "label": "cite the supplied refund-audit.md",
+            "artifact": true
+          },
+          {
+            "kind": "contains",
+            "file": "tasks/eval/report.md",
+            "pattern": "source/complaint-review\\.md",
+            "flags": "i",
+            "label": "cite the supplied complaint-review.md",
+            "artifact": true
+          },
+          {
+            "kind": "contains",
+            "file": "tasks/eval/report.md",
+            "pattern": "source/action-register\\.md",
+            "flags": "i",
+            "label": "cite the supplied action-register.md",
+            "artifact": true
+          }
+        ],
+        "artifact": true
+      }
+    ],
+    "taskGraph": {
+      "requireCraftbookTask": true,
+      "requireTerminalStep": true
+    }
+  },
+  "rubric": {
+    "artifact": {
+      "path": "tasks/eval/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"
+  ],
+  "mode": "workflow"
+}

package/data/craftbook-templates/re/research-to-document/manifest.json

@@ -16,7 +16,8 @@
     "report",
     "markdown",
     "docblocks",
-    "recommended"
+    "recommended",
+    "starter"
   ],
   "maintainer": {
     "name": "Gezel"