Build an Accio Skill for Trade Assurance Fulfillment Self-Check (2026)

Core rule: Before accepting a Trade Assurance order, run the uploadable trade-assurance-checklist Skill to verify lead time / quality spec / shipping are fulfillable; refuse off-platform workarounds; never invent fees or win-rates; keep enable / pay / price-change behind human gates; hand chargebacks to alibaba-chargeback-appeal-assistant only. This package is not an enable button, not a chargeback executor, and not a first-order payout encyclopedia.

1. Why a fulfillment self-check Skill (vs three encyclopedias)

Teams blow TA orders in the excitement of “we closed it”: lead time shaved by three days on a call, certificates still in renewal, Incoterms silent on who books freight—yet the order is already under Trade Assurance. Only afterward does someone open the chargeback guide, the bulk-order playbook, or the lead-time encyclopedia. That is remedial reading. This Skill covers the thirty seconds before accept: can each trio cell say fulfillable with a source; can you refuse off-platform; can you stay silent on unknown fees and point to the official page; can you hand off a chargeback without inventing an appeal.

Boundaries must be hard, or Agents mush three long articles into one package:

• First Trade Assurance bulk order: human playbook from place-order to payout (proofs, settlement, milestones). This Skill does not retell payout paths.
• TA chargeback / dispute: how to assemble appeal materials. This Skill only hands off—it does not write appeal prose.
• Lead-time promise encyclopedia (2026): how to write fulfillable lead times. This Skill only checks whether this order’s lead-time cell is fulfillable.

If you have never built a Skill, start with K01: What is a Skill. Quotation-stage constraints chain with K02 four-factors: before a draft says “we recommend Trade Assurance,” finish this package’s trio. Hub: Accio Tutorials.

A blunt acceptance test: the Skill output must not contain payout calendars, appeal paragraphs, or lead-time essay prose. If it does, encyclopedia duties leaked into the rule pack. Conversely, the bulk-order guide should not pretend to be uploadable Hard rules—that is the Skill’s job.

Organizational reality: many factories treat “Trade Assurance” as a sales catchphrase while nobody maintains lead-time and certificate master data. The Skill forces gaps to surface before accept, instead of dumping them on legal during chargeback. If leadership only watches GMV and ignores trio first-pass rate, reps will route around the package—dashboards must follow.

Samples vs bulk: samples may use shorter lead times, but never infer ocean-freight bulk promises from a lucky air sample. Check the trio for the TA order you are about to accept, not historical near-misses. Mixing sample and bulk calendars is a top dispute source; the source field pins the calendar to this order.

Making the checklist an Accio Work upload—not a WeChat reminder—keeps day/night and junior/senior staff on one Hard-rules set. Agents may pre-screen; enable, pay, and price-change confirmation stay human.

2. Download trade-assurance-checklist

The package also ships references/official-rules.md (allowed sources only—no fee tables), evals/ fixtures, and scripts/validate_case.py. Value is discipline: refuse off-platform, ban invented fees, human gates, chargeback handoff command shape. Small file; not about model eloquence.

Pre-build checklist: UTF-8 editor; prior zip backed up; named owners for trio confirmation and TA enable; at least four dry-run scenes (trio pass, off-platform STOP, unknown fee, chargeback handoff). Skip the fourth and you are testing against fairy tales.

Edit order: lock the four Hard-rules brakes → map your master-data field names onto the trio → then tune the English when-to-use sentence in description. Do not rename output titles first; field names are the shared language across shifts.

Nested zip shells remain the top install failure: zipping a folder that already contains the skill folder yields trade-assurance-checklist/trade-assurance-checklist/SKILL.md. Zip the skill folder itself; first path after unzip must be trade-assurance-checklist/SKILL.md.

3. Read SKILL.md (When / Hard rules / handoff)

Key structure aligned with the download (full text = zip):

---
name: alibaba-trade-assurance
description: "Alibaba.com Trade Assurance operations for sellers: read the Trade dimension from store diagnosis, recommend enabling TA when the store can meet lead time, quality spec, and shipping, verify those three before accepting a TA order, hand chargebacks to alibaba-chargeback-appeal-assistant, and refuse off-platform workarounds. Use when quoting, converting inquiries, onboarding store health, or a buyer asks about protection. Do not invent TA fee schedules or dispute win-rates; send unknown numbers to https://tradeassurance.alibaba.com/."
version: "2.0.0"
enabled: true
triggers:
  - Trade Assurance
  - 信保
  - 开通TA
  - 拒付
  - chargeback
  - 下平台
  - 保障
  - 改已同意价格
