選單

企業工作流程

企業工作,成果可檢查。

取得業務紀錄的授權,或委託製作以這些紀錄為基礎的 AI 代理任務。將電子郵件、聊天與系統狀態連結到具體的交付成果:一份修訂後的報價、一筆更新後的紀錄,以及與兩者一致的回覆。

洽談工作流程試行專案 查看工作流程範例

查看記錄的示範

訂單修改、機台停機、報價待修正。

客戶修改了訂單,生產端更換了機台。任務是讓兩者與排程及成本計算規則一致,然後更新報價、稽核歷程與給客戶的回覆。

虛構的業務資料。選擇一個預先準備的答案,即可查看其記錄的驗證器結果。本頁不會執行 AI 代理,也不會執行驗證器;金額已遮蔽。

選擇一個答案
起始工作區・mfg-rfq-001 重設 3366510ba57c…
chat/production.json  #production · 3 messages

tooling_lead  14 Nov 16:02
BM-07 is down for a screw and barrel replacement, back 10 Dec at the earliest. Run the JC20 mould on BM-03 until then.

planner_1  14 Nov 16:05
Noted. JC20 cycle on BM-03 runs 18% longer than on BM-07, same single cavity. BM-03 is booked, check machine_schedule before promising dates.

qc_lead  16 Nov 08:15
Reminder: drop test on the blue 10 L pails is at 2pm.
inbox/001.eml  09 Nov 10:14 · from procurement@selatbiru.example
RFQ - 20 L jerrican
Please quote for 50,000 pcs of your 20 L HDPE jerrican (JC20), natural colour. Delivery to Port Klang. Procurement, Selat Biru Agrochem
inbox/002.eml  13 Nov 15:31 · from procurement@selatbiru.example
Re: RFQ - 20 L jerrican (revised)
Revision to our RFQ: we now need the jerricans in BLUE, and the first order will be 12,000 pcs, not 50,000. We need delivery within 21 days of your quotation date. Please re-quote. Procurement, Selat Biru Agrochem
inbox/003.eml  16 Nov 08:40 · from sales.director@tembagaridge.example
Q-2611 today please
Please get Q-2611 out to Selat Biru today. Follow SOP-Q-07 and check with production first.
inbox/000.eml  16 Nov 09:05 · from procurement@selatbiru.example
Re: RFQ - 20 L jerrican (revised) - quotation?
Good morning. We have not yet received your revised quotation. Our planning meeting is this afternoon, so please send it today. Procurement, Selat Biru Agrochem
docs/SOP-Q-07.md  quoting & escalation SOP

# SOP-Q-07  Quotation costing and disposition (blow moulding)

1. Governing request. The latest written customer amendment governs quantity, colour and delivery.
2. Machine. Quote on the machine production has confirmed for the job. Never quote on a machine
   whose status is DOWN.
3. Unit cost in RM per piece:
   - material mass = part mass x (1 + 3% scrap)
   - coloured parts: masterbatch replaces resin at the dosing % in the masterbatch table
   - material cost = resin kg x resin price + masterbatch kg x masterbatch price
   - resin price = the row with the latest effective_date on or before the quotation date
   - machine cost = cycle seconds / cavities / 3600 x machine rate / hr
   - set-up = [amount] per job / quantity
   - unit cost = material + machine + set-up
4. Price. unit price = unit cost / (1 - 22%), rounded to 2 decimals. Never quote below an 18% margin.
5. MOQ for JC20 is 10,000 pcs. Below MOQ: stage REJECTED_MOQ and no price is sent.
6. Delivery.
   - production days = quantity x cycle seconds / cavities / (3600 x machine hours per day x 85% OEE),
     rounded up
   - first free day = the day after booked_until in machine_schedule
   - earliest delivery = first free day + production days + 3 days QC and dispatch
7. Disposition, in the quotes table:
   - delivery can be met: stage QUOTED, owner stays with the sales executive
   - delivery cannot be met: still price the job, stage ESCALATED_LEADTIME, owner = the sales manager.
     The reply states the price and the earliest delivery date and does not promise the requested date.
8. Outputs. Update the quotes row (qty, unit_price_rm, stage, owner). Record every change you make to a
   quotes field as a row in crm_history (quote_id, ts on the quotation date, actor, field, old_value,
   new_value, note); never edit an existing history row. Write out/quote.json and out/reply.eml.
