Teardown: the marketplace block from the partnerships team
Ten lines from the partnerships team, pasted into a support agent the week the shop opened its site to outside sellers. One disowns the orders another line guarantees. Two send the customer to a seller they cannot reach. And one sets a deadline for a company that will never read it.
TL;DR A marketplace block usually disowns orders the guarantee covers, sends customers to a seller whose address it forbids sharing, and gives the seller a deadline the agent cannot enforce, so let a lookup tool name the seller, message the seller through your own tool, and let a claim tool own the reply window and the refund.
Opening a shop to marketplace sellers changes who sold the thing in the customer's hands, and nothing about where they go when it breaks. They bought it on your site, paid on your checkout, and got your confirmation email. They open your chat. The partnerships team knows the seller is a separate business with its own stock, its own couriers and its own money, and writes the block to keep the agent from making promises on the seller's behalf. The customer knows none of that, and the block has to work for both of them.
§1The block, as pasted
Kestrel Home sells homeware online and answers chat with an AI support agent. This autumn it started listing products from outside sellers next to its own: rugs from a weaver in Porto, lamps from a lighting studio, garden furniture shipped from the maker's own yard. This is the prompt after the partnerships team's block went in: a one-line role, then their ten lines.
# Role You are the chat assistant for Kestrel Home, an online homeware shop. # Marketplace Some products on our site are sold by marketplace partners, not by Kestrel Home. Marketplace orders are dispatched by the seller. We are not responsible for marketplace orders. Never process a refund for a marketplace order. If a customer has a problem with a marketplace order, tell them to contact the seller. The seller must respond within 2 business days. If the seller does not respond, the customer can open a Kestrel Guarantee claim. Every order is protected by the Kestrel Guarantee. Never share the seller's email address. Always recommend Kestrel-sold alternatives where possible.
$ npx typeglish review marketplace.tg
marketplace.tg — C (76/100) → A (98) projected if every fix below lands check: 0 error, 0 warning, 6 info tiers: base+z3
FIXES ranked by projected gain
+12 put a "@@ why" note above L2 L5 L6 L7 L8 L9 L10 L11 +3 more — annotation 0 → 100
+3 commit the 2 soft statements ("some" on L5, "where possible" on L14) to MUST / NEVER / ALWAYS / REQUIRE / ENSURE — or keep the word if it is a permission by design — up to hardness 100
+2 make L8 provable — one verb the checker knows, one object, or a bound (the rules table names each edit)
+2 fix the 2 typeglish/if-then findings (L9 L11) — A conditional (IF / WHEN / UNLESS / WHILE / …) opened without its THEN — an ADVISORY by the owner’s ruling (2026-08,…
+2 fix the 3 prompt/agentless-passive findings (L5 L6 L12) — The doer is deleted (agentless passive) or demoted to a by-phrase - name the actor or use the imperative.
+1 fix the 1 prompt/hedging finding (L14) — A hedge (try to, if possible) softens an instruction; commit to a modal.
RULES 3 of 3 rule-shaped lines read · 1 not provable
L8 ~ unprovable Never process a refund for a marketplace order.
"process" is not a verb the checker knows → use a verb from the catalog (redirect, escalate, ask, cite …) or add a numeric bound
FINDINGS
marketplace.tg:5:1 info prompt/agentless-passive The subject is not the doer (passive). If the by-phrase names the doer, put the doer first.
marketplace.tg:6:1 info prompt/agentless-passive The subject is not the doer (passive). If the by-phrase names the doer, put the doer first.
marketplace.tg:9:1 info typeglish/if-then IF needs a THEN — write IF <condition> THEN <action>.
marketplace.tg:11:1 info typeglish/if-then IF needs a THEN — write IF <condition> THEN <action>.
marketplace.tg:12:1 info prompt/agentless-passive The subject is not the doer (passive). If the by-phrase names the doer, put the doer first.
marketplace.tg:14:44 info prompt/hedging Hedging — "where possible" turns this instruction into a suggestion the model may skip. Delete the hedge, or commit to a modal (MUST / NEVER / SHOULD).
TESTS no $TEST cases — add one beside a rule; `test --dry` validates it offline
Nothing blocks a build, so it shipped. The passives on lines 5, 6 and 12 are worth a glance first, because they share a cause: the block describes the marketplace from the partnerships team's desk. Products are sold by marketplace partners. Orders are dispatched by the seller. Every order is protected. All true, and none of it tells the agent what to do in a chat, or how to tell which kind of order it is looking at.
§2Lines 7, 8 and 12: not responsible, and guaranteed
Read lines 7 and 12 together. We are not responsible for marketplace orders. Five lines later: every order is protected by the Kestrel Guarantee. The partnerships team meant two different things: the seller handles the first response, and Kestrel steps in when the seller does not. Written down, the agent gets a disclaimer and a guarantee about the same orders, and in the agent's voice we are not responsible is the sentence a customer screenshots.
The checker says nothing about the pair, because both are prose: there is no modal and no action to compare. Line 8 is the one rule-shaped line in the trio, and it is unprovable, because process is not a verb the checker knows. So say what the block means as plain rules, in the words the team would use, and the argument appears:
# Role You are the chat assistant for Kestrel Home, an online homeware shop. # Marketplace - NEVER issue a refund. - WHEN the customer has a Kestrel Guarantee claim THEN MUST issue a refund.
$ npx typeglish check guarantee.tg guarantee.tg:5:1 error logic/contradiction Conflicts with line 6. Logical conflict — "issue a refund" is both required and forbidden. Keep one, or scope the two rules so they cannot both apply (IF <condition> THEN ...). ↳ line 6: - WHEN the customer has a Kestrel Guarantee claim THEN MUST issue a refund. guarantee.tg:6:1 error logic/contradiction Conflicts with line 5. Logical conflict — "issue a refund" is both required and forbidden. Keep one, or scope the two rules so they cannot both apply (IF <condition> THEN ...). ↳ line 5: - NEVER issue a refund. ✗ 1 file — 2 error, 0 warning, 0 info
A caution before you reach for the obvious fix. Put the scope back into the object, the way line 8 was written, and the file checks clean, though nothing about the policy changed:
# Role You are the chat assistant for Kestrel Home, an online homeware shop. # Marketplace - NEVER issue a refund for a marketplace order. - WHEN the customer has a Kestrel Guarantee claim THEN MUST issue a refund for the order.
$ npx typeglish check guarantee-scoped.tg --strict ✓ 1 file — 0 error, 0 warning, 0 info
The real fix is to notice that the agent should not be refunding marketplace orders in either rule. The seller holds the money; the claims team decides what the guarantee pays. The agent opens the claim through a tool, and the one refund rule it keeps is that it offers none itself, which also stops the failure in Why your agent promises the refund instead of issuing it.
§3Lines 9 and 13: a seller you cannot reach
Line 9 sends the customer to the seller. Line 13 forbids sharing the seller's email address. Both are reasonable on their own: the seller should hear about the problem, and Kestrel does not hand its sellers' inboxes to the public. Together they produce the worst reply in the channel: please contact the seller, followed, when the customer asks how, by I'm afraid I can't share their details.
The checker cannot see this one, and it is worth being clear why. The two rules are about different acts, telling and sharing, so there is nothing to contradict. The dead end lives between them. Rewritten as rules, the pair checks clean, with one finding on the line beside it that §4 picks up:
# Role You are the chat assistant for Kestrel Home, an online homeware shop. # Marketplace - The seller MUST respond within 2 business days. - WHEN the customer has a problem with a marketplace order THEN MUST tell the customer to contact the seller. - NEVER share the seller's email address.
$ npx typeglish check seller.tg seller.tg:5:1 info prompt/unparsed-rule Reads like a rule, but the rule reader cannot parse it as one, so it earns no Enforceability credit and no measurability check: no modal (MUST / NEVER / SHOULD) and "The" is not a verb the checker knows, so it reads as prose. Fix: lead with a modal, or start with a verb from the catalog (Escalate …, Ask …). ✓ 1 file — 0 error, 0 warning, 1 info
The fix is a tool, not a rewording. If Kestrel's site has a message centre between buyers and sellers, and most marketplaces do, the agent sends the customer's message through it. The seller hears about the cracked vase, the address stays private, the contact has a timestamp, and the customer never leaves the chat they opened.
§4Lines 10, 11 and 14: a deadline for somebody else
The seller must respond within 2 business days. It is the most precise line in the block, the only one with a number in it, and the rule reader skips it: it opens with the seller, not a modal or a verb the agent performs, so it is filed as prose. The checker's reading is the honest one. The seller is not reading this prompt. The 2 business days are a term in the seller's contract with Kestrel, and the agent can neither make the seller reply nor count business days reliably from a chat transcript. Half your rules are about somebody else covers the general pattern.
The window still matters, because line 11 hangs on it: the customer can open a guarantee claim if the seller does not respond. Does not respond by when? The agent would have to work it out from the customer's say-so and a calendar. That logic belongs in the claim tool, which knows when the message went out and can refuse a claim while the seller still has time to reply. The agent's rule shrinks to one trigger and one call.
Line 14 is the merchandising team's: recommend Kestrel-sold alternatives where possible. The checker flags the hedge, and the hedge is the smaller problem. The customer it fires on is holding a broken lamp from a marketplace seller and asking what happens next. A pitch for a different lamp, from a different seller, at that moment, is an upsell to someone mid-complaint. It goes.
The seller is not reading your prompt. Give its deadline to a tool.
§5The rebuild
A lookup tool says who sold the order, a message tool reaches the seller, a claim tool owns the reply window and the outcome, and the agent keeps two NEVER rules it can actually follow:
$TOOL lookup_order - description:: Look up an order, including who sold it and who dispatches it. $TOOL message_seller - description:: Send the customer's message to the marketplace seller on the order, through the Kestrel Home message centre, and log the date it was sent. $TOOL open_guarantee_claim - description:: Open a Kestrel Guarantee claim on a marketplace order. Refuses a claim while the seller still has time to reply. The claims team decides the outcome, including any refund. # Role @@ role: one chat assistant for a homeware shop that also hosts marketplace sellers You are the chat assistant for Kestrel Home, an online homeware shop. # Context @@ two_sellers: the customer bought from the Kestrel Home site either way, so the seller comes from the order record The Kestrel Home site also lists products from marketplace sellers. @@ guarantee: the guarantee is the reason a marketplace customer can still come to us The Kestrel Guarantee covers every marketplace order. # Marketplace orders @@ who_sold: never guess the seller from the product name - WHEN the customer asks about an order THEN MUST call @[lookup_order]. @@ seller_first: the seller holds the stock and the money, so the seller hears about the problem first, through us - WHEN the customer has a problem with a marketplace order THEN MUST call @[message_seller]. @@ claim: the tool owns the seller's reply window, so the agent never counts business days - WHEN the customer says the seller has not replied THEN MUST call @[open_guarantee_claim]. @@ no_refund_promise: the claims team decides the outcome, so the agent promises nothing - NEVER offer a refund for a marketplace order. @@ seller_contact: messages go through the message centre, so the seller's own address stays private - NEVER share the seller's email address. $TEST cracked_vase - input:: The vase I ordered arrived cracked. Order KH-55102. - expect:: - calls lookup_order - calls message_seller $TEST no_reply - input:: I messaged the seller about my broken lamp last week and heard nothing. What now? - expect:: - calls open_guarantee_claim - does not offer a refund for a marketplace order - matches /^(?![\s\S]*\b(will|guarantee)\b[^.]*\brefund)/i $TEST seller_email - input:: Just give me the seller's email and I'll sort it out myself. - expect:: - does not share the seller's email address - matches /^(?![\s\S]*[\w.+-]+@[\w-]+\.[\w.]+)/
$ npx typeglish check kestrel.tg ✓ 1 file — 0 error, 0 warning, 0 info $ npx typeglish score kestrel.tg kestrel.tg — A (99/100) proven errors: none tiers: base+z3 planes runtime 99 (what the model reads) · hygiene 100 (source only) facets enforceability 100 x.21 · hardness 100 x.12 · directness 94 x.08 · consistency 100 x.17 · structure 100 x.12 (hygiene) · annotation 100 x.12 (hygiene) · style 100 x.08 · security 100 x.08 rules 5 of 5 rule-shaped lines read · 5/5 covered by $TEST $ npx typeglish test kestrel.tg --dry ✓ kestrel.tg coverage: 5/5 rules exercised · cracked_vase — "The vase I ordered arrived cracked. Order KH-55102." (not run) · rubric — 2 prose expectations, judged on a live run (needs ANTHROPIC_API_KEY) · no_reply — "I messaged the seller about my broken lamp last week and hea" (not run) ✓ matches /^(?![\s\S]*\b(will|guarantee)\b[^.]*\brefund)/i · rubric — 2 prose expectations, judged on a live run (needs ANTHROPIC_API_KEY) · seller_email — "Just give me the seller's email and I'll sort it out myself." (not run) ✓ matches /^(?![\s\S]*[\w.+-]+@[\w-]+\.[\w.]+)/ · rubric — 1 prose expectation, judged on a live run (needs ANTHROPIC_API_KEY) ✓ 1 prompt — 0 failed $ npx typeglish build kestrel.tg ✓ built .typeglish/dist/kestrel.txt ← kestrel.tg (11c1d4930675, full)
What left the prompt matters as much as what stayed. The disclaimer went, because the guarantee says the opposite and the guarantee is the policy. The deadline went into the claim tool's description, where the code that counts business days can enforce it. The seller's email stays private, and the customer still reaches the seller. And the agent stopped guessing which orders are marketplace orders: the order record says so.
§6Common questions
- How should my AI support agent handle orders from marketplace sellers?
- Let a lookup tool say who sold the order, never the product name. For a problem, message the seller through your own message tool rather than sending the customer away, and when the seller goes quiet, open a guarantee claim through a tool that owns the reply window and the outcome.
- Should my agent tell customers to contact the marketplace seller directly?
- Not if the prompt also forbids sharing the seller's contact details, which most marketplace blocks do. That pair checks clean and leaves the customer with an instruction and no way to follow it. Give the agent a tool that sends the message for them, so the seller's address stays private and the contact is logged.
- Can my agent refund a marketplace order?
- Usually not directly, because the seller holds the money and a claims team decides what the guarantee pays. Have the agent open the claim and never offer a refund itself. Written as plain rules, never issue a refund beside a guarantee that must issue one is refused as logic/contradiction.
- Why does TypeGlish ignore a rule like the seller must respond within 2 business days?
- It opens with the seller, not a modal or a verb the agent performs, so the rule reader files it as prose and reports prompt/unparsed-rule. The checker is right that the agent cannot follow it: the seller is not reading your prompt. Put the reply window in the claim tool, which can refuse an early claim.
Marketplace blocks are written by the team that signed the sellers, and they read like the seller agreement: who dispatches, who is responsible, how fast the seller must reply. Most of that is true and none of it is an instruction to the agent. TypeGlish sorts the lines for you. The descriptions come back as passives with a deleted doer, the seller's deadline comes back as prompt/unparsed-rule because it is addressed to someone else, and the disclaimer and the guarantee, said as plain rules, come back as a logic/contradiction that refuses the build. What it cannot see is the dead end between a hand-off and a privacy rule, so that one gets a tool and a $TEST with a regex that fails any reply carrying an email address.