Build a Delayed Fraud Outcome and Label-Maturity Ledger
Track when fraud outcomes become known and when they are sufficiently mature for analysis. Prevent recent unresolved transactions from being mislabeled as legitimate activity.
What you are building
An outcome is known after 90 days under a fictional 60-day maturity rule. A second transaction of the same age remains unresolved. Build a dated label ledger that separates training eligibility from the eventual outcome. Export labels as known at a chosen cutoff. Do not count unresolved transactions as legitimate or treat 60 days as a real network deadline.
Rules
The maturity period is a fictional fixture policy, not a universal chargeback deadline. 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 point-in-time label store. A data-quality report quantifying unknown and revised outcomes. 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
Build a versioned outcome event ledger.
Apply an explicit fictional observation-window policy.
Produce as-of training snapshots and mature monitoring cohorts.
Export censoring summaries and label-revision histories.
Resources
4 attached datasets, including two visible synthetic starter cases. FRD-04 event-ledger prototype. Row patterns are deliberately artificial and unsuitable for model performance claims. FRD-04 delayed and unresolved outcomes. Keep this table separate from decision-time features. 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.