Implement an Automated Regulatory Change Tracker with Pydantic AI
Financial compliance teams struggle to manually track and map hundreds of updated banking regulations. Build a Pydantic AI compliance tracking agent that parses regulatory RSS and policy updates, maps delta changes to internal controls, and outputs structured XML audit logs with 99% schema validity.
What you are building
The core problem, expected build, and operating context for this challenge.
Build a type-safe Pydantic AI agent that ingests regulatory policy updates and outputs structured XML diffs and control impact mappings.
How work is evaluated
Evaluates XML schema validity and control mapping precision across regulatory updates.
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.
xml_well_formed_test
Output must parse as valid, well-formed XML.
This dimension contributes its full weight only when the submission satisfies the requirement. Partial credit is not awarded.
control_mapping_precision
Precision of assigned compliance control IDs. • target: 0.95 • range: 0.85-1
This dimension contributes its full weight only when the submission satisfies the requirement. Partial credit is not awarded.
What you should walk away with
Build type-safe regulatory trackers using Pydantic AI framework
Parse and diff regulatory updates against internal corporate policy databases
Generate structured, schema-validated XML change logs for compliance audits
Automate email alert notifications to policy owners upon regulatory shifts
Reference links and supporting material
Dataset of 150 regulatory amendment texts and mapped bank internal control standards.
Challenge setup
Evaluates XML schema validity and control mapping precision across regulatory updates.
Challenge input
Text payload of regulatory amendment notice
Pydantic AI
Ensures output format compliance and strict schema parsing.
Evaluated output
XML string containing impacted control IDs and change severity
- Output must parse as valid, well-formed XML.
- Precision of assigned compliance control IDs. • target: 0.95 • range: 0.85-1
- Benchmark: Regulatory Mapping Suite
- Control Mapping Precision target: 0.95
- 1 public reference case
- Python execution harness
- Python sandbox (unavailable on Versalist)
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
- Pydantic AI · Required
- Pydantic AI · Required
Evaluation contract
- xml_well_formed_test · Weight 1
- control_mapping_precision · Weight 1
Metrics
- control_mapping_precision · Target 0.95
Benchmarks
- Regulatory Mapping Suite
- general
Reference cases
- 1 public reference case
Workflow tasks
- Task 1
Input: Text payload of regulatory amendment notice
Output: XML string containing impacted control IDs and change severity
Execution harness: Python
Evaluation tools
- Pydantic AI · Type-Safe Agent Framework
Recipe freeze marker
No recipe freeze time is recorded.