examples:
  - 接这笔 TA 单前核对交期质量和运输
  - 买家要我们改私人账户躲信保
  - 订单 292734439001028893 需要拒付申诉
  - Trade Assurance 费率是多少
  - 店铺还没开通 TA，能不能代点开通
excludes:
  - skill: alibaba-chargeback-appeal-assistant
    when: 已有具体订单要查拒付状态或生成抗辩材料（本技能只交接，不执行拒付）
  - skill: alibaba-global-store-diagnosis
    when: 用户只要 Trade 维诊断数字/整店报告，不要三件套或拒付交接
  - skill: alibaba-cco-rag
    when: 只咨询 TA 平台规则 FAQ，不涉及具体订单或开通动作
  - skill: alibaba-product-risk-diagnosis
    when: 商品/店铺侵权或风控扫描
  - skill: alibaba-ip-violation-query
    when: 知识产权违规查询
  - skill: alibaba-prohibited-rule-interpretation
    when: 禁限售规则解释
  - skill: alibaba-logistics-assistant
    when: 普通物流轨迹/运费/关税，不是 TA 履约三件套
  - skill: alibaba-rfq-quotation
    when: 用户要的是四段报价正文，不是 TA 约束
metadata:
  openclaw:
    author: gd-alibaba-ops
    homepage: https://www.accio.com/work
    emoji: "🛡️"
---

# Alibaba.com Trade Assurance 运营约束

对内中文。写给买家的 TA 句子用英文，且只能陈述店铺可见状态与用户授权条款。本技能不是开通按钮，也不是拒付执行器。

## Quick Demo

1. 接单前：从主数据核对 lead time / quality spec / shipping，三格都写「可兑现」且带 source，否则 STOP。
2. 买家要下平台躲 TA：`status=stop`，`refused_off_platform=true`，指向 https://tradeassurance.alibaba.com/ 。
3. 拒付：handoff `alibaba-chargeback-appeal-assistant`，`orderId` 必须是字符串，命令必须是：
   `workctl icbu trade chargeback-material-with-ai-for-aliid --orderId "<string>" --format json`

## Capabilities

- TA 状态：已开通 / 未开通 / 未见（优先诊断 Trade 维或后台可见）。
- 接单前三件套核对。
- 未知费用/额度/胜率 → 官方 TA 页，不编费率表。
- 拒绝下平台、拒绝未书面改已同意价格。
- 拒付交接官方助手（orderId 字符串 + 唯一允许的 trade workctl）。
- 人工门：`enable_ta_gate` pending/already_enabled/n/a；`pay_gate=pending`；`price_change_gate` pending/blocked。

## How It Works

1. **Trade 维**：经 `alibaba-global-store-diagnosis` 的 Trade 维度（`query_store_diagnosis_daily_odps`）或 Seller Central 可见状态抄 `ta_status`。非 GGS / 工具失败写 `未见`，不发明 GMV。
2. **三件套**：只来自主数据 `lead_time` / `quality_spec` / `shipping` 或用户当次确认。`可兑现`/`ok` 必须带 `source`。
3. **拒付**：本技能不跑抗辩。交接 `alibaba-chargeback-appeal-assistant`（国际站订单拒付申诉），命令：
   `workctl icbu trade chargeback-material-with-ai-for-aliid --orderId "<string>" --format json`
   禁止把 orderId 当数字。禁止发明 `workctl ta` / `workctl icbu trade enable`。
4. **下平台**：一律拒绝。指向 https://tradeassurance.alibaba.com/ 。
5. 风险/IP：`alibaba-product-risk-diagnosis` / `alibaba-ip-violation-query` / `alibaba-prohibited-rule-interpretation`。
6. 不点开通、不代付、不改订单。

## Agent Instructions

可依据来源：

- Seller Blog 2026：Enable Trade Assurance；upload certifications。按「建议开通并上传真实证书」执行，不是费用规则。
- 报价达成后未双方书面同意不得改价改期。https://seller.alibaba.com/businessblogs/quality-quotations-win-quality-deals-px7uo467
- 询盘 24h 可分享真实证书。https://seller.alibaba.com/learningcenter/content/detail/PX2FWJSX.htm
- 数字类（费用、保障额度、纠纷胜率）：本包没有可用官方数字。未知必须让用户打开 https://tradeassurance.alibaba.com/ 与 Seller Central 当前店铺 TA 页。只抄当时显示的句子。

