Moxie Studio / Practice lab 01 / v0.1

Evidence Triage Practice · Free sample

Find the gap before you trust the conclusion.

For digital-product support-team leads and learners. Work from the supplied records, not from assumptions about what probably happened.

All cases and records are fictional, AI-assisted original exercises. Not legal, financial or live dispute advice. No win-rate, compliance or training-effectiveness claim. No customer records, uploads or account access.

How to practice

  1. Read a case. Mark each statement supported or not supported by these records only. Record elapsed minutes separately.
  2. Use the free Stripe evidence guidance if desired. Its categories are context, not an answer key for these fictional records.
  3. Commit answers before opening the key. Score locally or manually, one point per correct answer. A blank is unscored, not false.

No answers are transmitted or saved automatically. Closing or reloading clears selections. Without JavaScript, use the same questions and key with the manual CSV scorecard. Enter only A/B rows for this two-case sample; C/D rows are reserved for the full pack. Do not double-count case minutes across item rows.

Case A / Fictional dossier

The wrong account

Claim to audit: The reviewer says the access log proves the purchasing account used the product.

Supplied records

A1
2026-09-01 10:00 UTC | Order SYN-A | buyer account acct-17 | product Sketch Kit
A2
2026-09-01 10:05 UTC | Access event | account acct-71 | product Sketch Kit
A3
Export note | no account-link or delegation record supplied

Four evidence-quality checks

A1. The account IDs in A1 and A2 match.
A2. The supplied access event establishes use by the purchasing account.
A3. A verified account mapping or corrected export would help resolve the gap.
A4. These records establish that the buyer committed fraud.

Open case A answer key (after answering)
  1. Not supported. A1 names acct-17; A2 names acct-71. This is an adverse mismatch, not merely missing information. Record A1,A2.
  2. Not supported. The linkage is unproven. A3 supplies no mapping between the accounts. Record A1,A2,A3.
  3. Supported. A mapping could resolve the mismatch; requesting it does not mean it exists. Record A3.
  4. Not supported. A mismatch does not establish intent, authorization or fraud. Keep the conclusion limited to unsupported linkage. Record A1,A2,A3.

Guidance context: Stripe reason-specific evidence guidance. The scoring is based on the fictional records above, not a processor ruling.

Case B / Fictional dossier

A clock without a zone

Claim to audit: The reviewer says access definitely happened after the complaint.

Supplied records

B1
2026-09-03 09:30 UTC | account acct-22 | complaint: cannot open the file
B2
2026-09-03 10:00 | account acct-22 | access event | timezone field absent
B3
Export note | server timezone and UTC offset not supplied

Four evidence-quality checks

B1. B1 and B2 refer to the same account label.
B2. The sequence of B1 and B2 is determined by the displayed clock times.
B3. The missing timezone proves that the access event is fabricated.
B4. The original event timestamp with its UTC offset would help resolve chronology.

Open case B answer key (after answering)
  1. Supported. Both records name acct-22. That match alone does not establish who controlled it. Record B1,B2.
  2. Not supported. B1 is UTC; B2 has no zone. The absolute sequence remains unresolved. Record B1,B2,B3.
  3. Not supported. Missing context is not proof of fabrication. Record B2,B3.
  4. Supported. Seek original timestamp context rather than assume the local clock equals UTC. Record B2,B3.

Guidance context: Stripe reason-specific evidence guidance. The scoring is based on the fictional records above, not a processor ruling.

Compare, do not overclaim

For exploratory comparison, use A then B (or B then A for the next learner): guidance only on the first case, then review its explanation before the second case. Keep the second key closed until answering. C and D offer an additional pair in the full pack. Record case, condition, accuracy and elapsed minutes in the CSV. Cases are not calibrated equivalents; practice effects and order differences prevent causal conclusions.

Proposed full-team license: $12 USD once, up to five learners. Orders closed pending seller, payment and exact-delivery verification. This free two-case evaluation sample is not a purchase or a paid full-pack license.

Share exercise feedback

Optional: send role/team size, case IDs, anonymous aggregate score change, any confusing wording, and whether you would enquire about the proposed $12 team license. Do not send names, order IDs, payment details or customer records.

Selectable address: moxie@staticterminal.com
Suggested subject: Evidence Triage Practice feedback

Optional: launch your email app

No form submission, tracking or automatic follow-up.