@bendyline/gilde 0.1.3 → 0.1.4

package/data/craftbook-templates/in/inbox-triage/manifest.json

@@ -15,6 +15,7 @@
   "maintainer": {
     "name": "Gezel"
   },
+  "logo": "logo.webp",
   "license": "MIT",
   "yankedVersions": [],
   "workflow": "build-loop"

package/data/craftbook-templates/in/incident-comms-templates/art.json

@@ -0,0 +1,12 @@
+{
+  "schemaVersion": 1,
+  "promptVersion": "workshop-mark-1910-v2",
+  "periodCue": "circa-1910-subtle",
+  "family": "inspect-review",
+  "accents": [
+    "muted terracotta",
+    "sage"
+  ],
+  "sourceSummary": "Author a reusable set of incident communication templates: status-page posts and stakeholder update messages for each phase of an incident (Investigating, Identified, Monitoring, Resolved) across severities, with fill-in variables and a cadence guide.",
+  "styleReference": "accessibility-audit-1910"
+}

package/data/craftbook-templates/in/incident-comms-templates/manifest.json

@@ -15,6 +15,7 @@
   "maintainer": {
     "name": "Gezel"
   },
+  "logo": "logo.webp",
   "license": "MIT",
   "yankedVersions": [],
   "workflow": "build-loop"

package/data/craftbook-templates/in/incident-postmortem/art.json

@@ -0,0 +1,12 @@
+{
+  "schemaVersion": 1,
+  "promptVersion": "workshop-mark-1910-v2",
+  "periodCue": "circa-1910-subtle",
+  "family": "inspect-review",
+  "accents": [
+    "muted terracotta",
+    "sage"
+  ],
+  "sourceSummary": "Write a blameless incident postmortem after a production outage or degradation — a structured, factual document covering the impact, a precise timeline (detection → diagnosis → mitigation → resolution), the root cause and contributing factors via a five-whys analysis, what went well and what went poorly, and concrete,…",
+  "styleReference": "accessibility-audit-1910"
+}

package/data/craftbook-templates/in/incident-postmortem/manifest.json

@@ -16,6 +16,7 @@
   "maintainer": {
     "name": "Gezel"
   },
+  "logo": "logo.webp",
   "license": "MIT",
   "yankedVersions": [],
   "workflow": "build-loop"

package/data/craftbook-templates/in/insurance-inventory/art.json

@@ -0,0 +1,13 @@
+{
+  "schemaVersion": 1,
+  "promptVersion": "workshop-mark-1910-v2",
+  "periodCue": "circa-1910-subtle",
+  "family": "write-publish",
+  "accents": [
+    "muted terracotta",
+    "muted indigo",
+    "sage"
+  ],
+  "sourceSummary": "Compile the inventory nobody has until the day they desperately need it: every cataloged item with its value, photo reference, and acquisition info in one document, the gaps (no photo, no value) named instead of papered over, and the total stated with its basis.",
+  "styleReference": "accessibility-audit-1910"
+}

package/data/craftbook-templates/in/insurance-inventory/manifest.json

@@ -15,6 +15,7 @@
   "maintainer": {
     "name": "Gezel"
   },
+  "logo": "logo.webp",
   "license": "MIT",
   "yankedVersions": [],
   "workflow": "build-loop"

package/data/craftbook-templates/in/interactive-quiz/art.json

@@ -0,0 +1,13 @@
+{
+  "schemaVersion": 1,
+  "promptVersion": "workshop-mark-1910-v2",
+  "periodCue": "circa-1910-subtle",
+  "family": "build-code",
+  "accents": [
+    "muted indigo",
+    "terracotta",
+    "sage"
+  ],
+  "sourceSummary": "Build a single-file interactive quiz or assessment — multiple-choice, true/false, or a scored personality quiz — that asks questions one at a time, tracks the score, gives feedback, and shows a results screen.",
+  "styleReference": "accessibility-audit-1910"
+}

package/data/craftbook-templates/in/interactive-quiz/manifest.json

