@bendyline/gilde 0.1.26 → 0.1.28

package/data/craftbook-templates/em/email-sequence/versions/1.0.1/craftbook.json

@@ -0,0 +1,142 @@
+{
+  "id": "email-sequence",
+  "name": "Lifecycle Email Sequence",
+  "description": "Design and build a multi-email lifecycle sequence (welcome, onboarding, nurture, re-engagement) that moves a subscriber from one stage to the next: it first maps the customer journey — entry trigger, the goal of each email, send timing/cadence, and the one CTA per email — then drafts every email's subject line, preview text, and body to its single goal, then builds the sequence into a client-safe, inline-styled HTML email set ready to load into an ESP. Covers email sequence, drip campaign, welcome series, onboarding emails, nurture sequence, and lifecycle marketing. Journey-mapping before writing is the point: a small model that assigns each email one job and one CTA avoids the redundant sequence where every email says the same thing and asks for everything at once.\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. Journey scope (planner) — map the sequence: trigger, per-email goal, cadence, one CTA each → gated on artifact `notes/journey-scope.md` (markdown-notes)\n2. Draft the emails (copywriter) — write each email to its single goal and CTA → gated on artifact `notes/draft.md` (markdown-notes)\n3. Build the email set (developer) — render the sequence to client-safe inline-styled HTML → gated on `index.html` (html-page)\n\nThe gates never advance with an unmet criterion, and loop back to the\nowning phase to fix named gaps.\n",
+  "entryStepId": "journey-scope",
+  "triggers": [
+    "build an email sequence",
+    "welcome email series",
+    "drip campaign",
+    "nurture sequence",
+    "onboarding emails"
+  ],
+  "steps": [
+    {
+      "id": "journey-scope",
+      "name": "Journey scope",
+      "description": "map the sequence: trigger, per-email goal, cadence, one CTA each",
+      "prompt": "1) Define the sequence type and entry trigger (e.g. signed up, abandoned cart, went inactive). 2) Define the end goal (activate, convert, re-engage). 3) Lay out the emails in order — for EACH email specify: its single goal, send timing/delay (e.g. Day 0, Day 2, Day 5), the one CTA, and the key message. Each email does ONE job. 4) Note the audience and tone. Write an acceptance-criteria checklist (e.g. 'each email has exactly one goal and one CTA'; 'no two emails are redundant'; 'cadence/timing specified per email'; 'subject lines are distinct and curiosity/benefit-driven'; 'the arc progresses toward the end goal'; 'unsubscribe link present in each'). Use write_task_note for the journey map + per-email plan + checklist, and write the same to the produces path. No email copy yet.\n\nThe deliverable `notes/journey-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": "notes/journey-scope.md",
+        "minBytes": 1,
+        "sniff": "nonempty",
+        "artifact": true
+      },
+      "gate": {
+        "at": "completion",
+        "checks": [
+          {
+            "kind": "minBytes",
+            "file": "notes/journey-scope.md",
+            "bytes": 120,
+            "artifact": true
+          },
+          {
+            "kind": "sniff",
+            "file": "notes/journey-scope.md",
+            "sniff": "nonempty",
+            "artifact": true
+          }
+        ],
+        "onReject": "journey-scope",
+        "maxAttempts": 3
+      },
+      "next": "draft"
+    },
+    {
+      "id": "draft",
+      "name": "Draft the emails",
+      "description": "write each email to its single goal and CTA",
+      "prompt": "Write every email in the sequence to its mapped goal. 1) For each email provide: subject line (<=50 chars, distinct from the others), preview/preheader text (<=90 chars), and body. 2) The body serves the email's ONE goal and drives its ONE CTA — do not cram in unrelated asks. 3) Make the sequence progress: later emails build on earlier ones, none is redundant. 4) Keep a consistent brand voice, short scannable paragraphs, and a single primary CTA button per email. 5) Record each email's send timing from the map. Save the drafted copy (with email number, timing, subject, preview, body, CTA) to the produces path as structured markdown. Note which checklist items pass.\n\nThe deliverable `notes/draft.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": "notes/draft.md",
+        "minBytes": 1,
+        "sniff": "nonempty",
+        "artifact": true
+      },
+      "gate": {
+        "at": "completion",
+        "checks": [
+          {
+            "kind": "minBytes",
+            "file": "notes/draft.md",
+            "bytes": 120,
+            "artifact": true
+          },
+          {
+            "kind": "sniff",
+            "file": "notes/draft.md",
+            "sniff": "nonempty",
+            "artifact": true
+          }
+        ],
+        "onReject": "draft",
+        "maxAttempts": 3
+      },
+      "next": "build"
+    },
+    {
+      "id": "build",
+      "name": "Build the email set",
+      "description": "render the sequence to client-safe inline-styled HTML",
+      "prompt": "Build the approved copy into a deliverable, client-safe HTML email sequence in a single index.html. 1) Render each email as its own clearly separated section/block within the page (with a heading like 'Email 1 — Day 0 — subject'), so the whole sequence is previewable in one file. 2) Use email-safe HTML: inline styles only (no external CSS or <style> reliance), table-based layout where needed, web-safe fonts, and absolute links. 3) Include the subject and preview text as labeled metadata, a single prominent CTA button per email, and an unsubscribe link in each email's footer. 4) Keep it responsive at common widths. On a loop-back, fix only the named gaps. Save to the produces path (index.html) and note the email count.",
+      "suggestedRole": "developer",
+      "advanceWhen": {
+        "file": "index.html",
+        "minBytes": 1,
+        "sniff": "html-complete"
+      },
+      "gate": {
+        "at": "completion",
+        "checks": [
+          {
+            "kind": "minBytes",
+            "file": "index.html",
+            "bytes": 800
+          },
+          {
+            "kind": "htmlLint",
+            "file": "index.html"
+          }
+        ],
+        "scripts": [
+          {
+            "name": "checkHtmlComplete",
+            "scope": "standard",
+            "inputs": {
+              "file": "index.html"
+            }
+          }
+        ],
+        "onReject": "build",
+        "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": "Open index.html (render it if a browser/QA capability is available; otherwise read the source) and grade against the checklist. Check EACH criterion and write PASS/FAIL: (a) every planned email is present as a labeled section with subject + preview + body; (b) each email has exactly one CTA and one goal; (c) no two emails are redundant and the arc progresses toward the end goal; (d) subject lines are distinct and within length; (e) styles are inline/email-safe (no reliance on external CSS); (f) an unsubscribe link is present in each email. A sequence where emails are redundant or use non-email-safe CSS FAILS — 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",
+      "consumes": [
+        {
+          "file": "index.html"
+        }
+      ],
+      "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",
+      "terminal": true
+    }
+  ],
+  "version": "1.0.1",
+  "releasedAt": "2026-08-14T00:00:00Z"
+}

