Build an Account Takeover Evidence Review Workbench
Combine synthetic authentication, device, session, and transaction evidence into a reviewable case timeline. Distinguish verified customer activity from unresolved account takeover indicators.
What you are building
Two sessions show the same risk signal. Only one has independent customer confirmation. Build a case timeline that lets an investigator distinguish those records and explain the review route. Keep contradictory evidence visible. Use synthetic records only. Do not freeze an account, contact a customer, or turn a risk signal into an accusation.
Rules
No account freezing, customer contact, or fraud accusation. These fixtures are not practitioner-adjudicated bank cases. No fabricated records, source citations, professional endorsements, or expert-adjudication claims. No future-data leakage into dated decisions, model fitting, or historical valuation inputs. No unauthorized payments, account restrictions, regulatory filings, or production changes. No automated appraisal certification, tax-compliance determination, or unsupported fraud accusation. No concealed uncertainty or silently invented inputs required for a numerical conclusion.
How work is evaluated
100-point weighted review with safety gates. Visible starter cases do not establish full application correctness.
A case assembly service with reproducible decision snapshots. A review interface that distinguishes facts, hypotheses, and unresolved evidence. Runnable local application, setup commands, and a dependency lockfile. Versioned input data, data dictionary, acquisition instructions, and rights notes. Calculation traces, source references, assumption records, and exported review artifacts. A deterministic baseline and tests for normal, incomplete, contradictory, and failure-recovery cases. A recorded complete workflow with a reproducible manifest and explicit limitations.
Datasets
Public datasets, plus the private datasets you have access to.
How submissions are scored
Learning goals
Assemble evidence in event and observation order.
Identify conflicts between account activity and verification records.
Apply a transparent fictional review-routing policy.
Export an investigator packet with uncertainty and missing evidence.
Resources
4 attached datasets, including two visible synthetic starter cases. FRD-01 evidence timelines. Verification states are fictional and are not fraud truth. FRD-04 event-ledger prototype. Row patterns are deliberately artificial and unsuitable for model performance claims. The fixture ZIP supplies synthetic exercise inputs. It does not supply independently verified real-world records.
Challenge setup
Challenge input
Input details are not configured.
Agent execution
No agent tool is listed for this challenge.
Evaluated output
No output checks are configured.
- Rubric dimension 1
- Rubric dimension 2
- Rubric dimension 3
- 2 public reference cases
- No runtime settings are configured.
Shows the first task, up to three tools, and up to three evidence items.
View technical recipe
Configured tools
No tool records are attached.
Evaluation contract
- Rubric dimension 1 · Weight 30
- Rubric dimension 2 · Weight 25
- Rubric dimension 3 · Weight 20
- Rubric dimension 4 · Weight 15
- Rubric dimension 5 · Weight 10
Reference cases
- 2 public reference cases
Workflow tasks
No workflow tasks are configured.
Recipe freeze marker
No recipe freeze time is recorded.