FlakeMap Trust Desk / Proposed module 01

Shape the
scenario.

Turn an approved, redacted workflow fixture into a scenario with a named input, an expected artifact, and a human-readable criterion.

Scope a Trust Desk study Explore synthetic demo

APPROVED FIXTURE / PO-204

{
  "order": "PO-204",
  "tool": "stock.lookup",
  "source": "redacted",
  "expected_drafts": 1
}

Scenario readyExactly one draft
Original order reference

Proposed source mapping · synthetic example

DEMO — SYNTHETIC DATA

The question this module answers

What are we actually testing?

Input: Approved, redacted trace JSON
Output: A scoped scenario and source record

Keep the source attached

Retain fixture IDs, redaction notes, and source references alongside the scenario.

Define the artifact

Write the task-level criterion before running variants: exactly one purchase-order draft, with the original order reference.

Set the boundary

Separate allowed stub responses from excluded production calls. Trace access must be approved.

Follow the proposed workflow

A visible path from
input to decision.

Approve a redacted fixture

Approved, redacted trace JSON

Proposed process / synthetic example

Module boundaries

Useful evidence.
Honest limits.

Is Trust Desk live?

This module is available to explore in the synthetic demo. A first pilot would test one scoped module with approved fixtures.

What does the demo execute?

It selects deterministic stub fixtures and changes local mock states. It does not call models, write to tools, import customer traces, or modify CI.

How is value validated?

Compare with the existing eval gate and confirm a meaningful missed regression independently. A named engineering owner must commit a gate or fund a trial before expansion.

A smaller test. A clearer decision.

Start with the workflow
you can’t afford to guess.

Agree on one task criterion, an approved fixture, and a named engineering owner.

Request a replay study

Shape thescenario.