@@ -15,6 +15,7 @@
   "maintainer": {
     "name": "Gezel"
   },
+  "logo": "logo.webp",
   "license": "MIT",
   "yankedVersions": [],
   "workflow": "build-loop"

package/data/craftbook-templates/in/investigate/art.json

@@ -0,0 +1,12 @@
+{
+  "schemaVersion": 1,
+  "promptVersion": "workshop-mark-1910-v2",
+  "periodCue": "circa-1910-subtle",
+  "family": "inspect-review",
+  "accents": [
+    "muted terracotta",
+    "sage"
+  ],
+  "sourceSummary": "Systematic root-cause debugging procedure.",
+  "styleReference": "accessibility-audit-1910"
+}

package/data/craftbook-templates/in/investigate/manifest.json

@@ -12,6 +12,7 @@
   "maintainer": {
     "name": "Gezel"
   },
+  "logo": "logo.webp",
   "license": "MIT",
   "yankedVersions": [],
   "workflow": "investigation"

package/data/craftbook-templates/in/investigate-root-cause/art.json

@@ -0,0 +1,12 @@
+{
+  "schemaVersion": 1,
+  "promptVersion": "workshop-mark-1910-v2",
+  "periodCue": "circa-1910-subtle",
+  "family": "inspect-review",
+  "accents": [
+    "muted terracotta",
+    "sage"
+  ],
+  "sourceSummary": "Debug a defect or production incident down to its true root cause and document the diagnosis with evidence, instead of patching the first symptom.",
+  "styleReference": "accessibility-audit-1910"
+}

package/data/craftbook-templates/in/investigate-root-cause/manifest.json

@@ -15,6 +15,7 @@
   "maintainer": {
     "name": "Gezel"
   },
+  "logo": "logo.webp",
   "license": "MIT",
   "yankedVersions": [],
   "workflow": "build-loop"

package/data/craftbook-templates/in/invitation-design/art.json

@@ -0,0 +1,13 @@
+{
+  "schemaVersion": 1,
+  "promptVersion": "workshop-mark-1910-v2",
+  "periodCue": "circa-1910-subtle",
+  "family": "design-media",
+  "accents": [
+    "muted terracotta",
+    "sage",
+    "muted indigo"
+  ],
+  "sourceSummary": "Produce the invitation the day deserves and get the facts beyond doubt: the date, time, venue, and RSVP instructions checked letter-for-letter against the event record — because a beautiful card with the wrong date is the classic disaster.",
+  "styleReference": "accessibility-audit-1910"
+}

package/data/craftbook-templates/in/invitation-design/manifest.json

@@ -15,6 +15,7 @@
   "maintainer": {
     "name": "Gezel"
   },
+  "logo": "logo.webp",
   "license": "MIT",
   "yankedVersions": [],
   "workflow": "build-loop"

package/data/craftbook-templates/in/invoice-generator/art.json

@@ -0,0 +1,13 @@
+{
+  "schemaVersion": 1,
+  "promptVersion": "workshop-mark-1910-v2",
+  "periodCue": "circa-1910-subtle",
+  "family": "operate-maintain",
+  "accents": [
+    "sage",
+    "ochre",
+    "muted terracotta"
+  ],
+  "sourceSummary": "Generate a clean, professional, print-ready invoice from billing details — sender/recipient, line items with quantity and rate, subtotal, tax, total, invoice number, dates, and payment instructions.",
+  "styleReference": "accessibility-audit-1910"
+}

package/data/craftbook-templates/in/invoice-generator/manifest.json

@@ -15,6 +15,7 @@
   "maintainer": {
     "name": "Gezel"
   },
+  "logo": "logo.webp",
   "license": "MIT",
   "yankedVersions": [],
   "workflow": "build-loop"

package/data/craftbook-templates/in/invoice-run/art.json

