Build an OCDS Contracting Release Package Auditor
Parse Open Contracting Data Standard (OCDS) release packages to validate package metadata and release array structure. Detect missing publisher URIs, schema versions, and invalid release compilation structures.
What you are building
The core problem, expected build, and operating context for this challenge.
Parse Open Contracting Data Standard (OCDS) release packages to validate package metadata and release array structure. Detect missing publisher URIs, schema versions, and invalid release compilation structures.
Procurement Transparency Analyst
Ingest OCDS release package JSON files representing published procurement events.
Evaluate the root package metadata including URI, publisher details, and schema version.
Traverse the releases array to ensure each release contains the required structure and ID.
Compile an audit report flagging non-compliant or missing package metadata.
Browser validation dashboard showing package metadata compliance status and release ID listings.
Generate synthetic OCDS release packages containing valid and invalid root metadata structures. Starter examples below are synthetic. They are not downloaded records.
Open Contracting Data Standard Implements the OCDS Release Package structure, enforcing required fields such as uri, version, publishedDate, releases, and publisher.
langgraph, pandas, fastapi. LangGraph manages stateful traversal and validation workflows across multi-stage schema auditing pipelines. Hosted reasoning model capable of interpreting JSON schema structures and validating required metadata fields.
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 presence of required package metadata fields (uri, publishedDate, publisher, version).
Ensures releases array is present and contains at least one release object.
Produces a structured JSON error report for missing metadata.
```json [ { "input": { "uri": "http://example.com/ocds/package-1", "version": "1.1", "publishedDate": "2023-10-01T12:00:00Z", "publisher": { "name": "City Procurement" }, "releases": [ { "id": "release-1", "ocid": "ocds-213-1" } ] }, "expected_output": { "package_valid": true, "missing_fields": [], "release_count": 1, "status": "COMPLIANT", "note": "Simplified synthetic app records, not complete official schema files." } }, { "input": { "version": "1.1", "publishedDate": "2023-10-01T12:00:00Z", "publisher": { "name": "City Procurement" }, "releases": [] }, "expected_output": { "package_valid": false, "missing_fields": [ "uri" ], "release_count": 0, "status": "NON_COMPLIANT_EMPTY_RELEASES", "note": "Simplified synthetic app records, not complete official schema files." } } ] ```
Acts as an analytical project management tool without executing real-world contractual or site dispatch actions. Use mock external writes. Require human review before any real deployment.
Participation guide
Acts as an analytical project management tool without executing real-world contractual or site dispatch actions. Use mock external writes and human review.
How work is evaluated
Validates presence of required package metadata fields (uri, publishedDate, publisher, version). Ensures releases array is present and contains at least one release object. Produces a structured JSON error report for missing metadata.
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 OCDS release package JSON files representing published procurement events. Evaluate the root package metadata including URI, publisher details, and schema version. Traverse the releases array to ensure each release contains the required structure and ID. Compile an audit report flagging non-compliant or missing package metadata.
Missing or incorrect.
Partly complete, with documented gaps.
Complete, with reproducible evidence.
Correctness and evidence
Validates presence of required package metadata fields (uri, publishedDate, publisher, version). Ensures releases array is present and contains at least one release object. Produces a structured JSON error report for missing metadata.
Missing or incorrect.
Partly complete, with documented gaps.
Complete, with reproducible evidence.
Review interface
Browser validation dashboard showing package metadata compliance status and release ID listings.
Missing or incorrect.
Partly complete, with documented gaps.
Complete, with reproducible evidence.
Safe execution
Acts as an analytical project management tool without executing real-world contractual or site dispatch actions.
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 OCDS release package JSON files representing published procurement events.
Evaluate the root package metadata including URI, publisher details, and schema version.
Traverse the releases array to ensure each release contains the required structure and ID.
Compile an audit report flagging non-compliant or missing package metadata.
Reference links and supporting material
Generate synthetic OCDS release packages containing valid and invalid root metadata structures. 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.
- Ingest OCDS release package JSON files representing published procurement events. Evaluate the root package...
- Validates presence of required package metadata fields (uri, publishedDate, publisher, version). Ensures re...
- Browser validation dashboard showing package metadata compliance status and release ID listings.
- 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.