@bendyline/gilde 0.1.51 → 0.1.52

package/data/craftbook-templates/al/alert-rules/versions/1.0.3/test.json

@@ -0,0 +1,145 @@
+{
+  "schemaVersion": 1,
+  "title": "Prometheus alerts from scoped SLO brief",
+  "objective": "Measure whether the alert-rules craftbook scopes symptom alerts before writing deployable, low-noise alerting YAML.",
+  "tags": [
+    "html-page"
+  ],
+  "prompt": "In the `Alert Rules Eval` project, read `source/slo-brief.md` and write `alerts.yaml` as Prometheus-style alerting rules. Scope the signals and noise budget first, then produce YAML with groups, alert names, expr, for, severity/routing labels, summaries, descriptions, and runbook_url annotations for page alerts.",
+  "setup": {
+    "projectName": "Alert Rules Eval",
+    "about": "Self-contained eval project for alert-rules. The service SLO brief is in workspace/source/slo-brief.md and the deliverable is workspace/alerts.yaml.",
+    "missionObjectives": "Produce low-noise alerting rules from the seeded SLO brief with symptom signals, thresholds, severities, runbook links, and routing labels.",
+    "files": [
+      {
+        "path": "source/slo-brief.md",
+        "content": "# Alert scope brief\n\nService: Harbor Payments checkout-api and webhook-worker.\n\nSLOs:\n- Checkout p99 latency should stay below 800 ms over 10 minutes.\n- Checkout 5xx error rate should stay below 2% over 5 minutes.\n- Webhook retry backlog should stay below 5,000 jobs for more than 10 minutes.\n\nRouting:\n- page severity routes to team=payments, service=checkout-api or webhook-worker.\n- ticket severity routes to team=payments during business hours.\n- Page-level noise budget: no more than two page alerts.\n- Required runbooks: https://runbooks.example/payments/checkout-latency, https://runbooks.example/payments/checkout-errors, https://runbooks.example/payments/webhook-backlog.\n"
+      }
+    ],
+    "worker": {
+      "name": "Aafke",
+      "role": "SRE"
+    }
+  },
+  "mocks": [],
+  "success": {
+    "summary": "workspace/alerts.yaml is a Prometheus-style rule file with scoped symptom signals, thresholds, severities, routing, runbook annotations, and noise-budget evidence.",
+    "deliverables": [
+      {
+        "path": "alerts.yaml",
+        "kind": "yaml-spec",
+        "minBytes": 1200,
+        "checks": [
+          {
+            "kind": "prometheusAlerts",
+            "file": "alerts.yaml",
+            "minRules": 3,
+            "maxPageAlerts": 2,
+            "allowedSeverities": [
+              "page",
+              "ticket",
+              "info"
+            ],
+            "requiredServices": [
+              "checkout-api",
+              "webhook-worker"
+            ],
+            "requiredRunbookUrls": [
+              "https://runbooks.example/payments/checkout-latency",
+              "https://runbooks.example/payments/checkout-errors",
+              "https://runbooks.example/payments/webhook-backlog"
+            ]
+          },
+          {
+            "kind": "contains",
+            "file": "alerts.yaml",
+            "pattern": "groups:|rules:|alert:|expr:|for:",
+            "flags": "i"
+          },
+          {
+            "kind": "contains",
+            "file": "alerts.yaml",
+            "pattern": "severity:|team:|service:",
+            "flags": "i"
+          },
+          {
+            "kind": "contains",
+            "file": "alerts.yaml",
+            "pattern": "runbook_url|runbook",
+            "flags": "i"
+          },
+          {
+            "kind": "contains",
+            "file": "alerts.yaml",
+            "pattern": "checkout-api|webhook-worker|latency|error|backlog",
+            "flags": "i"
+          },
+          {
+            "kind": "contains",
+            "file": "alerts.yaml",
+            "pattern": "800|0\\.8|2%|0\\.02|5000|5,000|10m|5m",
+            "flags": "i"
+          },
+          {
+            "kind": "contains",
+            "file": "alerts.yaml",
+            "pattern": "histogram_quantile|p99|0\\.99",
+            "flags": "i",
+            "label": "checkout latency alert uses a p99 signal"
+          },
+          {
+            "kind": "contains",
+            "file": "alerts.yaml",
+            "pattern": "5xx|5\\.\\.|status",
+            "flags": "i",
+            "label": "checkout error alert targets 5xx rate"
+          },
+          {
+            "kind": "contains",
+            "file": "alerts.yaml",
+            "pattern": "retry|backlog|5000|5,000",
+            "flags": "i",
+            "label": "webhook backlog alert uses retry backlog threshold"
+          },
+          {
+            "kind": "notContains",
+            "file": "alerts.yaml",
+            "pattern": "CPU|memory|disk|node_cpu|node_memory|node_filesystem",
+            "flags": "i",
+            "label": "avoid raw infrastructure cause alerts not present in the SLO brief"
+          }
+        ]
+      }
+    ]
+  },
+  "rubric": {
+    "artifact": {
+      "path": "alerts.yaml",
+      "kind": "yaml"
+    },
+    "axes": [
+      {
+        "name": "structure",
+        "description": "Layout and hierarchy fit the content; sections are scannable and coherent."
+      },
+      {
+        "name": "grounding",
+        "description": "Seeded source content is used faithfully — no invented facts or dropped requirements."
+      },
+      {
+        "name": "interactivity",
+        "description": "Controls and states the page claims to offer actually work."
+      },
+      {
+        "name": "polish",
+        "description": "Styling is intentional and responsive rather than unstyled or broken."
+      }
+    ]
+  },
+  "qualityFocus": [
+    "symptom alerts",
+    "noise budget",
+    "runbook annotations",
+    "routing labels"
+  ]
+}

