Build a Beneficial-Ownership Evidence Retention Review Console
Develop a beneficial-ownership evidence retention and permission review console using explicitly fictional policies. Parse BODS data to verify compliance with mock retention rules and generate structured permission evaluation reports.
What you are building
The core problem, expected build, and operating context for this challenge.
Develop a beneficial-ownership evidence retention and permission review console using explicitly fictional policies. Parse BODS data to verify compliance with mock retention rules and generate structured permission evaluation reports.
KYC onboarding escalation analyst
Parse simplified synthetic BODS v0.4 statements to extract beneficial ownership declarations and attached evidence document metadata.
Evaluate evidence records against explicitly fictional data retention rules and mock permission schemas.
Identify documents exceeding mock retention limits or lacking required user access level justifications.
Synthesize a structured permission review report detailing non-compliant records and recommended access revocation actions.
Split-screen dashboard displaying evidence retention flags on the left and generated permission review reports on the right.
Generate simplified synthetic BODS statement packages in JSON format modeling multi-tiered holding companies and attached evidence metadata with fictional retention attributes. Starter examples below are synthetic. They are not downloaded records.
Beneficial Ownership Data Standard Extracts BODS v0.4 data modeling concepts for beneficial ownership declarations and entity relationship links.
langgraph, pydantic, fastapi. Manages complex state transitions across evidence parsing, mock policy evaluation, and report generation. Fast hosted model or local Ollama instance capable of evaluating document metadata against structured mock policies and drafting clear reports.
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.
Validates retention dates against fictional policy limits and identifies violations.
Flags documents with unauthorized access according to mock permission schemas.
Outputs a structured JSON report of retention violations and recommended actions.
```json [ { "input": { "subject_entity": "Atlas Logistics Holdings", "evidence_records": [ { "doc_id": "doc1", "type": "passport", "retention_days": 400, "access_level": "admin" }, { "doc_id": "doc2", "type": "utility_bill", "retention_days": 150, "access_level": "user" } ], "mock_policy": { "max_retention_days": 365, "required_access": "admin" } }, "expected_output": { "subject_entity": "Atlas Logistics Holdings", "violations": [ { "doc_id": "doc1", "reason": "Exceeds max_retention_days" }, { "doc_id": "doc2", "reason": "Insufficient access_level" } ], "compliance_status": "failed", "recommended_actions": [ "Revoke or delete doc1", "Update access for doc2" ] } }, { "input": { "subject_entity": "Direct Green Energy SA", "evidence_records": [ { "doc_id": "doc3", "type": "incorporation_certificate", "retention_days": 100, "access_level": "admin" } ], "mock_policy": { "max_retention_days": 365, "required_access": "admin" } }, "expected_output": { "subject_entity": "Direct Green Energy SA", "violations": [], "compliance_status": "passed", "recommended_actions": [] } } ] ```
Performs read-only mock policy audits on simplified synthetic app records; uses explicitly fictional policies for compliance checks. Use mock external writes. Require human review before any real deployment.
Participation guide
Performs read-only mock policy audits on simplified synthetic app records; uses explicitly fictional policies for compliance checks. Use mock external writes and human review.
How work is evaluated
Validates retention dates against fictional policy limits and identifies violations. Flags documents with unauthorized access according to mock permission schemas. Outputs a structured JSON report of retention violations and recommended actions.
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
Parse simplified synthetic BODS v0.4 statements to extract beneficial ownership declarations and attached evidence document metadata. Evaluate evidence records against explicitly fictional data retention rules and mock permission schemas. Identify documents exceeding mock retention limits or lacking required user access level justifications. Synthesize a structured permission review report detailing non-compliant records and recommended access revocation actions.
Missing or incorrect.
Partly complete, with documented gaps.
Complete, with reproducible evidence.
Correctness and evidence
Validates retention dates against fictional policy limits and identifies violations. Flags documents with unauthorized access according to mock permission schemas. Outputs a structured JSON report of retention violations and recommended actions.
Missing or incorrect.
Partly complete, with documented gaps.
Complete, with reproducible evidence.
Review interface
Split-screen dashboard displaying evidence retention flags on the left and generated permission review reports on the right.
Missing or incorrect.
Partly complete, with documented gaps.
Complete, with reproducible evidence.
Safe execution
Performs read-only mock policy audits on simplified synthetic app records; uses explicitly fictional policies for compliance checks.
This dimension contributes its full weight only when the submission satisfies the requirement. Partial credit is not awarded.
What you should walk away with
Parse simplified synthetic BODS v0.4 statements to extract beneficial ownership declarations and attached evidence document metadata.
Evaluate evidence records against explicitly fictional data retention rules and mock permission schemas.
Identify documents exceeding mock retention limits or lacking required user access level justifications.
Synthesize a structured permission review report detailing non-compliant records and recommended access revocation actions.
Reference links and supporting material
Generate simplified synthetic BODS statement packages in JSON format modeling multi-tiered holding companies and attached evidence metadata with fictional retention attributes. Supplied starter examples are synthetic, not source extracts.
Challenge setup
Configuration summary for this challenge.
Challenge input
Input details are not configured.
LangGraph
Runtime for stateful agent workflows.
Evaluated output
No output checks are configured.
- Parse simplified synthetic BODS v0.4 statements to extract beneficial ownership declarations and attached e...
- Validates retention dates against fictional policy limits and identifies violations. Flags documents with u...
- Split-screen dashboard displaying evidence retention flags on the left and generated permission review repo...
- 2 public reference cases
- 2 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
- LangGraph · Optional
- LangGraph · 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.