Build a Supplier Payment-Change Verification Workspace
Review fictional supplier bank-detail changes using trusted verification records and document history. Keep convincing email text separate from independently authenticated payment instructions.
What you are building
A supplier email asks to change a payment destination. Build a review desk that checks for independently recorded confirmation rather than trusting the wording of the email. Even a confirmed change goes to human approval. Show which evidence is missing and preserve the original instruction. Do not contact suppliers or change payment details.
Rules
No payments, supplier-master writes, impersonation, or external contact. 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 payment-change evidence reconciliation module. A mock approval workflow with an immutable decision record. 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
Compare requested changes with the approved supplier record.
Separate requester-supplied content from trusted verification evidence.
Apply a fictional verification workflow with explicit unresolved states.
Export a reviewer packet without changing payment instructions.
Resources
2 attached datasets, including two visible synthetic starter cases. 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.