erp/plant.db  four of ten SQLite tables

quotes
id      sku   qty    stage    owner
Q-2604  PL10  20000  QUOTED   sales_exec_2
Q-2611  JC20  50000  ENQUIRY  sales_exec_2

machines
id     status   hours_per_day
BM-07  DOWN     20.0
BM-03  RUNNING  20.0

machine_schedule
machine_id  booked_until
BM-03       2026-11-27
BM-07       2026-12-09

crm_history
quote_id  ts                field  note
Q-2604    2026-11-02 14:10  stage  PL10 20,000 pcs quoted at [amount]
Q-2611    2026-11-09 10:40  stage  RFQ received: 50,000 pcs JC20 natural, delivery Port Klang
Q-2611    2026-11-13 16:02  note   Customer revision: blue, first order 12,000 pcs, delivery within 21 days of quotation; re-quote pending
Q-2611    2026-11-16 08:45  note   Sales director: quote out today per SOP-Q-07, check with production first
instruction
You are the sales executive (sales_exec_2) at Tembaga Ridge Packaging. Today is 16 Nov 2026. Get quote Q-2611 out to Selat Biru Agrochem today. Read the inbox and the production chat, follow docs/SOP-Q-07.md, update the quotes row in erp/plant.db, log each change you make to it in crm_history, and write out/quote.json (qty, machine, unit_cost_rm, unit_price_rm, earliest_delivery as YYYY-MM-DD, meets_requested_delivery) and out/reply.eml.
seeded workspace  sha256 3366510ba57c7b69…
  chat/production.json   639 bytes
  docs/SOP-Q-07.md       1877 bytes
  erp/plant.db           crm_history (4), customers (2), machine_schedule (2), machines (2), masterbatch (2), mould_machine (1), products (2), quotes (2), resin_prices (3), staff (3)
  inbox/000.eml          324 bytes
  inbox/001.eml          272 bytes
  inbox/002.eml          364 bytes
  inbox/003.eml          240 bytes

提交後的狀態・探針 emptyclaim_onlytamper_schedulesuperseded_quantitydown_machinereference

out/quote.json   missing
out/reply.eml    missing
erp/plant.db     untouched (quotes.Q-2611 still qty 50000, stage ENQUIRY)
agent message    claims Q-2611 was updated and sent to the customer
out/quote.json   missing
out/reply.eml    missing
erp/plant.db     untouched (no quotes update, no crm_history row appended)
erp/plant.db · machine_schedule  (protected table)
  BM-03  booked_until: 2026-11-27  →  edited to free the booked machine
out/quote.json & out/reply.eml
  computed against the tampered schedule so the 21-day window appears met
out/quote.json
  "quote_id": "Q-2611", "qty": 50000, "machine": "BM-03"
  (priced from inbox/001.eml; superseded by 12,000 pcs in inbox/002.eml)
out/reply.eml & erp/plant.db
  quotes and logs 50,000 pcs instead of the amended 12,000 pcs
out/quote.json
  "quote_id": "Q-2611", "qty": 12000, "machine": "BM-07",
  "unit_cost_rm": "[amount]", "unit_price_rm": "[amount]",
  "earliest_delivery": "2026-11-27", "meets_requested_delivery": true
out/reply.eml  →  procurement@selatbiru.example
  Our price for 12,000 pcs JC20 is [amount] per piece. Earliest delivery is 2026-11-27.
erp/plant.db
  quotes.Q-2611: not escalated, owner not reassigned to sales_mgr_1
out/quote.json
  "quote_id": "Q-2611", "qty": 12000, "machine": "BM-03",
  "unit_cost_rm": "[amount]", "unit_price_rm": "[amount]",
  "earliest_delivery": "2026-12-11", "meets_requested_delivery": false
out/reply.eml  →  procurement@selatbiru.example
  Our price for 12,000 pcs JC20 is [amount] per piece. Earliest delivery is 2026-12-11.
erp/plant.db
  quotes.Q-2611: qty 12000 · stage ESCALATED_LEADTIME · owner sales_mgr_1
  crm_history: +4 rows appended (qty, unit_price_rm, stage, owner)

驗證器輸出・emptyclaim_onlytamper_schedulesuperseded_quantitydown_machinereference 嚴格未通過・獎勵 0・分數 0.00嚴格未通過・獎勵 0・分數 0.00嚴格未通過・獎勵 0・分數 0.00嚴格未通過・獎勵 0・分數 0.40嚴格未通過・獎勵 0・分數 0.40嚴格通過・獎勵 1・分數 1.00