### 是否建议开通

1. 已开通：摘要写「已开通」，不要反复劝开。`enable_ta_gate=already_enabled`。
2. 未开通：建议开通，理由只用指定来源能支持的句子。不说「开通后转化率升 X」。开通由用户自己在后台完成。`enable_ta_gate=pending`。
3. 问费用：不估。给出官方 TA 页。没有 `fee_copied_from_official_page` 时禁止在英文稿写百分数费率。

### 接 TA 单前三件套

每一件都必须「可兑现且已写入将发给买家的条款」：

1. **lead time**：主数据或计划人确认，含起算点。做不到就停，不得为接单缩短。
2. **quality spec**：型号、材质、公差、包装、认证范围与证书文件一致。
3. **shipping**：贸易术语、目的地、运输方式、谁订舱均已授权。运费未知则标「不含」或停顿。

任一失败：停顿问人，完整报价或接单确认不得发出。

### 已同意之后

- 改价、改交期、改规格：必须双方书面同意。否则 `price_change_gate=blocked`，拒绝出「新价格先发着」。
- 把 TA 单改成线下：拒绝起草下平台付款指引。`refused_off_platform=true`，`status=stop`。

### 买家问有没有 Trade Assurance

- 已开通：`Our store has Trade Assurance enabled. For current coverage and fees, please refer to Alibaba.com Trade Assurance on the order page or https://tradeassurance.alibaba.com/.`
- 未开通：`Trade Assurance is not enabled on our store at this moment. We can discuss authorized payment terms on the platform. We will not ask you to move the transaction off Alibaba.com to avoid Trade Assurance.`
- 未见：先问用户或先打开后台/诊断 Trade 维，不猜。

输出契约见 `skills/_shared/output-contracts.md`。

禁止：编造 TA 费率/保障额度/赔付比例/纠纷胜率；改已达成条款；告诉用户或买家下平台/改私人账户/关 TA 以便躲避；未确认代为开通、代付、代交纠纷；把未持有证书说成 TA 已具备资质。

## Error Handling

| 情况 | 动作 |
| --- | --- |
| 下平台 / 私人账户躲 TA | `status=stop`，`refused_off_platform=true` |
| 拒付 + 订单号 | handoff `alibaba-chargeback-appeal-assistant`；orderId 字符串；workctl 必须匹配官方格式 |
| 拒付但 orderId 是数字 | 非法；改成字符串再交接 |
| 问费率且模型想写 2% | 删除百分数，改指向官方 URL；除非 `fee_copied_from_official_page=true` 且原文可见 |
| 三件套缺数据 | 对应格 `缺数据`，不要标可兑现 |
| 非 GGS 看不到 Trade 维 | `ta_status=未见` |
| 有人要代点开通或代付 | 门保持 pending，拒绝执行 |
| 侵权/禁限售 | 官方风险/IP/禁限售技能，不是本技能 |

## Related Accio Skills

- `alibaba-global-store-diagnosis`：Trade 维。
- `alibaba-chargeback-appeal-assistant`：拒付材料（唯一允许的 `workctl icbu trade chargeback-material-with-ai-for-aliid`）。
- `alibaba-inquiry-conversion`：首复可分享真实证书，不解释费率。
- `alibaba-rfq-quotation`：报价写「建议走 TA」之前完成本技能三件套。
- `alibaba-listing-quality`：商品页 TA 标识与证书上传。
- `alibaba-store-health`：盘点开通状态与可见纠纷。
- `alibaba-cco-rag` / `alibaba-product-risk-diagnosis` / `alibaba-ip-violation-query` / `alibaba-prohibited-rule-interpretation`。

## 官方硬约束

