What records and relationships can MirrorFirm generate for this workflow?

A release for this workflow could contain the two sides of the mismatch, the history around them, the rules that govern the fix, and the outcome.

**Records.** Paired records across systems: invoices and payments, orders and shipments, claims and reserves, appointments and billing lines. Each set can include matching and non-matching cases, so an agent learns what agreement looks like as well as disagreement.

**Relationships.** Match keys, partial matches, one-to-many splits, reversals, duplicates and superseded versions. Timestamps let a buyer test whether the agent separates timing differences from errors.

**Policies.** Tolerance rules, approval limits, correction methods, cut-off dates and escalation paths, written as text and, where useful, as structured fields.

**Tasks.** A case to resolve, with a stated goal, the tools available, and a labelled root cause that is held out from the agent.

**Environment state.** A simulated set of systems with seeded records that an agent can query and change, with a reset to the initial state.

All of this is generated and shaped by direct observation of how businesses handle these cases. It is not a copy of business records, so a buyer should still inspect a sample for grounding, plausibility and any disclosure risk before relying on it.