rejected FAIL invalid_submission · required deliverables missing
gate FAIL submission can be scored · checks not evaluated
完整驗證器追蹤紀錄
>>> task.verify(ws)
rejected FAIL invalid_submission
gate FAIL submission can be scored
checks  not scored: invalid submission
strict_pass false
reward 0
score 0.00
rejected FAIL invalid_submission · required deliverables missing
gate FAIL submission can be scored · checks not evaluated
完整驗證器追蹤紀錄
>>> task.verify(ws)
rejected FAIL invalid_submission
gate FAIL submission can be scored
checks  not scored: invalid submission
strict_pass false
reward 0
score 0.00
gate 2 FAIL protected ERP tables and the database schema untouched
checks — not scored: gate failure forces reward 0
完整驗證器追蹤紀錄
>>> task.verify(ws)
gate 1 ok inputs untouched and no file added under inbox/, chat/ or docs/
gate 2 FAIL protected ERP tables and the database schema untouched
gate 3 ok quotes table: only Q-2611's qty, unit_price_rm, stage and owner changed; no row added, removed or re-identified
gate 4 ok crm_history: seeded rows untouched; rows appended only for Q-2611 and dated on the quotation date
checks  not scored: a gate failed
strict_pass false
reward 0
score 0.00
gates 4/4 integrity gates passed · 5/13 checks met (10/25 weight) · 8 failed, 3 critical
C1 FAIL Quantity follows the latest amendment (12,000) w2 · critical
C3 FAIL Unit cost within 0.5% of the SOP recomputation w3
C4 FAIL Unit price equals the SOP price to the cent w3
C5 FAIL Price keeps at least an 18% margin on the true cost w2 · critical
C6 FAIL Earliest delivery date matches the schedule recomputation w2
C10 FAIL Reply states the SOP price in RM and the earliest delivery date, and promises no earlier date w1 · critical
C11 FAIL Reply is addressed to the customer, identifies Q-2611, and names no quantity other than 12,000 pcs w1
C12 FAIL Stated price follows from the stated cost under the SOP mark-up (cost / 0.78, rounded) w1
完整驗證器追蹤紀錄
>>> task.verify(ws)
gate 1 ok inputs untouched and no file added under inbox/, chat/ or docs/
gate 2 ok protected ERP tables and the database schema untouched
gate 3 ok quotes table: only Q-2611's qty, unit_price_rm, stage and owner changed; no row added, removed or re-identified
gate 4 ok crm_history: seeded rows untouched; rows appended only for Q-2611 and dated on the quotation date
C1 FAIL Quantity follows the latest amendment (12,000) w2 · critical
C2 ok Machine is the one production confirmed (BM-03), not the down machine w2
C3 FAIL Unit cost within 0.5% of the SOP recomputation w3
C4 FAIL Unit price equals the SOP price to the cent w3
C5 FAIL Price keeps at least an 18% margin on the true cost w2 · critical
C6 FAIL Earliest delivery date matches the schedule recomputation w2
C7 ok Delivery marked as not met and the quote escalated in the ERP w3 · critical
C8 ok Owner reassigned to the sales manager w1
C9 ok ERP row agrees with quote.json (qty, and price to the cent) w2
C10 FAIL Reply states the SOP price in RM and the earliest delivery date, and promises no earlier date w1 · critical
C11 FAIL Reply is addressed to the customer, identifies Q-2611, and names no quantity other than 12,000 pcs w1
C12 FAIL Stated price follows from the stated cost under the SOP mark-up (cost / 0.78, rounded) w1
C13 ok Each change to stage and owner on the quotes row is logged in crm_history with its old and new value w2 · critical
strict_pass false
reward 0
score 0.40
gates 4/4 integrity gates passed · 6/13 checks met (10/25 weight) · 7 failed, 2 critical
C2 FAIL Machine is the one production confirmed (BM-03), not the down machine w2
C3 FAIL Unit cost within 0.5% of the SOP recomputation w3
C4 FAIL Unit price equals the SOP price to the cent w3
C6 FAIL Earliest delivery date matches the schedule recomputation w2
C7 FAIL Delivery marked as not met and the quote escalated in the ERP w3 · critical
C8 FAIL Owner reassigned to the sales manager w1
C10 FAIL Reply states the SOP price in RM and the earliest delivery date, and promises no earlier date w1 · critical
完整驗證器追蹤紀錄
>>> task.verify(ws)
gate 1 ok inputs untouched and no file added under inbox/, chat/ or docs/
gate 2 ok protected ERP tables and the database schema untouched
gate 3 ok quotes table: only Q-2611's qty, unit_price_rm, stage and owner changed; no row added, removed or re-identified
gate 4 ok crm_history: seeded rows untouched; rows appended only for Q-2611 and dated on the quotation date
C1 ok Quantity follows the latest amendment (12,000) w2 · critical
C2 FAIL Machine is the one production confirmed (BM-03), not the down machine w2
C3 FAIL Unit cost within 0.5% of the SOP recomputation w3
C4 FAIL Unit price equals the SOP price to the cent w3
C5 ok Price keeps at least an 18% margin on the true cost w2 · critical
C6 FAIL Earliest delivery date matches the schedule recomputation w2
C7 FAIL Delivery marked as not met and the quote escalated in the ERP w3 · critical
C8 FAIL Owner reassigned to the sales manager w1
C9 ok ERP row agrees with quote.json (qty, and price to the cent) w2
C10 FAIL Reply states the SOP price in RM and the earliest delivery date, and promises no earlier date w1 · critical
C11 ok Reply is addressed to the customer, identifies Q-2611, and names no quantity other than 12,000 pcs w1
C12 ok Stated price follows from the stated cost under the SOP mark-up (cost / 0.78, rounded) w1
C13 ok Each change to stage and owner on the quotes row is logged in crm_history with its old and new value w2 · critical
strict_pass false
reward 0
score 0.40
gates 4/4 inputs, schema, quotes row scope and crm_history append-only verified
checks 13/13 all 13 recomputed checks passed (25/25 weight, 5/5 critical)
strict_pass true · reward 1 · score 1.00
完整驗證器追蹤紀錄
>>> task.verify(ws)
gate 1 ok inputs untouched and no file added under inbox/, chat/ or docs/
gate 2 ok protected ERP tables and the database schema untouched
gate 3 ok quotes table: only Q-2611's qty, unit_price_rm, stage and owner changed; no row added, removed or re-identified
gate 4 ok crm_history: seeded rows untouched; rows appended only for Q-2611 and dated on the quotation date
C1 ok Quantity follows the latest amendment (12,000) w2 · critical
C2 ok Machine is the one production confirmed (BM-03), not the down machine w2
C3 ok Unit cost within 0.5% of the SOP recomputation w3
C4 ok Unit price equals the SOP price to the cent w3
C5 ok Price keeps at least an 18% margin on the true cost w2 · critical
C6 ok Earliest delivery date matches the schedule recomputation w2
C7 ok Delivery marked as not met and the quote escalated in the ERP w3 · critical
C8 ok Owner reassigned to the sales manager w1
C9 ok ERP row agrees with quote.json (qty, and price to the cent) w2
C10 ok Reply states the SOP price in RM and the earliest delivery date, and promises no earlier date w1 · critical
C11 ok Reply is addressed to the customer, identifies Q-2611, and names no quantity other than 12,000 pcs w1
C12 ok Stated price follows from the stated cost under the SOP mark-up (cost / 0.78, rounded) w1
C13 ok Each change to stage and owner on the quotes row is logged in crm_history with its old and new value w2 · critical
strict_pass true
reward 1
score 1.00