package/data/craftbook-templates/an/anniversary-cut/versions/1.0.5/craftbook.json

@@ -0,0 +1,381 @@
+{
+  "id": "anniversary-cut",
+  "name": "Anniversary Cut",
+  "description": "Build the highlight reel for the occasion: the archive queried for the person and the years that matter, clips chosen with stated reasons, assembled through the project's media pipeline with a run log, and delivered with a chapter list and a dedication — the reel that makes the birthday. Locks the occasion and the selection criteria FIRST (era coverage, the famous moments in, a length budget), then selects from the archive with no invented footage, then assembles, then writes the presentation notes. Use for birthday reels, anniversary videos, memorial montages, 'make a highlight reel', and milestone tributes.\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 occasion (filmarchivaris) — occasion, person, selection criteria and length budget locked → gated on artifact `{{workPath}}/scope.md` (markdown-notes)\n2. Select the clips (curator) — the cut list: archive clips chosen with reasons, in reel order → gated on `cutlist.json` (json)\n3. Assemble the reel (developer) — the reel rendered through the media pipeline, log on disk → gated on `renders/assembly-log.json` (json)\n4. Chapters and dedication (copywriter) — the chapter list, the dedication, how to play it on the day → gated on artifact `{{workPath}}/report.md` (markdown-report)\n\nThe gates never advance with an unmet criterion, and loop back to the\nowning phase to fix named gaps.\n",
+  "entryStepId": "scope",
+  "triggers": [
+    "make a highlight reel",
+    "anniversary video",
+    "birthday montage",
+    "put together a tribute",
+    "clips of grandma over the years"
+  ],
+  "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 occasion",
+      "description": "occasion, person, selection criteria and length budget locked",
+      "prompt": "Define the reel before pulling a single clip. Step 1: name the occasion and the person it honors, and read family.md so names and relationships are right. Step 2: read clips.json — the archive's indexed moments — and survey what exists for this person: which tapes, which years, which of the family-famous moments are on file. Step 3: lock the selection criteria — the reel covers the person's eras rather than clustering in one year, the moments the family always retells make the cut, every selection carries a stated reason, only clips that exist in the archive may be used (no invented footage, ever), and the total sticks to a length budget you set now from the occasion. Step 4: write an acceptance-criteria checklist ('every selected clip exists in clips.json', 'every selection has a reason', 'eras covered per the criteria', 'total within the length budget', 'assembled through the project's pipeline script via run_installed_script with a status-ok log', 'chapter list and dedication delivered'). Call write_task_note with the occasion + archive counts + checklist and write {{workPath}}/scope.md.\n\nThe deliverable `{{workPath}}/scope.md` lands in the project's artifacts drawer — write it with `write_artifact` and read it back with `read_artifact`; the shipped workspace stays untouched.",
+      "suggestedRole": "filmarchivaris",
+      "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": "select",
+      "toolPolicy": {
+        "disallowBuiltinToolsets": [
+          "ai-apps",
+          "audio",
+          "browser-automation",
+          "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": "select",
+      "name": "Select the clips",
+      "description": "the cut list: archive clips chosen with reasons, in reel order",
+      "prompt": "Choose the reel's clips from the archive against the locked criteria. Step 1: sweep clips.json for every candidate moment featuring the person, across all tapes and years. Step 2: select — the famous moments first, then the quieter ones that show an era the famous ones miss; cut candidates that repeat a beat already covered. Every clip id must come from clips.json exactly as indexed; if a moment the family remembers is not in the archive, note it as missing footage rather than inventing a reference. Step 3: order the selections into the reel's emotional arc — chronology is the default, but a strong opening and a strong close outrank strict order. Step 4: write cutlist.json as a JSON array, each record with the clip id from the archive and the reason it made the cut; keep the running total inside the length budget. Call write_task_note with the selection count, the era coverage in one line, and anything remembered-but-missing.",
+      "suggestedRole": "curator",
+      "advanceWhen": {
+        "file": "cutlist.json",
+        "minBytes": 1,
+        "sniff": "json-valid"
+      },
+      "gate": {
+        "at": "completion",
+        "checks": [
+          {
+            "kind": "minBytes",
+            "file": "cutlist.json",
+            "bytes": 2
+          },
+          {
+            "kind": "recordSchema",
+            "file": "cutlist.json",
+            "fields": [
+              {
+                "name": "clip",
+                "type": "nonempty"
+              },
+              {
+                "name": "reason",
+                "type": "nonempty"
+              }
+            ],
+            "minRows": 5
+          },
+          {
+            "kind": "valuesSubsetOf",
+            "file": "cutlist.json",
+            "sourceFiles": [
+              "clips.json"
+            ],
+            "pattern": "\"clip\"\\s*:\\s*\"([^\"]+)\""
+          }
+        ],
+        "scripts": [
+          {
+            "name": "checkJsonValid",
+            "scope": "standard",
+            "inputs": {
+              "file": "cutlist.json"
+            }
+          }
+        ],
+        "onReject": "select",
+        "maxAttempts": 3
+      },
+      "next": "assemble",
+      "toolPolicy": {
+        "disallowBuiltinToolsets": [
+          "ai-apps",
+          "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"
+        ]
+      }
+    },
+    {
+      "id": "assemble",
+      "name": "Assemble the reel",
+      "description": "the reel rendered through the media pipeline, log on disk",
+      "prompt": "Assemble the reel from the cut list. Step 1: the assembly pipeline is a project script — call list_scripts to find it, then run it with run_installed_script({ name: \"<script name>\" }); never run it with run_nodejs_script and never reimplement it. It reads cutlist.json and the archive index, refuses any clip it cannot find, writes the render into renders/, and writes its run log to renders/assembly-log.json with a status field. Step 2: if run_installed_script reports an error, read the error text, fix what it names, and run it again — never write renders/assembly-log.json yourself; a fabricated log on a family keepsake is still a fabricated log. Step 3: once it succeeds, read the log and confirm status ok, the clip list matching the cut list, and the computed duration inside the length budget. Call write_task_note with the run outcome and the reel's duration.",
+      "suggestedRole": "developer",
+      "consumes": [
+        {
+          "file": "cutlist.json"
+        }
+      ],
+      "advanceWhen": {
+        "file": "renders/assembly-log.json",
+        "minBytes": 1,
+        "sniff": "json-valid"
+      },
+      "gate": {
+        "at": "completion",
+        "checks": [
+          {
+            "kind": "minBytes",
+            "file": "renders/assembly-log.json",
+            "bytes": 2
+          },
+          {
+            "kind": "fileCount",
+            "ext": [
+              "mp4"
+            ],
+            "min": 1,
+            "dir": "renders"
+          },
+          {
+            "kind": "jsonPathEquals",
+            "file": "renders/assembly-log.json",
+            "path": "status",
+            "value": "ok",
+            "label": "the assembly log reports status ok"
+          }
+        ],
+        "scripts": [
+          {
+            "name": "checkJsonValid",
+            "scope": "standard",
+            "inputs": {
+              "file": "renders/assembly-log.json"
+            }
+          }
+        ],
+        "onReject": "assemble",
+        "maxAttempts": 3
+      },
+      "next": "report",
+      "toolPolicy": {
+        "disallowBuiltinToolsets": [
+          "ai-apps",
+          "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"
+        ]
+      }
+    },
+    {
+      "id": "report",
+      "name": "Chapters and dedication",
+      "description": "the chapter list, the dedication, how to play it on the day",
+      "prompt": "Write the presentation notes that turn a render into a gift. Step 1: write the chapter list — each selected moment in reel order with its rough position, who is in it, and one warm line about why it is there (the reasons from the cut list, written for the family rather than the archive). Step 2: write the dedication — a short paragraph to open or close the reel, in the family's voice, naming the occasion and the person. Step 3: add the practical notes — the reel's duration, where the render lives, and anything remembered-but-missing from the archive so nobody wonders why a famous moment is absent. Write {{workPath}}/report.md and call write_task_note with the report path and the chapter count.\n\nThe deliverable `{{workPath}}/report.md` lands in the project's artifacts drawer — write it with `write_artifact` and read it back with `read_artifact`; the shipped workspace stays untouched.",
+      "suggestedRole": "copywriter",
+      "advanceWhen": {
+        "file": "{{workPath}}/report.md",
+        "minBytes": 1,
+        "sniff": "nonempty",
+        "artifact": true
+      },
+      "gate": {
+        "at": "completion",
+        "checks": [
+          {
+            "kind": "minBytes",
+            "file": "{{workPath}}/report.md",
+            "bytes": 800,
+            "artifact": true
+          },
+          {
+            "kind": "contains",
+            "file": "{{workPath}}/report.md",
+            "pattern": "chapter",
+            "flags": "i",
+            "label": "a chapter list for the reel",
+            "artifact": true
+          },
+          {
+            "kind": "contains",
+            "file": "{{workPath}}/report.md",
+            "pattern": "(?:^|\\n)#{1,3}\\s+\\S",
+            "flags": "i",
+            "label": "at least one markdown heading",
+            "artifact": true
+          }
+        ],
+        "onReject": "report",
+        "maxAttempts": 4
+      },
+      "next": "evaluate",
+      "toolPolicy": {
+        "disallowBuiltinToolsets": [
+          "ai-apps",
+          "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, cutlist.json, renders/assembly-log.json, and clips.json and verify every criterion from {{workPath}}/scope.md: every selected clip id exists in the archive, every selection carries a real reason, the eras are covered per the criteria, the log reports status ok with a duration inside the length budget, the chapter list matches the assembled order, and the dedication names the occasion and the person warmly and correctly. Write PASS/FAIL per criterion; on any failure, name the gap and loop back to report — or to select if the selection itself is the problem.\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: \"report\" })` 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": "report",
+      "toolPolicy": {
+        "disallowBuiltinToolsets": [
+          "ai-apps",
+          "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.5",
+  "releasedAt": "2026-09-01T20:00:00Z",
+  "minGezelVersion": "1.26233"
+}