Build a Chronological Ledger Narrative and Documentary Missing-Link Annotator
Draft chronological narrative summaries from normalized account ledgers. Highlight critical documentary omissions by cross-referencing tabular completeness against provided supporting invoices and contracts.
What you are building
The core problem, expected build, and operating context for this challenge.
Draft chronological narrative summaries from normalized account ledgers. Highlight critical documentary omissions by cross-referencing tabular completeness against provided supporting invoices and contracts.
Financial Crime Case Preparer
Ingest simplified normalized ledger entries containing sender, receiver, timestamp, and purpose fields.
Validate ledger tabular completeness against required schema fields using Frictionless Data, focusing on attachment references.
Draft an objective chronological narrative describing the fund flow sequence across all verified accounts.
Compile an explicit list of missing-link annotations where tabular records lack corresponding external documentary references.
A two-pane narrative review window with editable summary paragraphs alongside flagged tabular missing-link annotations.
Generate synthetic business transaction batches with deliberately omitted supporting invoice references and transport documents to test missing-link detection. Starter examples below are synthetic. They are not downloaded records.
Frictionless data validation Frictionless Data validation concepts to check transaction ledger completeness against schema expectations.
dspy, frictionless, pydantic. Optimizes narrative compilation prompts to systematically highlight evidence gaps without hallucinations. Local or cloud LLM with strong zero-shot summarization and tabular factual reasoning.
Submit runnable source, pinned dependencies, setup commands, a working interface, example outputs, and a recorded end-to-end demo. Include tests and an action log.
Drafts chronological summaries describing all transactions in the ingested fixture.
Accurately isolates specific transaction IDs lacking mandatory documentary references based on tabular completeness rules.
Generates clean Markdown and JSON output formats ready for senior investigator review.
```json [ { "input": { "case_id": "CASE-1049", "transactions": [ { "tx_id": "TX-01", "amount": 45000, "currency": "EUR", "sender": "Alpha Ltd", "receiver": "Beta SA", "doc_attached": "INV-2023-99" }, { "tx_id": "TX-02", "amount": 42000, "currency": "EUR", "sender": "Beta SA", "receiver": "Gamma Inc", "doc_attached": null } ] }, "expected_output": { "case_id": "CASE-1049", "narrative": "Alpha Ltd transferred 45,000 EUR to Beta SA supported by INV-2023-99. Beta SA subsequently transferred 42,000 EUR to Gamma Inc.", "missing_link_annotations": [ { "tx_id": "TX-02", "missing_field": "doc_attached", "reason": "Missing supporting external documentary reference." } ], "ready_for_review": false } }, { "input": { "case_id": "CASE-1050", "transactions": [ { "tx_id": "TX-03", "amount": 10000, "currency": "USD", "sender": "Acme Corp", "receiver": "Delta LLC", "doc_attached": "PO-8812" } ] }, "expected_output": { "case_id": "CASE-1050", "narrative": "Acme Corp remitted 10,000 USD to Delta LLC verified by purchase order PO-8812.", "missing_link_annotations": [], "ready_for_review": true } } ] ```
Narratives are purely descriptive without accusatory legal claims or regulatory filing triggers. Examples are simplified synthetic app records. Use mock external writes. Require human review before any real deployment.
Participation guide
Narratives are purely descriptive without accusatory legal claims or regulatory filing triggers. Examples are simplified synthetic app records. Use mock external writes and human review.
How work is evaluated
Drafts chronological summaries describing all transactions in the ingested fixture. Accurately isolates specific transaction IDs lacking mandatory documentary references based on tabular completeness rules. Generates clean Markdown and JSON output formats ready for senior investigator review.
Runnable source, pinned dependencies, setup commands, working interface, example outputs, recorded demo, tests, and action logs.
Challenge datasets
Public datasets, plus the private datasets you have access to.
How submissions are scored
These dimensions define what the evaluator checks and which criteria separate a passable run from a strong one.
Complete workflow
Ingest simplified normalized ledger entries containing sender, receiver, timestamp, and purpose fields. Validate ledger tabular completeness against required schema fields using Frictionless Data, focusing on attachment references. Draft an objective chronological narrative describing the fund flow sequence across all verified accounts. Compile an explicit list of missing-link annotations where tabular records lack corresponding external documentary references.
Missing or incorrect.
Partly complete, with documented gaps.
Complete, with reproducible evidence.
Correctness and evidence
Drafts chronological summaries describing all transactions in the ingested fixture. Accurately isolates specific transaction IDs lacking mandatory documentary references based on tabular completeness rules. Generates clean Markdown and JSON output formats ready for senior investigator review.
Missing or incorrect.
Partly complete, with documented gaps.
Complete, with reproducible evidence.
Review interface
A two-pane narrative review window with editable summary paragraphs alongside flagged tabular missing-link annotations.
Missing or incorrect.
Partly complete, with documented gaps.
Complete, with reproducible evidence.
Safe execution
Narratives are purely descriptive without accusatory legal claims or regulatory filing triggers. Examples are simplified synthetic app records.
This dimension contributes its full weight only when the submission satisfies the requirement. Partial credit is not awarded.
What you should walk away with
Ingest simplified normalized ledger entries containing sender, receiver, timestamp, and purpose fields.
Validate ledger tabular completeness against required schema fields using Frictionless Data, focusing on attachment references.
Draft an objective chronological narrative describing the fund flow sequence across all verified accounts.
Compile an explicit list of missing-link annotations where tabular records lack corresponding external documentary references.
Reference links and supporting material
Generate synthetic business transaction batches with deliberately omitted supporting invoice references and transport documents to test missing-link detection. Supplied starter examples are synthetic, not source extracts.
Challenge setup
Configuration summary for this challenge.
Challenge input
Input details are not configured.
DSPy
Prompt and LM program optimization framework.
Evaluated output
No output checks are configured.
- Ingest simplified normalized ledger entries containing sender, receiver, timestamp, and purpose fields. Val...
- Drafts chronological summaries describing all transactions in the ingested fixture. Accurately isolates spe...
- A two-pane narrative review window with editable summary paragraphs alongside flagged tabular missing-link...
- 2 public reference cases
- 3 configured tools
Summary shows the first task, up to three tools, and up to three evidence items. Open the technical recipe to view all configured items.
View technical recipe
Configured tools
- DSPy · Optional
- DSPy · Optional
- DSPy · Optional
Evaluation contract
- Complete workflow · Weight 40
- Correctness and evidence · Weight 30
- Review interface · Weight 20
- Safe execution · Weight 10
Reference cases
- 2 public reference cases
Workflow tasks
No workflow tasks are configured.
Recipe freeze marker
No recipe freeze time is recorded.