@@ -0,0 +1,13 @@
+{
+  "schemaVersion": 1,
+  "promptVersion": "workshop-mark-1910-v2",
+  "periodCue": "circa-1910-subtle",
+  "family": "write-publish",
+  "accents": [
+    "muted terracotta",
+    "muted indigo",
+    "sage"
+  ],
+  "sourceSummary": "Run the month's invoicing in one calm pass from the office's own books: an invoice per client built from the tracked work in the ledger, numbering that continues the sequence without a skip or a repeat, due dates per each client's terms, everything recorded as sent — plus a one-page summary of what went out.",
+  "styleReference": "accessibility-audit-1910"
+}

package/data/craftbook-templates/in/invoice-run/manifest.json

@@ -15,7 +15,9 @@
   "maintainer": {
     "name": "Gezel"
   },
+  "logo": "logo.webp",
   "license": "MIT",
   "yankedVersions": [],
-  "workflow": "build-loop"
+  "workflow": "build-loop",
+  "version": "1.0.1"
 }

package/data/craftbook-templates/in/invoice-run/versions/1.0.1/craftbook.json

@@ -0,0 +1,168 @@
+{
+  "id": "invoice-run",
+  "name": "Monthly Invoice Run",
+  "description": "Run the month's invoicing in one calm pass from the office's own books: an invoice per client built from the tracked work in the ledger, numbering that continues the sequence without a skip or a repeat, due dates per each client's terms — plus a one-page summary of what went out. Unlike a one-off invoice generator, this is the standing monthly ritual over the client roster and ledger, ending in print-ready invoices. Use for the monthly invoice run, end-of-month invoicing, 'bill the clients for this month', and closing the billing month.\n\nThis book is a DECLARATIVE FANOUT host. The scope step writes a machine list of the billable clients (notes/billables.json); the draft step is a `spawnFanout` step, so the runtime spawns one child task per client — each child drafts that client's invoice as its own print-ready HTML file. The collect step's `fileCount` gate is the barrier that waits for the crew's files before the run summary is accepted; the evaluate step loops back on a miss.\n\nSteps:\n\n1. Scope the run (kantoormeester) — billable clients + numbering + terms → writes notes/scope.md and the machine list notes/billables.json\n2. Draft the invoices (spawnFanout) — the runtime fans out one child per client; each child writes invoices/{number}.html\n3. Collect and summarize (copywriter) — gated on `fileCount html >= 2` in invoices/; writes report.md\n4. Evaluate (reviewer) — every criterion passes → finish; any miss → loop back to draft\n5. Finish\n",
+  "entryStepId": "scope",
+  "triggers": [
+    "run the monthly invoices",
+    "end of month invoicing",
+    "bill the clients for this month",
+    "invoice run",
+    "send this month's invoices"
+  ],
+  "steps": [
+    {
+      "id": "scope",
+      "name": "Scope the run",
+      "description": "billable clients from the books; write the machine billables list",
+      "prompt": "Read the books before any invoice exists. Step 1: read clients.json and ledger.json from the workspace. Step 2: work out which clients have tracked, uninvoiced work this month, and the next invoice number — it continues the last issued number with no skip and no repeat. Step 3: write notes/scope.md — an acceptance-criteria checklist: one invoice per billable client (none invented), every amount traces to a ledger entry, numbers continue the sequence, due dates match each client's terms, and any client with no work is skipped on purpose. Step 4: write notes/billables.json — a top-level JSON ARRAY (nothing wrapping it) with ONE object per billable client, each object EXACTLY these keys: {\"client\": the client's name, \"number\": the invoice number for this client as a string, \"rate\": the total amount owed this month as a string, \"work\": a short description of the tracked work, \"due\": the due date computed from the client's terms}. Assign each client the next number in the running sequence — no skip, no repeat. The crew reads this file to draft the invoices, so the numbers and amounts must be exact. Call write_task_note with the billable count and the numbers you assigned.",
+      "suggestedRole": "kantoormeester",
+      "advanceWhen": {
+        "file": "notes/billables.json",
+        "minBytes": 2,
+        "sniff": "json-valid"
+      },
+      "gate": {
+        "at": "completion",
+        "checks": [
+          {
+            "kind": "minBytes",
+            "file": "notes/scope.md",
+            "bytes": 120
+          },
+          {
+            "kind": "sniff",
+            "file": "notes/scope.md",
+            "sniff": "nonempty"
+          },
+          {
+            "kind": "sniff",
+            "file": "notes/billables.json",
+            "sniff": "json-valid"
+          }
+        ],
+        "onReject": "scope",
+        "maxAttempts": 3
+      },
+      "next": "draft"
+    },
+    {
+      "id": "draft",
+      "name": "Draft the invoices",
+      "description": "fan out one invoice draft per billable client",
+      "prompt": "The crew drafts the invoices — one print-ready HTML file per billable client, each built from notes/billables.json. This step fans the work out to the crew automatically; you do not draft the invoices yourself.",
+      "suggestedRole": "kantoormeester",
+      "spawnFanout": true,
+      "advanceWhen": {
+        "file": "notes/draft.md",
+        "minBytes": 1,
+        "sniff": "nonempty"
+      },
+      "next": "collect"
+    },
+    {
+      "id": "collect",
+      "name": "Collect and summarize",
+      "description": "verify the invoice files and write the run summary",
+      "prompt": "The crew has drafted one invoice file per billable client under invoices/. Read notes/billables.json and the files in invoices/, then write report.md — the month's run summary: Step 1: a headline sentence with how many invoices went out and the total billed. Step 2: one line per invoice — number, client, amount, due date. Step 3: state the sequence issued (from-to) and confirm it continues the books with no gap. Step 4: name any client skipped this month and why. Keep it to one page. Call write_task_note with the report path and the total billed. If fewer invoice files than billable clients exist yet, the crew is still drafting — re-check invoices/ and finish only once every billable client has its file.",
+      "suggestedRole": "copywriter",
+      "advanceWhen": {
+        "file": "report.md",
+        "minBytes": 1,
+        "sniff": "nonempty"
+      },
+      "gate": {
+        "at": "completion",
+        "checks": [
+          {
+            "kind": "minBytes",
+            "file": "report.md",
+            "bytes": 800
+          },
+          {
+            "kind": "fileCount",
+            "ext": [
+              "html"
+            ],
+            "min": 2,
+            "dir": "invoices"
+          }
+        ],
+        "scripts": [
+          {
+            "name": "checkContains",
+            "scope": "standard",
+            "inputs": {
+              "file": "report.md",
+              "pattern": "(?:^|\\n)#{1,3}\\s+\\S",
+              "flags": "i"
+            }
+          }
+        ],
+        "onReject": "collect",
+        "maxAttempts": 6
+      },
+      "next": "evaluate"
+    },
+    {
+      "id": "evaluate",
+      "name": "Evaluate",
+      "description": "Grade the run against every acceptance criterion. All pass -> finish; any fail -> loop back to draft.",
+      "prompt": "Open the invoice files under invoices/, notes/billables.json, and report.md, and verify every criterion from notes/scope.md: every billable client has exactly one invoice file of its own, every amount traces to the ledger, the numbers continue the sequence with no skip or repeat, due dates match each client's terms, and report.md names any client skipped on purpose. Write PASS/FAIL per criterion.\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: \"draft\" }) to loop back so the missing or wrong invoice is redrafted.\n\nNever route to finish while any criterion is unmet. After ~3 unproductive loops, stop and report DONE_WITH_CONCERNS so the user can step in.",
+      "suggestedRole": "reviewer",
+      "next": "draft"
+    },
+    {
+      "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: the invoices issued, the sequence range, and the total billed. Then report DONE.",
+      "suggestedRole": "developer",
+      "terminal": true
+    }
+  ],
+  "spawn": {
+    "overFile": "notes/billables.json",
+    "entryStepId": "draft-invoice",
+    "steps": [
+      {
+        "id": "draft-invoice",
+        "name": "Draft the invoice for {{client}}",
+        "description": "one print-ready HTML invoice for {{client}}",
+        "prompt": "Draft the invoice for {{client}} (invoice number {{number}}) as one print-ready HTML file at invoices/{{number}}.html. Your task notes carry this client's details (read_task_notes). The invoice must show: {{client}} and their contact details; the invoice number {{number}} and the due date {{due}}; a line-items table for the work — {{work}} — with the amount {{rate}}; and a total that re-adds to {{rate}}. Style it for paper: an @page rule with honest margins and a @media print block so it prints cleanly. Write the whole file in one go with writeFile to invoices/{{number}}.html. Do not write any other client's invoice — the crew is handling those in parallel.",
+        "suggestedRole": "designer",
+        "advanceWhen": {
+          "file": "invoices/{{number}}.html",
+          "minBytes": 400,
+          "sniff": "html-complete"
+        },
+        "gate": {
+          "at": "completion",
+          "checks": [
+            {
+              "kind": "minBytes",
+              "file": "invoices/{{number}}.html",
+              "bytes": 400
+            },
+            {
+              "kind": "cssMinBytes",
+              "file": "invoices/{{number}}.html",
+              "bytes": 150
+            },
+            {
+              "kind": "contains",
+              "file": "invoices/{{number}}.html",
+              "pattern": "@page|@media\\s+print",
+              "flags": "i",
+              "label": "print CSS"
+            }
+          ],
+          "onReject": "draft-invoice",
+          "maxAttempts": 3
+        }
+      }
+    ]
+  },
+  "version": "1.0.1",
+  "releasedAt": "2026-07-25T22:45:00.000Z"
+}