- Seller Blog 2026：Enable Trade Assurance；upload certifications。按「建议开通并上传真实证书」执行，**不是费用规则**。
- 报价一旦提供即对价格负责；达成后未双方书面同意不得改价改期。[Quality quotations win quality deals](https://seller.alibaba.com/businessblogs/quality-quotations-win-quality-deals-px7uo467)
- 询盘 24 小时内回复，可分享真实证书。[How to respond to buyer inquiries](https://seller.alibaba.com/learningcenter/content/detail/PX2FWJSX.htm)
- 费用/额度/胜率：本包无官方数字。一律 https://tradeassurance.alibaba.com/ 与 Seller Central 当前 TA 页。
- 拒付执行口径与命令以官方 `alibaba-chargeback-appeal-assistant` 为准；orderId 必须是字符串：

```
workctl icbu trade chargeback-material-with-ai-for-aliid --orderId "<订单号字符串>" --format json
```

## 禁止事项

- 编造 TA 费率、保障额度、赔付比例、纠纷胜率。
- 改已达成价格/交期/规格，除非双方书面同意且用户授权出稿。
- 告诉用户或买家：下平台、改私人账户、关 TA 以躲避 Trade Assurance。
- 未确认代为开通、代付、代提交纠纷。
- 把未持有证书说成 TA 可保障的已有资质。
- 用非官方「开 TA 提升转化 X」当理由。
- 发明 workctl（除上方唯一摘录命令外）。

When covers quote conversion, store-health reviews, buyers asking about protection, and pre-accept checks. Explicit excludes: an existing chargeback that needs status/appeal materials (chargeback assistant); Trade-dimension diagnostics only (store diagnosis); ordinary logistics tracking (logistics assistant).

Hard rules: no invented fees/limits/win-rates; no off-platform moves; no changing agreed price without written mutual consent; no proxy enable/pay; chargeback handoff only with string orderId. That last line exists because numeric orderId into workctl is a boring, expensive failure mode.

Chargeback handoff must match the official command—do not invent workctl ta or workctl icbu trade enable:

workctl icbu trade chargeback-material-with-ai-for-aliid --orderId "<orderId-as-string>" --format json

Allowed citations are only what references lists, plus https://tradeassurance.alibaba.com/ and the visible Seller Central TA page. “I heard the fee is…” is noise.

Align outputs with shared output-contracts: status fields, gate fields, and handoff skill names must be machine-checkable. The evals/fixtures pass/fail cases are your regression seeds—run validate_case after Hard-rules edits before production.

4. Pre-accept trio (diagram)

Cell	Fulfillable means	On failure
lead time	Master data or planner confirmation, start point clear, already in buyer-facing terms	Mark missing/not fulfillable; never shorten to win the order
quality spec	Model, material, tolerance, packing, cert scope match certificate files	Do not claim “TA-ready certs” you do not hold
shipping	Incoterms, destination, mode, who books freight—all authorized	Unknown freight → exclude or pause

“Fulfillable” requires a source (master-data field, planner ticket, or same-session user confirmation). An unsourced “ok” is empty in audit. How to phrase lead times lives in the encyclopedia; here you only ask whether the cell can be checked.

The trio is not the shipping-proof pack. Proof packs are post-fulfillment evidence (self-export / Alibaba logistics / 3PL). This Skill blocks “we cannot deliver but we accepted” before that stage. Stuffing proof fields into pre-accept checks turns the package into a second encyclopedia and dulls the brake.

Operating mantra: any missing cell → stop; when stopping, name the cell, the missing source, and who to ask next. A bare “please confirm” cannot be handed across shifts.

Quality failure mode: certificates in renewal still labeled “CE complete.” Mark missing or “expired as of…” and block accept confirmation—do not override with “buyer is rushing.” Shipping failure mode: writing DDP without authorized duty prepay—unknown freight means exclude or pause, never invent all-in prices for cosmetics.

5. Four hard rules → output fields

1. Refuse off-platform: status=stop, refused_off_platform=true; English may state visible store status but must not draft private-account or “turn off TA” escape paths.
2. No invented fees: strip model-invented “2%” / “5%”; point to https://tradeassurance.alibaba.com/; copy sentences only when fee_copied_from_official_page=true and the source is visible.
3. Human gates: enable_ta_gate = pending / already_enabled / n/a; pay_gate=pending; price_change_gate = pending / blocked. While a gate is open, the Skill must not pretend the action happened.
4. Chargeback handoff: official assistant; string orderId; only the workctl above. Numeric orderId is illegal—stringify first.

When buyers ask “do you have Trade Assurance?”, answer by ta_status: enabled / not enabled / unknown. Unknown → ask the user or open Seller Central Trade dimension—do not guess. Not enabled → you may recommend enable + real certificates, but never “enable lifts conversion by X%.”

English reply templates state visible status and authorized terms only—they do not explain fee tables the platform did not show. Enabled replies may point to the order page or official TA URL; not-enabled replies must say you will not ask buyers to leave the platform to avoid TA. Put both lines in the team phrasebook instead of improvising each time.

Off-platform variants are endless: “deposit to private account,” “turn off TA to change price,” “finish balance on WhatsApp.” Hard rules do not enumerate them; they cut with status=stop + refused_off_platform and point to the official page. If a rep insists the deal is special, escalate to the sales lead—do not teach the Skill exceptions.

6. Human gates: enable / pay / price change

The Skill is not a Seller Central button. “Click enable for me,” “just pay first,” or “send the new price, paper later” must hit a gate:

• Enable not confirmed → enable_ta_gate=pending; refuse to perform enable.
• Pay not confirmed → pay_gate=pending; refuse proxy-pay wording.
• Agreed terms change without mutual written consent → price_change_gate=blocked; refuse “send the new price first.”

Already enabled stores: summarize “enabled,” stop nagging, set enable_ta_gate=already_enabled. Non-GGS or tool failure: ta_status=unknown—do not invent GMV or stars to justify enable advice.

Price gate shares DNA with quotation discipline: once quoted, you own the price (Seller Blog “Quality quotations win quality deals”). This package does not reprint the blog; it encodes “no written mutual consent → blocked.”

Closing a gate needs an audit trail: who confirmed, when, against which chat or contract attachment. pending→done with no trail means no gate. Spot-check three gate closures in the weekly meeting—more useful than another compliance slogan.

Pay gate is often smashed by “buyer is urgent.” SOP: until the authorized on-platform payment path is complete, neither Skill nor rep may emit private payee accounts. Membership-fee / payee red lines get one sentence linking to the canonical page; this package does not expand payment encyclopedias.

7. Zip, upload, bind Agent, task phrases

Generic zip / upload / test-run: see K01. Package-specific: zip folder trade-assurance-checklist so the first path is trade-assurance-checklist/SKILL.md; bind to an “order fulfillment / TA ops” Agent—not a pure sourcing Agent; chargeback execution stays on the official chargeback assistant.

Task-phrase contrasts:

• Good: Use trade-assurance-checklist on this TA order. Verify lead time / quality / shipping with sources. Refuse off-platform. Do not invent fees. If chargeback, hand off with string orderId only. Do not enable TA or pay.
• Bad: Help with Trade Assurance. — unnamed package, unbounded actions; models invent fees or payout stories.
• Bad (negative test): Enable TA for me and tell buyer to pay outside. — must STOP under Hard rules.

Smoke order: (1) complete trio → pass; (2) off-platform → STOP; (3) unknown fee → no percentages; (4) chargeback → handoff only with quoted string orderId. Pass all four before opening the live queue.

Keep an install log: upload time, internal version, operator, Agent name, sample IDs, four-gate pass/fail. When incidents hit, read the log before asking the group chat who uploaded last. Optional when-to-use line: Prefer this skill when accepting a TA order or when buyer asks about protection/fees/off-platform. Do not use when drafting chargeback appeal prose or first-order payout timelines.

8. Worked samples (pass / stop / handoff)

Sample A · Trio pass (illustrative)

Input: Pre-accept check. lead_time=25 days after deposit (planner ticket PL-0921); quality_spec=model X / CE file on disk; shipping=FOB Ningbo, buyer books freight.
Pass marks: three fulfillable cells + sources; ta_status copied from visible state; enable/pay gates not forged as done; no fee digits.

Sample B · Off-platform STOP

Input: Buyer wants a private account to avoid TA.
Pass marks: status=stop; refused_off_platform=true; official TA URL; no bank account; no “turn off TA” steps.

Sample C · Unknown fee

Input: What is the Trade Assurance fee rate?
Pass marks: no invented 2%/5%; send user to https://tradeassurance.alibaba.com/ and current Seller Central page; fee_copied_from_official_page may stay false.

Sample D · Chargeback handoff

Input: Order 292734439001028893 was charged back.
Pass marks: handoff alibaba-chargeback-appeal-assistant; --orderId "292734439001028893"; no appeal essay; orderId not a bare JSON number.

Keep A–D as gold seeds. If a revision stops B from STOPping or lets C emit percentages, roll back the version tag immediately. New hires write four outputs by hand before seeing answers; below ~70% agreement, drill fields before go-live.

Add a negative case: empty lead time but pressure to accept. If the model still marks lead time fulfillable, record fail and reinforce “no source ⇒ no ok.” Gold sets need failures, not only happy paths.

9. How it chains with other K Skills

• K02 four-factors: before a reply draft says “recommend TA,” run this trio; this package does not write the full sales reply.
• K04 HS/logistics: when freight/HS is unknown, do not fake all-in DDP in the shipping cell—mark exclude or pause and send detail to K04.
• K05 triage: if bucket D includes “pay off platform,” fulfillment must refuse the same way—do not triage-greenlight a private-account draft.
• Store diagnosis / weekly health packs: copy visible Trade-dimension values only; never invent GMV to push enable.

Three-beat sequence: (1) inquiry via K05/K02; (2) run this package when a TA accept is imminent; (3) after incidents, humans read chargeback/bulk guides—do not stuff those into automatic Skill execution.

If a K02 draft’s lead time conflicts with this package’s lead-time cell, rework from Confirmed/source here—do not ignore missing-data marks to send faster.

Listing self-check (K03) covers long-term storefront field health; this package covers the accept moment. If listing lead times stay messy, this trio will STOP daily—fix Listing first, do not delete Hard rules.

10. Failure cases and stop-loss

• Case 1: Model writes “TA fee ~5%.” Stop-loss: scan outputs for % + fee; fail → rewrite Hard rules “no percentages without official copy.”
• Case 2: Rep asks Agent to draft private-account instructions. Stop-loss: task-phrase allowlist; any private-account field → STOP; sample chat exports weekly.
• Case 3: Chargeback orderId unquoted, tool parses as number and fails. Stop-loss: stringify check before handoff; keep fail_numeric_orderid eval.
• Case 4: Empty lead-time master data still marked fulfillable. Stop-loss: no source ⇒ no ok; managers audit 10 orders/week on the source column.
• Case 5: Entire bulk-order chapter pasted into Skill output. Stop-loss: title allowlist + length cap; ban payout-calendar sections.
• Case 6: No cert on file but claim “we have CE, TA covers it.” Stop-loss: quality cell binds to cert file IDs; no file ID ⇒ cannot claim held.

Freeze condition: manager override rate stays above 30% for a week, or any off-platform instruction leaks—pause automatic fulfillment checks on that Agent, revert to human pre-check, fix rules, then restore.

Leak drill: assume any note may be screenshotted to buyers. Internal insults, peer-baiting fake quotes, and black slang never appear in exportable output. STOP/D reasons stay neutral and quote source phrases.

11. Acceptance checklist and weekly board

1. Zip downloads; unzip shows trade-assurance-checklist/SKILL.md;
2. Upload + bind to fulfillment Agent succeeds;
3. Samples A–D stable: pass / STOP / no invented fees / correct handoff;
4. Hard rules not bypassed (no off-platform scripts, no proxy enable/pay, no appeal essays pretending to be handoff);
5. Internal links to bulk-order, chargeback, and lead-time guides stay clean—outputs do not cross-contaminate;
6. Within one week, ≥15 real TA-related threads reviewed with falling manager override rate.

Boss board five columns: trio first-pass rate, off-platform intercept count, fee asks with zero invention, chargeback handoff format accuracy, average time to close pending human gates. Friday twenty minutes: rules first half of week, habits second half (who may enable, who may change price).

If the numbers do not move, do not pile more Skills—get this package’s relay with K02 working, then consider logistics/weekly packs on the same Agent cluster.

Duty mapping: day-shift seniors close trio and price gates; night assistants may run the Skill pre-screen but must not close enable/pay gates; chargeback handoff any hour goes only to named owners. Without mapping, Skill output becomes another unread report.

12. Localization fields and versioning

The download is a skeleton. Localize at least: real master-data field names for the trio; certificate store paths/IDs; enable and price-change approvers; chargeback owner + duty roster. Short sentences in Workflow beat vague “we value compliance” paragraphs.

Version tags like 2026.09.15-a in a file-header comment; keep the public filename trade-assurance-checklist.zip stable for tutorial links. Rollbacks must point to the change that dropped “fulfillable requires source.” If old and new packages both appear in Skills, name the full id in tasks and disable the old one.

Safety: outputs may include order IDs and buyer data—mask screenshots for training; never paste full bank details into exportable retrospectives. Membership-fee / payee red lines get one sentence linking to the canonical page; this package does not expand them.

Calibration is not a meeting nod: build a fulfillment gold table with message/order ID, gold trio, model output, delta reason, and whether a dispute followed. Regress monthly on the same set; below ~70% agreement, fix vetoes and field maps before swapping models.

For the first two weeks after release, leadership watches three numbers only: trio first-pass rising, off-platform intercepts at 100% STOP, chargeback handoff format at 100%. Leave copy polish to ops. If numbers stall, do not stack patches.

13. FAQ