Menu

Enterprise workflows

Enterprise work. Checkable outcomes.

License business records or commission agent tasks built around them. Connect email, chat and system state to a concrete deliverable: a revised quote, an updated record and a reply that agrees with both.

Discuss a workflow pilot Inspect the workflow example

Inspect a recorded demonstration

A revised order. A machine down. A quote to fix.

The customer changes the order. Production changes the machine. The task is to reconcile both with the schedule and costing rules, then update the quote, audit history and customer reply.

Invented business data. Select a prepared answer to inspect its recorded verifier result. This page does not run an agent or execute the verifier; monetary values are masked.

Pick an answer
Starting workspace · mfg-rfq-001 reset 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

Submitted state · probe 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)

Verifier output · emptyclaim_onlytamper_schedulesuperseded_quantitydown_machinereference strict fail · reward 0 · score 0.00strict fail · reward 0 · score 0.00strict fail · reward 0 · score 0.00strict fail · reward 0 · score 0.40strict fail · reward 0 · score 0.40strict pass · reward 1 · score 1.00

rejected FAIL invalid_submission · required deliverables missing
gate FAIL submission can be scored · checks not evaluated
Full verifier trace
>>> 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
Full verifier trace
>>> 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
Full verifier trace
>>> 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
Full verifier trace
>>> 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
Full verifier trace
>>> 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
Full verifier trace
>>> 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

Public demonstration · task mfg-rfq-001 v1.0.3 · 4 gates, 13 checks (5 critical), 19 reward hacks and 26 plausible mistakes (10 November 2026). About the public demonstrations

What this demonstration proves

The recorded checks test consistency across files, database rows and the customer reply. Planted mistakes and reward-hack probes test specific failure cases. They do not establish frontier-model difficulty or a measured training gain.

The verifier still misses some contradictions expressed in prose, including certain delivery promises without an explicit date. Those cases need human review. Read the known gaps.

Pricing terminology: the recorded C12 check says “mark-up”, but its formula divides cost by 0.78. That targets a 22% gross margin, consistent with the procedure. The original check text is preserved in the report.

From records to tasks

A sample pack a buyer can evaluate.

Start with a workflow and agree the acceptance criteria. Available sources, usage rights and expert review are confirmed for each scope.

  • Source records

    Relevant email, chat, procedures and system exports, with provenance, revisions and a data dictionary. Coverage depends on the source; not every workflow has every record.

  • Task and workspace

    For a task pilot, specify the instruction, starting state, allowed tools and permitted edits. Keep the reference answer and grading logic outside the agent’s workspace.

  • Finished work

    Define the required files and system changes. Grade the final state against the business rules, including agreement between the records and the customer-facing response.

  • Acceptance evidence

    Agree checks for correct alternatives, plausible mistakes and attempts to bypass grading. Include versioned results, known gaps and reset instructions. Model difficulty needs separate, repeated model runs.

  • Rights and review

    Confirm permitted uses, redaction rules and delivery terms before release. Where judgment is required, scope qualified practitioner review and how disagreements will be resolved.

Contact-centre speech

Calls as they are really spoken, two languages in one sentence.

We are scoping service, sales, verification and complaint calls in English, Malay and Chinese, including language switches within a call. Recording availability, language varieties, review labels and quantities must be confirmed; the specification below is planned.

Scoping

Recording sources and consent requirements are in the speech licensing policy.

Planned speech specification
Proposed delivery specification. Confirmed per scope.
PartWhat it holds
AudioLicensed recordings in their source format, or separately labelled re-enacted calls; sample rate and channel layout agreed per source
TranscriptsVerbatim, speaker-attributed and timestamped, with a language tag on every segment: en, ms, zh or mixed
LabelsQuality-review items, call reason and outcome, where the source holds them
De-identificationA scoped redaction policy for transcript and audio, with reviewed spans and a record of transformations. Removing direct identifiers does not make a voice anonymous
MetadataApproved fields such as direction, call type, duration, language mix and speaker roles; direct customer identifiers excluded
Quality checkIndependent review of an agreed sample; report transcription and speaker-attribution errors with the sampling method and code-switching rules
DeliveryAudio with JSON transcripts, a datasheet and a rights note per recording
Illustrative Generated transcript, not a real call
{
  "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." }
  ]
}

Discuss speech requirements

Questions

Straight answers.

Pilot delivery and collaboration.

Buyer rights and data handling

Do you compete with model developers?

No. We build the data and verifiers, not models to sell, informed by our team’s research in reinforcement learning and post-training. The model and its training platform stay yours.

What is ready today?

The public workflow demonstration and its recorded checks are available to inspect now. Partner datasets and custom tasks require source, rights and scope confirmation. Speech is in scoping. A demonstration is not a claim that a corresponding customer dataset is ready to license.

How is a pilot accepted?

Agree the workflow, deliverables, permitted uses and review criteria before work starts. For tasks, assess the reference output, verifier results and known gaps. If difficulty matters, agree the models, tool access, attempt count and target pass-rate range, then measure them before expanding the batch.

Bring us a workflow.

Tell us the job, the systems involved and what a correct result must contain. We will scope the records, task and acceptance evidence.

Discuss a workflow pilot