package/data/craftbook-templates/in/invoice-run/versions/1.0.1/test.json

@@ -0,0 +1,140 @@
+{
+  "schemaVersion": 1,
+  "title": "Monthly Invoice Run — ledger to numbered, recorded invoices",
+  "objective": "Measure whether the invoice-run craftbook turns a seeded client roster and work ledger into one print-ready invoice per billable client with unbroken numbering, ledger-true amounts, and a run summary — numeric integrity is the class bar.",
+  "tags": [
+    "html-page"
+  ],
+  "prompt": "end of month — can you run the invoicing? three clients have billable work logged, last invoice number was 2026-041, dont break the sequnce",
+  "setup": {
+    "projectName": "Fieldnote Studio Office",
+    "about": "Freelance office for Fieldnote Studio, a one-person design practice. The client roster is workspace/clients.json and the work ledger is workspace/ledger.json; invoices go under workspace/invoices.",
+    "missionObjectives": "Invoice amounts come from the tracked ledger only, numbering continues without a skip or repeat, and the books record what went out. No live services, no real credentials.",
+    "files": [
+      {
+        "path": "clients.json",
+        "content": "{\n  \"clients\": [\n    {\n      \"name\": \"Harbor & Pine Architects\",\n      \"contact\": \"billing@harborpine.example\",\n      \"terms\": \"net 30\"\n    },\n    {\n      \"name\": \"Kestrel Coffee Roasters\",\n      \"contact\": \"anna@kestrelroasters.example\",\n      \"terms\": \"net 14\"\n    },\n    {\n      \"name\": \"Bluestem Community Fund\",\n      \"contact\": \"office@bluestemfund.example\",\n      \"terms\": \"net 30\"\n    },\n    {\n      \"name\": \"Ondaatje Books\",\n      \"contact\": \"marguerite@ondaatjebooks.example\",\n      \"terms\": \"net 30\",\n      \"note\": \"retainer paused — no work this month\"\n    }\n  ]\n}\n"
+      },
+      {
+        "path": "ledger.json",
+        "content": "{\n  \"lastInvoiceNumber\": \"2026-041\",\n  \"entries\": [\n    {\n      \"date\": \"2026-07-03\",\n      \"client\": \"Harbor & Pine Architects\",\n      \"description\": \"Project signage system — concept and revisions\",\n      \"amount\": 1840.00,\n      \"invoiced\": false\n    },\n    {\n      \"date\": \"2026-07-11\",\n      \"client\": \"Kestrel Coffee Roasters\",\n      \"description\": \"Seasonal packaging refresh — three SKUs\",\n      \"amount\": 2600.00,\n      \"invoiced\": false\n    },\n    {\n      \"date\": \"2026-07-18\",\n      \"client\": \"Bluestem Community Fund\",\n      \"description\": \"Annual report layout, 24 pages\",\n      \"amount\": 975.00,\n      \"invoiced\": false\n    },\n    {\n      \"date\": \"2026-06-24\",\n      \"client\": \"Harbor & Pine Architects\",\n      \"description\": \"Wayfinding audit — invoiced on 2026-041\",\n      \"amount\": 1200.00,\n      \"invoiced\": true,\n      \"invoice\": \"2026-041\"\n    }\n  ]\n}\n"
+      }
+    ],
+    "worker": {
+      "name": "Jules",
+      "role": "Office manager"
+    }
+  },
+  "mocks": [],
+  "success": {
+    "summary": "invoices/ holds a print-ready invoice per billable client plus a run sheet whose numbers continue 2026-041 and whose amounts are ledger-true; report.md summarizes the run.",
+    "deliverables": [
+      {
+        "path": "report.md",
+        "kind": "markdown-report",
+        "minBytes": 800,
+        "checks": [
+          {
+            "kind": "contains",
+            "file": "report.md",
+            "pattern": "(?:^|\\n)#{1,3}\\s+\\S"
+          },
+          {
+            "kind": "contains",
+            "file": "report.md",
+            "pattern": "total",
+            "flags": "i",
+            "label": "total billed stated"
+          },
+          {
+            "kind": "contains",
+            "file": "report.md",
+            "pattern": "Ondaatje",
+            "label": "the skipped client is named, not silently dropped"
+          },
+          {
+            "kind": "contains",
+            "file": "report.md",
+            "pattern": "2026-04[2-9]",
+            "label": "numbering continues the sequence"
+          },
+          {
+            "kind": "valueGrounding",
+            "file": "report.md",
+            "facts": [
+              {
+                "id": "harbor-amount",
+                "label": "Harbor & Pine amount from the ledger",
+                "required": [
+                  "1,?840(?:\\.00)?"
+                ]
+              },
+              {
+                "id": "kestrel-amount",
+                "label": "Kestrel amount from the ledger",
+                "required": [
+                  "2,?600(?:\\.00)?"
+                ]
+              },
+              {
+                "id": "bluestem-amount",
+                "label": "Bluestem amount from the ledger",
+                "required": [
+                  "975(?:\\.00)?"
+                ]
+              }
+            ]
+          }
+        ]
+      }
+    ],
+    "checks": [
+      {
+        "kind": "fileCount",
+        "ext": [
+          "html"
+        ],
+        "min": 3,
+        "dir": "invoices"
+      },
+      {
+        "kind": "sniff",
+        "file": "ledger.json",
+        "sniff": "json-valid"
+      }
+    ]
+  },
+  "rubric": {
+    "artifact": {
+      "path": "report.md",
+      "kind": "markdown"
+    },
+    "axes": [
+      {
+        "name": "numeric integrity",
+        "description": "Every amount traces to a tracked ledger entry; nothing estimated or invented."
+      },
+      {
+        "name": "numbering continuity",
+        "description": "Invoice numbers continue 2026-041 with no skip and no repeat."
+      },
+      {
+        "name": "professionalism",
+        "description": "The invoices look worth paying — clear line items, terms-correct due dates, print-ready pages."
+      },
+      {
+        "name": "completeness",
+        "description": "One invoice per billable client, the idle client skipped on purpose, and the books updated."
+      },
+      {
+        "name": "print-polish",
+        "description": "Each invoice is styled for paper — an @page rule, honest margins, a professional face."
+      }
+    ]
+  },
+  "qualityFocus": [
+    "ledger-true amounts",
+    "sequence continuity",
+    "print-ready invoices"
+  ]
+}