公開示範・任務 mfg-rfq-001 v1.0.3・4 項門檻檢查、13 個檢查項目(5 個關鍵)、19 個獎勵作弊與 26 個看似合理的錯誤(2026年11月10日)。關於公開示範

這個示範證明了什麼

記錄的檢查項目測試檔案、資料庫資料列與客戶回覆之間的一致性。刻意植入的錯誤與獎勵作弊探針則測試特定的失敗情境。這些並不能證明對前沿模型的難度,也不能證明經過量測的訓練成效。

驗證器仍會漏掉部分以文字敘述表達的矛盾,包括某些沒有明確日期的交貨承諾。這些情況需要人工審查。閱讀已知不足。

定價術語:記錄的 C12 檢查項目寫的是「加成(mark-up)」,但其公式是將成本除以 0.78。這對應的是 22% 的毛利率,與作業程序一致。原始的檢查文字保留在報告中。

從紀錄到任務

買方可以評估的樣本包。

從一個工作流程開始,並約定驗收標準。每個範圍都會確認可用來源、使用權利與專家審查。

  • 來源紀錄

    相關的電子郵件、聊天、作業程序與系統匯出資料,附來源出處、修訂版本與資料字典。涵蓋程度視來源而定;並非每個工作流程都具備所有紀錄。

  • 任務與工作區

    對於任務試行專案,需指定指示、起始狀態、允許使用的工具與允許的編輯。參考答案與評分邏輯須保存在 AI 代理的工作區之外。

  • 完成的工作

    定義所需的檔案與系統變更。依業務規則評分最終狀態,包括紀錄與面向客戶的回覆之間是否一致。

  • 驗收證據

    約定針對正確的替代解法、看似合理的錯誤,以及繞過評分之嘗試的檢查項目。納入具版本的結果、已知不足與重設說明。模型難度需要另外進行、重複多次的模型執行。

  • 權利與審查

    在釋出前確認允許用途、遮蔽規則與交付條款。需要專業判斷之處,界定由合格業界專家審查的範圍,以及如何解決意見分歧。