package/data/craftbook-templates/em/email-sequence/versions/1.0.1/test.json

@@ -0,0 +1,97 @@
+{
+  "schemaVersion": 1,
+  "title": "Lifecycle Email Sequence smoke eval",
+  "objective": "Self-contained smoke eval for the Lifecycle Email Sequence craftbook using the html-page generic harness.",
+  "tags": [
+    "html-page"
+  ],
+  "prompt": "Can you biuld us a little page for this? The content notes are in source/page-content.md. Save it as index.html — one file, nothing fancy needed on our end.",
+  "setup": {
+    "projectName": "Lifecycle Email Sequence Eval",
+    "about": "Self-contained eval project for email-sequence. Seeded inputs are under workspace/source or workspace/fixtures; final deliverable is workspace/index.html.",
+    "missionObjectives": "Use the Lifecycle Email Sequence craftbook/template, read the seeded local fixtures, and write index.html without network calls, real credentials, or live services.",
+    "files": [
+      {
+        "path": "source/brief.md",
+        "content": "# Lifecycle Email Sequence 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: email-sequence - Lifecycle Email Sequence.\n"
+      },
+      {
+        "path": "source/page-content.md",
+        "content": "# Boreal Desk Support Board\n\nBuild content around a support operations board. Required labels: Open issues, Status silence, Response time, Refund leakage, Next action. Required metric text: 18 hours to 6 hours and 14.2% to 8.9%.\n"
+      }
+    ],
+    "worker": {
+      "name": "Jules",
+      "role": "Developer"
+    }
+  },
+  "mocks": [],
+  "success": {
+    "summary": "index.html is a source-grounded self-contained HTML page/tool.",
+    "deliverables": [
+      {
+        "path": "index.html",
+        "kind": "html-page",
+        "minBytes": 3000,
+        "checks": [
+          {
+            "kind": "cssMinBytes",
+            "bytes": 650,
+            "file": "index.html"
+          },
+          {
+            "kind": "jsParses",
+            "file": "index.html"
+          },
+          {
+            "kind": "contains",
+            "file": "index.html",
+            "pattern": "Boreal|Support Board|returns",
+            "flags": "i"
+          },
+          {
+            "kind": "contains",
+            "file": "index.html",
+            "pattern": "18\\s*hours|6\\s*hours|14\\.2%|8\\.9%",
+            "flags": "i"
+          },
+          {
+            "kind": "contains",
+            "file": "index.html",
+            "pattern": "button|input|filter|tab|card|section|nav",
+            "flags": "i"
+          }
+        ]
+      }
+    ]
+  },
+  "rubric": {
+    "artifact": {
+      "path": "index.html",
+      "kind": "html"
+    },
+    "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": [
+    "self-contained UI",
+    "source grounding",
+    "responsive structure"
+  ]
+}

package/data/craftbook-templates/em/email-template/versions/1.0.1/craftbook.json

@@ -0,0 +1,143 @@
+{
+  "id": "email-template",
+  "name": "Responsive HTML Email",
+  "description": "Build a responsive HTML email template that renders across email clients — Outlook, Gmail, Apple Mail — using table-based layout, inline styles, and bulletproof buttons, for a newsletter, transactional, or promo send. Designs the visual structure and the client-safe constraints first, writes the copy, then builds the table-based HTML with all CSS inlined. Email is not the web: external CSS, flexbox, and modern selectors break, so the design phase locks the table layout and inline-only rule before any markup, the ordering that keeps a small model from producing a div-and-class email that renders broken in Outlook.\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. Email design (visual-designer) — table layout, palette, client-safe constraints → gated on artifact `notes/design.md` (markdown-notes)\n2. Copywriting (copywriter) — subject, preheader, body copy, CTA label → gated on artifact `notes/copy.md` (markdown-notes)\n3. Build (developer) — implement email.html with table layout + inline CSS → gated on `email.html` (html-page)\n\nThe gates never advance with an unmet criterion, and loop back to the\nowning phase to fix named gaps.\n",
+  "entryStepId": "design",
+  "triggers": [
+    "html email",
+    "email template",
+    "newsletter email",
+    "responsive email",
+    "marketing email",
+    "build an email"
+  ],
+  "steps": [
+    {
+      "id": "design",
+      "name": "Email design",
+      "description": "table layout, palette, client-safe constraints",
+      "prompt": "Design the email within email's constraints. (1) Pick a palette (hex) and a single web-safe font stack with fallbacks. (2) Lay out the structure as nested tables: a centered container (max ~600px), header/logo, hero, body sections, a bulletproof CTA button, and footer with unsubscribe. (3) State the hard rules: table-based layout, ALL CSS inline on elements, no external stylesheets, no flexbox/grid, images with width/alt and a text fallback. (4) Define the mobile behavior (single column, scalable text). (5) Write an acceptance-criteria checklist of 6-8 items, e.g. 'layout uses tables not divs', 'all styles are inline', 'container is max ~600px and centered', 'a bulletproof CTA button is present', 'a footer with unsubscribe exists', 'images have alt text', 'no external CSS or web fonts'. Write to notes/design.md and via write_task_note. No markup yet.\n\nThe deliverable `notes/design.md` lands in the project's artifacts drawer — write it with `write_artifact` and read it back with `read_artifact`; the shipped workspace stays untouched.",
+      "suggestedRole": "visual-designer",
+      "advanceWhen": {
+        "file": "notes/design.md",
+        "minBytes": 1,
+        "sniff": "nonempty",
+        "artifact": true
+      },
+      "gate": {
+        "at": "completion",
+        "checks": [
+          {
+            "kind": "minBytes",
+            "file": "notes/design.md",
+            "bytes": 120,
+            "artifact": true
+          },
+          {
+            "kind": "sniff",
+            "file": "notes/design.md",
+            "sniff": "nonempty",
+            "artifact": true
+          }
+        ],
+        "onReject": "design",
+        "maxAttempts": 3
+      },
+      "next": "copy"
+    },
+    {
+      "id": "copy",
+      "name": "Copywriting",
+      "description": "subject, preheader, body copy, CTA label",
+      "prompt": "Write the email copy. (1) A subject line and a preheader (the preview snippet). (2) A headline and the body sections' copy, tight and scannable. (3) The CTA button label (action verb). (4) Footer text including an unsubscribe line and sender info. Match the send's purpose (newsletter, transactional, promo). Write the copy keyed by slot to notes/copy.md and via write_task_note.\n\nThe deliverable `notes/copy.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": "notes/copy.md",
+        "minBytes": 1,
+        "sniff": "nonempty",
+        "artifact": true
+      },
+      "gate": {
+        "at": "completion",
+        "checks": [
+          {
+            "kind": "minBytes",
+            "file": "notes/copy.md",
+            "bytes": 120,
+            "artifact": true
+          },
+          {
+            "kind": "sniff",
+            "file": "notes/copy.md",
+            "sniff": "nonempty",
+            "artifact": true
+          }
+        ],
+        "onReject": "copy",
+        "maxAttempts": 3
+      },
+      "next": "build"
+    },
+    {
+      "id": "build",
+      "name": "Build",
+      "description": "implement email.html with table layout + inline CSS",
+      "prompt": "Implement email.html as a client-safe HTML email to the design and copy. (1) Use nested <table> layout with a centered max-600px container; NO divs-for-layout, NO external CSS, NO flexbox/grid. (2) Put every style inline on the element via style attributes. (3) Include the preheader as hidden preview text near the top. (4) Build a bulletproof CTA button (a styled table-cell anchor that survives Outlook). (5) Add alt text to images and a footer with an unsubscribe link. (6) Ensure it degrades to a single column on narrow widths. On a loop-back, fix only the named gaps without regressing passing criteria. write_task_note the path and passing criteria.",
+      "suggestedRole": "developer",
+      "advanceWhen": {
+        "file": "email.html",
+        "minBytes": 1,
+        "sniff": "html-complete"
+      },
+      "gate": {
+        "at": "completion",
+        "checks": [
+          {
+            "kind": "minBytes",
+            "file": "email.html",
+            "bytes": 1200
+          },
+          {
+            "kind": "htmlLint",
+            "file": "email.html"
+          }
+        ],
+        "scripts": [
+          {
+            "name": "checkHtmlComplete",
+            "scope": "standard",
+            "inputs": {
+              "file": "email.html"
+            }
+          }
+        ],
+        "onReject": "build",
+        "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": "Evaluate the email for client-safety. Open/render email.html and inspect the source. Check EACH criterion from notes/design.md and write PASS/FAIL with a reason: is the layout table-based (grep for layout <div> — should be none), are ALL styles inline (no <style> block doing layout, no external <link>), is the container ~600px and centered, is there a bulletproof CTA button, a footer with unsubscribe, image alt text, and zero web fonts/external CSS? Any external CSS or div-based layout is a FAIL — 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",
+      "consumes": [
+        {
+          "file": "email.html"
+        }
+      ],
+      "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",
+      "terminal": true
+    }
+  ],
+  "version": "1.0.1",
+  "releasedAt": "2026-08-14T00:00:00Z"
+}

package/data/craftbook-templates/em/email-template/versions/1.0.1/test.json

@@ -0,0 +1,97 @@
+{
+  "schemaVersion": 1,
+  "title": "Responsive HTML Email smoke eval",
+  "objective": "Self-contained smoke eval for the Responsive HTML Email craftbook using the html-page generic harness.",
+  "tags": [
+    "html-page"
+  ],
+  "prompt": "Can you biuld us a little page for this? The content notes are in source/page-content.md. Save it as index.html — one file, nothing fancy needed on our end.",
+  "setup": {
+    "projectName": "Responsive HTML Email Eval",
+    "about": "Self-contained eval project for email-template. Seeded inputs are under workspace/source or workspace/fixtures; final deliverable is workspace/index.html.",
+    "missionObjectives": "Use the Responsive HTML Email craftbook/template, read the seeded local fixtures, and write index.html without network calls, real credentials, or live services.",
+    "files": [
+      {
+        "path": "source/brief.md",
+        "content": "# Responsive HTML Email 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: email-template - Responsive HTML Email.\n"
+      },
+      {
+        "path": "source/page-content.md",
+        "content": "# Boreal Desk Support Board\n\nBuild content around a support operations board. Required labels: Open issues, Status silence, Response time, Refund leakage, Next action. Required metric text: 18 hours to 6 hours and 14.2% to 8.9%.\n"
+      }
+    ],
+    "worker": {
+      "name": "Jules",
+      "role": "Developer"
+    }
+  },
+  "mocks": [],
+  "success": {
+    "summary": "index.html is a source-grounded self-contained HTML page/tool.",
+    "deliverables": [
+      {
+        "path": "index.html",
+        "kind": "html-page",
+        "minBytes": 3000,
+        "checks": [
+          {
+            "kind": "cssMinBytes",
+            "bytes": 650,
+            "file": "index.html"
+          },
+          {
+            "kind": "jsParses",
+            "file": "index.html"
+          },
+          {
+            "kind": "contains",
+            "file": "index.html",
+            "pattern": "Boreal|Support Board|returns",
+            "flags": "i"
+          },
+          {
+            "kind": "contains",
+            "file": "index.html",
+            "pattern": "18\\s*hours|6\\s*hours|14\\.2%|8\\.9%",
+            "flags": "i"
+          },
+          {
+            "kind": "contains",
+            "file": "index.html",
+            "pattern": "button|input|filter|tab|card|section|nav",
+            "flags": "i"
+          }
+        ]
+      }
+    ]
+  },
+  "rubric": {
+    "artifact": {
+      "path": "index.html",
+      "kind": "html"
+    },
+    "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": [
+    "self-contained UI",
+    "source grounding",
+    "responsive structure"
+  ]
+}