Skip to main content
Challenge

Build a BODS Terminal Natural Person Verification Profiler

Traverse multi-tier BODS ownership declarations to identify holding structures lacking terminal natural person nodes. Formulate missing verification alerts based on entity termination types.

CybersecurityHosted by Vera
Challenge brief

What you are building

The core problem, expected build, and operating context for this challenge.

Traverse multi-tier BODS ownership declarations to identify holding structures lacking terminal natural person nodes. Formulate missing verification alerts based on entity termination types.

Corporate Transparency Compliance Analyst

Ingest simplified normalized BODS v0.4 ownership statements.

Traverse corporate holding paths to locate terminal entity nodes.

Evaluate terminal node properties to confirm natural person identifier status.

Generate precise evidence requests for paths terminating in unverified corporate vehicles.

A tabular tree view visualizing holding chains alongside highlighted missing ultimate beneficial owners.

Mock BODS v0.4 JSON datasets representing multi-jurisdiction ownership chains with varying equity stakes. Starter examples below are synthetic. They are not downloaded records.

Beneficial Ownership Data Standard BODS v0.4 data model, schema definitions, and entity interest representations.

pydantic-ai, fastapi, networkx. Validates BODS v0.4 data models and structures verified calculation payloads. Structured JSON reasoning model via API or local runner.

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.

Traverses multi-level corporate entity structures to identify terminal nodes.

Flags holding chains that end in corporate vehicles without a natural person.

Produces verification alerts targeted at the terminal entity for RFI follow-up.

```json [ { "input": { "subject_entity": "Apex Holdings LLC", "ownership_statements": [ { "entity": "Apex Holdings LLC", "held_by": "MidCo Ltd" }, { "entity": "MidCo Ltd", "held_by": "Unknown Trust" } ] }, "expected_output": { "subject_entity": "Apex Holdings LLC", "terminal_paths": [ { "path": [ "Unknown Trust", "MidCo Ltd", "Apex Holdings LLC" ], "terminal_node": "Unknown Trust", "is_natural_person": false } ], "rfi_required_for": [ "Unknown Trust" ] } }, { "input": { "subject_entity": "Clearwater Corp", "ownership_statements": [ { "entity": "Clearwater Corp", "held_by": "Jane Doe" } ] }, "expected_output": { "subject_entity": "Clearwater Corp", "terminal_paths": [ { "path": [ "Jane Doe", "Clearwater Corp" ], "terminal_node": "Jane Doe", "is_natural_person": true } ], "rfi_required_for": [] } } ] ```

Maintains non-punitive due diligence posture; does not execute direct corporate freeze requests. Use mock external writes. Require human review before any real deployment.

Rules

Participation guide

Maintains non-punitive due diligence posture; does not execute direct corporate freeze requests. Use mock external writes and human review.

Delivery guide

How work is evaluated

Evaluation

Traverses multi-level corporate entity structures to identify terminal nodes. Flags holding chains that end in corporate vehicles without a natural person. Produces verification alerts targeted at the terminal entity for RFI follow-up.

Submission format

Runnable source, pinned dependencies, setup commands, working interface, example outputs, recorded demo, tests, and action logs.

Datasets

Challenge datasets

Public datasets, plus the private datasets you have access to.

Evaluation rubric

How submissions are scored

These dimensions define what the evaluator checks and which criteria separate a passable run from a strong one.

Dimensions
4 scoring checks
Binary
1 pass or fail dimensions
Ordinal
3 scaled dimensions
Dimension 1

Complete workflow

Ingest simplified normalized BODS v0.4 ownership statements. Traverse corporate holding paths to locate terminal entity nodes. Evaluate terminal node properties to confirm natural person identifier status. Generate precise evidence requests for paths terminating in unverified corporate vehicles.

Score scale
012
Score 0

Missing or incorrect.

Score 1

Partly complete, with documented gaps.

Score 2

Complete, with reproducible evidence.

Dimension 2

Correctness and evidence

Traverses multi-level corporate entity structures to identify terminal nodes. Flags holding chains that end in corporate vehicles without a natural person. Produces verification alerts targeted at the terminal entity for RFI follow-up.

Score scale
012
Score 0

Missing or incorrect.

Score 1

Partly complete, with documented gaps.

Score 2

Complete, with reproducible evidence.

Dimension 3

Review interface

A tabular tree view visualizing holding chains alongside highlighted missing ultimate beneficial owners.

Score scale
012
Score 0

Missing or incorrect.

Score 1

Partly complete, with documented gaps.

Score 2

Complete, with reproducible evidence.

Dimension 4

Safe execution

Maintains non-punitive due diligence posture; does not execute direct corporate freeze requests.

Binary check

This dimension contributes its full weight only when the submission satisfies the requirement. Partial credit is not awarded.

Learning goals

What you should walk away with

  • Ingest simplified normalized BODS v0.4 ownership statements.

  • Traverse corporate holding paths to locate terminal entity nodes.

  • Evaluate terminal node properties to confirm natural person identifier status.

  • Generate precise evidence requests for paths terminating in unverified corporate vehicles.

Resources and assets

Reference links and supporting material

Dataset notes

Mock BODS v0.4 JSON datasets representing multi-jurisdiction ownership chains with varying equity stakes. Supplied starter examples are synthetic, not source extracts.

Challenge setup

Configuration summary for this challenge.

Challenge input

Input details are not configured.

Pydantic AI

Typed Python agent framework.

Evaluated output

No output checks are configured.

Evaluation checks
  • Ingest simplified normalized BODS v0.4 ownership statements. Traverse corporate holding paths to locate ter...
  • Traverses multi-level corporate entity structures to identify terminal nodes. Flags holding chains that end...
  • A tabular tree view visualizing holding chains alongside highlighted missing ultimate beneficial owners.
Configured evaluation evidence
  • 2 public reference cases
Configured runtime
  • 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

Action Space
  • Pydantic AI · Optional
Orchestration
  • Pydantic AI · 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.

Frequently Asked Questions about Build a BODS Terminal Natural Person Verification Profiler