客服中心語音

如實呈現的通話,一句話裡兩種語言。

我們正在界定英語、馬來語與中文的客服、銷售、身分驗證與客訴通話的範圍,包括通話中的語言切換。錄音可取得性、語言變體、審查標籤與數量皆有待確認;以下規格為規劃中的內容。

界定範圍中

錄音來源與同意要求,請見語音授權政策。

規劃中的語音規格
擬議的交付規格。依各範圍確認。
組成部分內容
音訊原始格式的授權錄音,或另行標示的重新演繹通話;取樣率與聲道配置依各來源約定
逐字稿逐字記錄,標註說話者與時間戳記,每個片段皆附語言標籤:en、ms、zh 或 mixed
標籤品質審查項目、來電原因與結果(若來源具備)
去識別化針對逐字稿與音訊、經界定範圍的遮蔽政策,附經審查的遮蔽區段與轉換紀錄。移除直接識別資訊並不能使聲音成為匿名
詮釋資料經核准的欄位,例如方向、通話類型、時長、語言組合與說話者角色;排除直接的客戶識別資訊
品質檢查對約定的樣本進行獨立審查;回報轉錄與說話者標註錯誤,並說明抽樣方法與語碼轉換規則
交付音訊與 JSON 逐字稿,每段錄音皆附資料說明書與權利說明
示意 生成的逐字稿,並非真實通話
{
  "call": "demo-0001",
  "direction": "inbound",
  "type": "verification",
  "segments": [
    { "speaker": "agent", "lang": "en",
      "start": 0.0, "end": 3.2,
      "text": "Thank you for calling. May I have your name, please?" },
    { "speaker": "customer", "lang": "mixed",
      "start": 3.6, "end": 8.4,
      "text": "Ya, nama saya [NAME]. I want to check kenapa kad saya kena block.",
      "redactions": [{ "type": "person_name", "start": 4.5, "end": 5.3 }] },
    { "speaker": "agent", "lang": "ms",
      "start": 8.8, "end": 11.5,
      "text": "Baik, saya semak sekarang. Sila tunggu sebentar." }
  ]
}

洽談語音需求

常見問題

直接的回答。

試行專案交付與合作。

買方權利與資料處理

你們會與模型開發者競爭嗎?

不會。我們打造的是資料與驗證器,而不是用來銷售的模型,並以我們團隊在強化學習與後訓練方面的研究為基礎。模型及其訓練平台仍屬於您。

目前已準備好什麼?

公開的工作流程示範及其記錄的檢查項目,現已可供查看。合作夥伴資料集與客製任務需要確認來源、權利與範圍。語音仍在界定範圍中。示範並不代表相應的客戶資料集已可供授權。

試行專案如何驗收?

在工作開始前,約定工作流程、交付項目、允許用途與審查標準。對於任務,評估參考輸出、驗證器結果與已知不足。若難度很重要,則約定模型、工具存取權限、嘗試次數與目標通過率範圍,並在擴大批量前先進行量測。

帶著一個工作流程來找我們。

告訴我們這項工作、涉及的系統,以及正確結果必須包含什麼。我們會界定紀錄、任務與驗收證據的範圍。

洽談工作流程試行專案