@mccaskie-labs/workbench-config 0.3.1 → 0.4.0

package/dist/capabilities.gen.js

@@ -1,6 +1,6 @@
 // Generated by `npm run capabilities:build` from capabilities/*.json. Do not edit.
 // check:capabilities fails in Checks when this file is stale.
-export const MANIFEST_VERSION = "9aae488ad117";
+export const MANIFEST_VERSION = "7ad8cef4de58";
 export const capabilities = {
     "ai": {
         "$schema": "./schema.json",
@@ -25,7 +25,9 @@ export const capabilities = {
                 "checkWriting",
                 "writingStops",
                 "writingNotes",
-                "writingFixNote"
+                "writingFixNote",
+                "Ai.reply",
+                "checkGuide"
             ]
         },
         "config": [
@@ -197,6 +199,13 @@ export const capabilities = {
                 "text": "Name a Workbench voice and spelling with the voice and spelling options, so the Gateway adds the text, or bring the app's own voice. Never paste Workbench's voice text into a prompt.",
                 "enforced_by": "gateway",
                 "probe": "ai.voice"
+            },
+            {
+                "id": "ai.reply-facts-from-code",
+                "kind": "must",
+                "text": "Draft replies with ai.reply from facts worked out by code (prices and dates from quote(), never from the AI), and show the draft in renderReplyBox for a person to check and copy. Never send a draft automatically, and never let a draft with needs_human_check go out unread.",
+                "enforced_by": "review",
+                "probe": "ai.reply"
             }
         ],
         "examples": [
@@ -213,6 +222,13 @@ export const capabilities = {
                 "lang": "ts",
                 "code": "const r = await ai.text({ model: 'claude-default', job: 'article.write', voice: 'conversational', spelling: 'en-AU', prompt })\nconst issues = checkWriting(r.text, { voice: 'conversational' })\nif (writingStops(issues).length > 0) await retryWith(prompt + writingFixNote(issues))",
                 "probe": "ai.voice"
+            },
+            {
+                "id": "ai.example.reply",
+                "title": "Draft a reply to an enquiry",
+                "lang": "ts",
+                "code": "import { REPLY_GUIDES } from './replies.generated'\nconst ai = createAi({ key: env.WORKBENCH_GATEWAY_KEY, env: workbenchEnv(env), url: env.WORKBENCH_GATEWAY_URL, replyGuides: REPLY_GUIDES })\nconst q = quote(settings, ask)\nconst draft = await ai.reply({\n  guide: 'venue-quote',\n  facts: { venue_name: venue.name, date: ask.date, available: q.available, packages: q.options.map((o) => ({ name: o.package, price: o.total.amount })), alternatives: q.alternatives.map((a) => a.date) },\n  incoming: { text, intake: read },\n  language: account.reply_language,\n})\nreturn html(renderReplyBox(draft, { againAction: `/enquiries/${id}/reply` }))",
+                "probe": "ai.reply"
             }
         ],
         "probes": [
@@ -292,20 +308,26 @@ export const capabilities = {
                 "half": "runtime",
                 "expect": "pass",
                 "cost_hint_usd": 0.008
+            },
+            {
+                "id": "ai.reply",
+                "half": "runtime",
+                "expect": "pass",
+                "cost_hint_usd": 0.005
             }
         ],
         "offer": {
             "pattern": "feature_or_content",
-            "when": "The client wants the app to write, summarise, sort, answer questions or pull details out of text with AI, as a feature visitors use, or wants wording for the site written once.",
+            "when": "The client wants the app to write, summarise, sort, answer questions or pull details out of text with AI, as a feature visitors use, or wants wording for the site written once, or wants ready-to-paste replies to the messages the business gets (quote requests, booking questions).",
             "say": "I'll do this with Workbench AI, which uses Claude through Workbench, so the app holds no AI key and spending has a monthly cap.",
             "answers_file": "workbench/ai/<name>.json",
             "per": "feature or piece of wording",
-            "answers_format": "For a feature: `{ \"format\": 1, \"route\": \"feature\", \"name\", \"about\" (the client's words), \"who\", \"cap_usd\", \"keep\", \"job\" }`, where `job` is the `X-Workbench-Job` the feature's calls send (`<name>` with dots, such as `quotes.estimate`), so its spending shows on its own line in Control. Write it, then build the feature with the package. For wording made once: `npx workbench-ai pick <name> <round>-<draft>` writes it from the draft the client picked, with the round's request ids and cost; never write one from nothing. Then put the wording into the strings catalogue (the workbench-strings skill), keyed for where it is shown. Drafts and their previews stay in `workbench/ai/drafts/`, which isn't committed.",
+            "answers_format": "For a feature: `{ \"format\": 1, \"route\": \"feature\", \"name\", \"about\" (the client's words), \"who\", \"cap_usd\", \"keep\", \"job\" }`, where `job` is the `X-Workbench-Job` the feature's calls send (`<name>` with dots, such as `quotes.estimate`), so its spending shows on its own line in Control. Write it, then build the feature with the package. For wording made once: `npx workbench-ai pick <name> <round>-<draft>` writes it from the draft the client picked, with the round's request ids and cost; never write one from nothing. Then put the wording into the strings catalogue (the workbench-strings skill), keyed for where it is shown. Drafts and their previews stay in `workbench/ai/drafts/`, which isn't committed. For replies: write the guide itself to `workbench/replies/<name>.json` (format 1: `name`, `version`, `voice`, `spelling`, `max_words`, `max_questions`, `facts` as a small JSON Schema with `x-money` on amounts and `format: date` on dates, `ask_order`, `guide` lines, `examples`, `never`), then run `npx workbench-ai replies generate`, which checks it and writes `src/replies.generated.ts`; never edit that file. Offer samples with `npx workbench-ai replies drafts <name> --languages <the client's languages>` (two to four, with the development key; tell the client the cost it prints) and keep the one the client picks with `npx workbench-ai replies pick <name> <round>-<draft>`, which makes it the guide's first example.",
             "questions": [
                 {
                     "id": "ai.route",
                     "sets": "route",
-                    "ask": "Is this something visitors use on the site, or something made once for the site?",
+                    "ask": "Is this something visitors use on the site, something made once for the site, or replies to the messages you get?",
                     "style": "cards",
                     "answers": [
                         {
@@ -317,10 +339,15 @@ export const capabilities = {
                             "label": "Made once for the site",
                             "value": "content",
                             "means": "Wording for a page, written once and kept: an About page, a welcome, product descriptions."
+                        },
+                        {
+                            "label": "Replies to messages",
+                            "value": "reply",
+                            "means": "A ready-to-paste reply to a customer's message, with your prices and dates filled in from your own details. A person checks it and copies it; nothing is sent by itself."
                         }
                     ],
                     "must_ask": true,
-                    "note": "Ask it even when the client's words seem to say, as a quick check: the two routes are built and paid for differently."
+                    "note": "Ask it even when the client's words seem to say, as a quick check: the two routes are built and paid for differently. Replies are their own route: the facts (prices, dates) come from the app's own code, so ask where those facts come from before anything else."
                 },
                 {
                     "id": "ai.who",
@@ -453,6 +480,196 @@ export const capabilities = {
                         ]
                     },
                     "note": "Name the piece after where it goes (about_us, home_blurb): lower case and underscores. The client's own words, with any facts they give (when they started, where they are), go in --about, because the drafts never invent facts and leave [gaps] for the owner instead."
+                },
+                {
+                    "id": "ai.reply.purpose",
+                    "sets": "reply.purpose",
+                    "ask": "What are these replies answering?",
+                    "style": "cards",
+                    "answers": [
+                        {
+                            "label": "Quote and price requests",
+                            "value": "quote",
+                            "means": "\"How much for Dec 12, 15 pax?\": the reply gives the price and asks only for what's missing."
+                        },
+                        {
+                            "label": "Availability questions",
+                            "value": "availability",
+                            "means": "\"Available pa po ba sa Sabado?\": the reply says yes or offers other dates."
+                        },
+                        {
+                            "label": "Booking or appointment requests",
+                            "value": "booking",
+                            "means": "\"May slot po ba bukas?\": the reply lists the free times and asks which one."
+                        }
+                    ],
+                    "other": {
+                        "kind": "text",
+                        "min": 3,
+                        "max": 200,
+                        "description": "What the messages are, in a few words."
+                    },
+                    "must_ask": true,
+                    "when": {
+                        "id": "ai.route",
+                        "is": [
+                            "reply"
+                        ]
+                    },
+                    "note": "Name the guide after it (venue-quote, appointment-slots): lower case and dashes. Say that prices and dates always come from the app's own details (workbench-availability's quote() where it's a booking), never from the AI."
+                },
+                {
+                    "id": "ai.reply.facts",
+                    "sets": "reply.facts",
+                    "ask": "Here are the details a reply can use. Keep, change or add?",
+                    "style": "table",
+                    "must_ask": true,
+                    "when": {
+                        "id": "ai.route",
+                        "is": [
+                            "reply"
+                        ]
+                    },
+                    "note": "Propose one row per fact from the client's words and what the app already holds: its name, what it is, where the app gets it, and whether it is money (x-money with the currency) or a date. Only these can appear in a reply; a fact the app doesn't have can't be quoted. Then ask which details a reply may ask the customer for, most important first (ask_order); intake's missing fields are asked from that list only."
+                },
+                {
+                    "id": "ai.reply.language",
+                    "sets": "reply.language",
+                    "ask": "Which language should replies use?",
+                    "style": "cards",
+                    "answers": [
+                        {
+                            "label": "Match the message",
+                            "value": "match",
+                            "means": "English gets English, Taglish gets Taglish, Tagalog gets Tagalog. When it can't tell, it uses your fallback and asks you to check."
+                        },
+                        {
+                            "label": "Always Taglish",
+                            "value": "taglish"
+                        },
+                        {
+                            "label": "Always English",
+                            "value": "en"
+                        },
+                        {
+                            "label": "Always Tagalog",
+                            "value": "tl"
+                        }
+                    ],
+                    "when": {
+                        "id": "ai.route",
+                        "is": [
+                            "reply"
+                        ]
+                    },
+                    "note": "This is the default. Where the app has accounts (a venue each), make it each account's own setting in its portal, defaulting to this, and pass it to ai.reply as language; with match, pass the account's fallback as fallbackLanguage."
+                },
+                {
+                    "id": "ai.reply.voice",
+                    "sets": "reply.voice",
+                    "ask": "Which tone?",
+                    "style": "cards",
+                    "answers": [
+                        {
+                            "label": "Conversational",
+                            "value": "conversational",
+                            "means": "Warm and natural, like a helpful person at the front desk."
+                        },
+                        {
+                            "label": "Casual",
+                            "value": "casual",
+                            "means": "Relaxed and friendly, like chatting with a regular."
+                        },
+                        {
+                            "label": "Plain",
+                            "value": "plain",
+                            "means": "Short and clear, nothing extra."
+                        },
+                        {
+                            "label": "Formal",
+                            "value": "formal",
+                            "means": "Polite and proper, for a business that keeps a formal tone."
+                        }
+                    ],
+                    "when": {
+                        "id": "ai.route",
+                        "is": [
+                            "reply"
+                        ]
+                    }
+                },
+                {
+                    "id": "ai.reply.length",
+                    "sets": "reply.max_words",
+                    "ask": "How long can a reply be, at most?",
+                    "style": "cards",
+                    "answers": [
+                        {
+                            "label": "About 90 words",
+                            "value": 90,
+                            "means": "Room for a price or two and one question."
+                        },
+                        {
+                            "label": "About 50 words",
+                            "value": 50,
+                            "means": "A quick chat reply."
+                        },
+                        {
+                            "label": "About 150 words",
+                            "value": 150,
+                            "means": "Room for several packages or options."
+                        }
+                    ],
+                    "other": {
+                        "kind": "whole",
+                        "min": 20,
+                        "max": 300,
+                        "description": "Words, from 20 to 300."
+                    },
+                    "when": {
+                        "id": "ai.route",
+                        "is": [
+                            "reply"
+                        ]
+                    },
+                    "note": "A reply up to a quarter over passes quietly; one over twice as long is sent back to be written again, then flagged for a person to check."
+                },
+                {
+                    "id": "ai.reply.never",
+                    "sets": "reply.never",
+                    "ask": "Is there anything a reply must never say?",
+                    "style": "cards",
+                    "answers": [
+                        {
+                            "label": "The usual three",
+                            "value": "usual",
+                            "means": "Never promise a discount, confirm a booking, or ask for payment details. Code checks these as well as telling the AI."
+                        },
+                        {
+                            "label": "The usual three, and more",
+                            "value": "usual_and_more",
+                            "means": "Those three plus things of your own (type them in Other)."
+                        },
+                        {
+                            "label": "Nothing",
+                            "value": "none",
+                            "means": "No rules beyond Workbench's own content rules."
+                        }
+                    ],
+                    "other": {
+                        "kind": "list",
+                        "min": 1,
+                        "max": 10,
+                        "description": "Each thing a reply must never do, in a few words (give medical advice, mention the pool)."
+                    },
+                    "must_ask": true,
+                    "when": {
+                        "id": "ai.route",
+                        "is": [
+                            "reply"
+                        ]
+                    },
+                    "note": "Write each as a never line in the guide. Lines about payment details, discounts and confirming bookings are also checked by code; others go into the prompt only, so say so if the client's line matters a lot."
                 }
             ],
             "not_asked": [
@@ -475,6 +692,9 @@ export const capabilities = {
                 "command": "npx workbench-ai drafts text <name> --about \"<what it is for, with the client's facts>\""
             }
         },
+        "styles": {
+            "prefix": "wb-reply-"
+        },
         "delivery": {
             "choice": "built_in",
             "intro": "Writing, summarising and answering questions with Claude, with a monthly spending cap."
@@ -3579,6 +3799,369 @@ export const capabilities = {
             "intro": "Pictures made by AI from a description."
         }
     },
+    "intake": {
+        "$schema": "./schema.json",
+        "format": 1,
+        "component": "intake",
+        "title": "Message intake through the Gateway",
+        "summary": "Reads one social media message (a Messenger chat, a group post or a comment), as a screenshot, pasted text or both, into one of the project's own intake types: the type, its fields, what is missing or reads two ways, and whether a person should check it. The types are files in the project's repo, sent with every call. Workbench keeps only the call's facts, never the image or the text; the project can keep them in its own bucket.",
+        "status": "built",
+        "surfaces": {
+            "gateway": [
+                "POST /v1/intake/read"
+            ],
+            "package": [
+                "Ai.intake",
+                "defineIntakeTypes",
+                "IntakeTypes",
+                "IntakeResult"
+            ]
+        },
+        "config": [
+            {
+                "name": "WORKBENCH_GATEWAY_KEY",
+                "required": true,
+                "secret": true,
+                "environments": [
+                    "staging",
+                    "production"
+                ],
+                "description": "Project key with the ai scope, delivered as a Worker secret by gw_key_issue"
+            }
+        ],
+        "limits": [
+            {
+                "id": "intake.types-per-call",
+                "value": 20,
+                "unit": "types",
+                "per": "request",
+                "enforced_by": "gateway",
+                "refusal": "invalid_request"
+            },
+            {
+                "id": "intake.properties-per-type",
+                "value": 40,
+                "unit": "properties",
+                "per": "type",
+                "enforced_by": "gateway",
+                "refusal": "invalid_request"
+            },
+            {
+                "id": "intake.definition-size",
+                "value": 16384,
+                "unit": "bytes",
+                "per": "type",
+                "enforced_by": "gateway",
+                "refusal": "invalid_request"
+            },
+            {
+                "id": "intake.types-size",
+                "value": 65536,
+                "unit": "bytes",
+                "per": "request",
+                "enforced_by": "gateway",
+                "refusal": "invalid_request"
+            },
+            {
+                "id": "intake.text-length",
+                "value": 20000,
+                "unit": "characters",
+                "per": "request",
+                "enforced_by": "gateway",
+                "refusal": "invalid_request"
+            },
+            {
+                "id": "intake.image-size",
+                "value": 5242880,
+                "unit": "bytes",
+                "per": "request",
+                "enforced_by": "gateway",
+                "refusal": "invalid_request"
+            },
+            {
+                "id": "intake.images-per-call",
+                "value": 1,
+                "unit": "images",
+                "per": "request",
+                "enforced_by": "gateway",
+                "refusal": "invalid_request"
+            }
+        ],
+        "errors": [
+            {
+                "code": "invalid_request",
+                "http": 400,
+                "retryable": false,
+                "meaning": "No text or image, an image too large or of another kind, or a type definition that breaks the rules (the message names the type and the JSON path)"
+            },
+            {
+                "code": "budget_exceeded",
+                "http": 402,
+                "retryable": false,
+                "meaning": "The project's budget, its intake cap or the global ceiling is reached"
+            },
+            {
+                "code": "content_refused",
+                "http": 422,
+                "retryable": false,
+                "meaning": "The content rules, or Claude itself, refused the message or the reading"
+            },
+            {
+                "code": "content_check_unavailable",
+                "http": 503,
+                "retryable": true,
+                "meaning": "The content checker is down, so nothing was read"
+            },
+            {
+                "code": "upstream_error",
+                "http": 502,
+                "retryable": true,
+                "meaning": "Anthropic failed after the Gateway's retries"
+            },
+            {
+                "code": "upstream_timeout",
+                "http": 504,
+                "retryable": true,
+                "meaning": "Anthropic didn't answer in time"
+            }
+        ],
+        "rules": [
+            {
+                "id": "intake.types-from-files",
+                "kind": "must",
+                "text": "Keep each intake type as a file, workbench/intake/<name>.json, and pass intakeTypes from src/intake.generated.ts. Run npx workbench-ai intake generate after changing one, and keep npx workbench-ai intake generate --check in the project's Checks. Never write definitions inline.",
+                "enforced_by": "types",
+                "probe": "intake.read.text"
+            },
+            {
+                "id": "intake.human-check",
+                "kind": "must",
+                "text": "Act on needsHumanCheck: show the reading to a person (or keep it marked to check) before it becomes a booking, a quote or a reply. It is the Gateway's rule, not the model's score.",
+                "enforced_by": "review",
+                "probe": "intake.read.unknown"
+            },
+            {
+                "id": "intake.personal-marked",
+                "kind": "must",
+                "text": "Mark every field that holds a personal detail with x-personal (name, handle, phone, email, address, photo). An unmarked field whose name or format looks personal is refused, and personal details the type doesn't ask for are blanked in rawText.",
+                "enforced_by": "gateway",
+                "probe": "intake.read.personal-blanked"
+            },
+            {
+                "id": "intake.no-content-kept",
+                "kind": "must_not",
+                "text": "Expect Workbench to keep the image or the text: it keeps only the call's facts. To keep them, set save_input to project in workbench/intake.json and pass store: env.INTAKE_STORE.",
+                "enforced_by": "gateway",
+                "probe": "intake.read.text"
+            },
+            {
+                "id": "intake.subject-is-app-user",
+                "kind": "must_not",
+                "text": "Send the poster's name or number as subject or ref. subject is user:<id> of the app's own user; ref is the app's own record id, such as enquiry:4812.",
+                "enforced_by": "review",
+                "probe": "intake.read.text"
+            },
+            {
+                "id": "intake.bad-type-refused",
+                "kind": "must_not",
+                "text": "Send a type that breaks the format: the Gateway refuses it with invalid_request before any spend.",
+                "enforced_by": "gateway",
+                "probe": "intake.read.bad-type-refused"
+            }
+        ],
+        "examples": [
+            {
+                "id": "intake.example.read",
+                "title": "Read a pasted message or a screenshot",
+                "lang": "ts",
+                "code": "import { intakeTypes } from './intake.generated'\n\nconst r = await ai.intake({ types: intakeTypes, text, image, timeZone: country.timeZone.id, job: 'intake.quote-request', subject: `user:${user.id}`, ref: `enquiry:${enquiry.id}`, store: env.INTAKE_STORE })\nif (r.type === 'venue-quote-request') {\n  await saveEnquiry({ ...r.data, toCheck: r.needsHumanCheck, missing: r.missing })\n}",
+                "probe": "intake.read.text"
+            }
+        ],
+        "probes": [
+            {
+                "id": "intake.read.text",
+                "half": "runtime",
+                "expect": "pass",
+                "smoke": true,
+                "cost_hint_usd": 0.01,
+                "note": "One of HmPo's sample messages as text: the type, the data and no human check"
+            },
+            {
+                "id": "intake.read.unknown",
+                "half": "runtime",
+                "expect": "pass",
+                "cost_hint_usd": 0.01,
+                "note": "A thank-you review comes back unknown, with needs_human_check and unknown_type"
+            },
+            {
+                "id": "intake.read.personal-blanked",
+                "half": "runtime",
+                "expect": "pass",
+                "cost_hint_usd": 0.01,
+                "note": "A message with a phone number the type doesn't ask for: rawText shows [phone]"
+            },
+            {
+                "id": "intake.read.bad-type-refused",
+                "half": "runtime",
+                "expect": "refused_as_expected",
+                "refusal": "invalid_request",
+                "cost_hint_usd": 0,
+                "note": "A type with an unmarked contact_phone field is refused before any spend"
+            }
+        ],
+        "offer": {
+            "pattern": "settings",
+            "when": "The client gets enquiries, orders or posts as messages (Messenger, a Facebook group, comments) and wants them read into a form or a list instead of typed up by hand.",
+            "say": "I'll set this up with Workbench message intake: you paste a message or a screenshot and it fills in the details, and flags the ones a person should check. Workbench never keeps the message. Here are the details I'd pull out; tell me what to change.",
+            "answers_file": "workbench/intake/<name>.json",
+            "per": "kind of message",
+            "generator": "npx workbench-ai intake generate",
+            "answers_format": "One type per file, docs/message-intake.md §3: `{ \"format\": 1, \"name\", \"version\": 1, \"description\" (the client's words, made plain), \"not_this\", \"examples\" (1 to 5 real-looking messages with the data each should give), \"glossary\" (the trade's own shorthand), \"schema\" (the fields from intake.fields; required lists what the app can't do without), \"confidence_floor\", \"model\", \"save_input\" }`. The project's own setting is workbench/intake.json, `{ \"format\": 1, \"save_input\": \"none\" | \"project\" }`. Then run the generator and commit src/intake.generated.ts.",
+            "questions": [
+                {
+                    "id": "intake.kind",
+                    "sets": [
+                        "name",
+                        "description"
+                    ],
+                    "ask": "What kind of message do you want read?",
+                    "style": "table",
+                    "other": {
+                        "kind": "text",
+                        "min": 3,
+                        "max": 200,
+                        "description": "In the client's words, such as \"quote requests on Messenger\" or \"orders in comments under our posts\"."
+                    },
+                    "must_ask": true,
+                    "note": "Only the client knows. Name the type after it in lower case with hyphens (venue-quote-request). Ask for two or three real messages (names blanked) to use as examples."
+                },
+                {
+                    "id": "intake.fields",
+                    "sets": [
+                        "schema",
+                        "examples"
+                    ],
+                    "ask": "Here are the details I'd pull out of each message. Keep them, change some, or add or remove?",
+                    "style": "table",
+                    "other": {
+                        "kind": "list",
+                        "min": 1,
+                        "max": 40,
+                        "description": "Each detail: its name, what it is, whether the app can't do without it, and the choices if it is one of a list."
+                    },
+                    "must_ask": true,
+                    "note": "Propose from intake.kind, as a table of field, meaning, kind (text, number, date, one of a list), and needed. For an enquiry: the date, how many people, what for, budget, extras. Mark as needed only what the app can't act without; the rest are optional."
+                },
+                {
+                    "id": "intake.personal",
+                    "sets": "schema.x-personal",
+                    "ask": "Should it keep the person's name or contact details?",
+                    "style": "cards",
+                    "answers": [
+                        {
+                            "label": "No, leave them out",
+                            "value": "none",
+                            "means": "Names, numbers and handles are blanked in what it reads, and never kept."
+                        },
+                        {
+                            "label": "Their display name only",
+                            "value": "name",
+                            "means": "The name shown on the message, so the owner knows who asked."
+                        },
+                        {
+                            "label": "Name and how to reach them",
+                            "value": "contact",
+                            "means": "The name and a phone number or email when the message gives one."
+                        }
+                    ],
+                    "must_ask": true,
+                    "note": "Each kept detail becomes a field marked x-personal with its kind (name, phone, email). Say that what the app keeps is under its own privacy notice."
+                },
+                {
+                    "id": "intake.save",
+                    "sets": "save_input",
+                    "ask": "Should your app keep a copy of each message (the screenshot and its text)?",
+                    "style": "cards",
+                    "answers": [
+                        {
+                            "label": "No, read it and let it go",
+                            "value": "none",
+                            "means": "Only the filled-in details are kept, by your app."
+                        },
+                        {
+                            "label": "Yes, in your own storage",
+                            "value": "project",
+                            "means": "Your app keeps the screenshot and text in its own private bucket. Workbench never keeps it."
+                        }
+                    ],
+                    "must_ask": true,
+                    "note": "project sets save_input in workbench/intake.json and needs the INTAKE_STORE bucket bound to the app (a private R2 bucket <id>-intake per environment, in the projects account). Pass store: env.INTAKE_STORE on every call. Say who will be able to see the copies and for how long."
+                },
+                {
+                    "id": "intake.check",
+                    "sets": "app.when_unsure",
+                    "ask": "When it isn't sure, what should the app do?",
+                    "style": "cards",
+                    "answers": [
+                        {
+                            "label": "Ask you to check first",
+                            "value": "ask",
+                            "means": "The details wait for you to confirm before they are saved."
+                        },
+                        {
+                            "label": "Save it, marked to check",
+                            "value": "mark",
+                            "means": "It is saved straight away with a \"to check\" mark."
+                        },
+                        {
+                            "label": "Skip it",
+                            "value": "skip",
+                            "means": "Unsure readings aren't saved; you read the message yourself."
+                        }
+                    ],
+                    "note": "This is the app's own behaviour when needsHumanCheck is true; nothing in the type file changes."
+                },
+                {
+                    "id": "intake.model",
+                    "sets": "model",
+                    "ask": "How careful should the reading be?",
+                    "style": "cards",
+                    "answers": [
+                        {
+                            "label": "Careful",
+                            "value": "claude-default",
+                            "means": "About US$0.01 a message."
+                        },
+                        {
+                            "label": "Quick and cheap",
+                            "value": "claude-fast",
+                            "means": "Cheaper, and misses more in long or messy chats."
+                        }
+                    ],
+                    "note": "Recommend careful. Leave model out of the file for claude-default."
+                }
+            ],
+            "not_asked": [
+                {
+                    "sets": "confidence_floor",
+                    "why": "0.75 suits a start; it is tuned from real results, not asked."
+                },
+                {
+                    "sets": "glossary",
+                    "why": "Claude adds the trade's own shorthand from the client's example messages (DU for day use); the Gateway's built-in Filipino and Taglish glossary covers everyday words."
+                },
+                {
+                    "sets": "budget",
+                    "why": "Intake has its own monthly cap in the Gateway, set with Control's gw_budget_set (tool intake); offer it only when the client asks about cost."
+                }
+            ]
+        },
+        "delivery": {
+            "choice": "optional",
+            "intro": "Turns a pasted message or a screenshot of a chat into a filled-in form, so enquiries don't have to be typed up by hand."
+        }
+    },
     "pdf": {
         "$schema": "./schema.json",
         "format": 1,