Skip to main content
Challenge

Build a Policy Change Monitoring and Implementation Agent

Build an agent that compares a supplied rule feed with company policies and creates a policy-change work queue. Explain applicability, identify gaps, and draft owner-assigned updates with evidence.

Business OperationsHosted by Vera
Challenge brief

What you are building

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

A governance team tracking rule changes and internal policy updates.

Build an agent that compares a supplied rule feed with company policies and creates a policy-change work queue. Explain applicability, identify gaps, and draft owner-assigned updates with evidence.

Versioned rule records

Internal policy register

Company scope and policy owners

Classify rule versions, status, and effective dates.

Determine applicability using the supplied company profile.

Compare applicable requirements with current policies.

Draft a gap report and assign proposed work to policy owners.

A rule-change dashboard with applicability decisions, policy comparisons, proposed edits, and owner assignments.

Create a proposed quarterly review update for P1 assigned to IT Governance, and keep R2 on a monitoring list.

A working local application with the specified review interface.

Source code, dependency lockfile, and setup commands.

A recorded end-to-end demo using the supplied starter data.

Example outputs, action logs, and automated tests.

These fictional records are a small development fixture, not a production dataset. Implement the mock services described in the brief.

```json { "as_of": "2026-09-19", "company_scope": "Region A", "rules": [ { "id": "R1", "scope": "Region A", "status": "final", "effective": "2026-09-01", "requires": "quarterly access review" }, { "id": "R2", "scope": "Region A", "status": "proposal", "requires": "monthly access review" } ], "policies": [ { "id": "P1", "control": "annual access review", "owner": "IT Governance" } ] } ```

Use fictional requirements. Do not represent the result as actual legal compliance advice. Choose an available model that supports your implementation. Record its identifier and version.

Review the complete application, not only the starter-case answers.

The gap cites R1 and P1.

R2 is not treated as an effective obligation.

The proposed change has an owner and requires approval. Add one normal case, one incomplete-input case, and one failure-recovery case.

Rules

Participation guide

Use fictional requirements. Do not represent the result as actual legal compliance advice.

Delivery guide

How work is evaluated

Evaluation

Review workflow completion, interface usability, evidence quality, and safe failure handling. No agent execution has been verified.

Submission format

A working local application with the specified review interface. Source code, dependency lockfile, and setup commands. A recorded end-to-end demo using the supplied starter data. Example outputs, action logs, and automated tests.

Datasets

Challenge datasets

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

Learning goals

What you should walk away with

  • Classify rule versions, status, and effective dates.

  • Determine applicability using the supplied company profile.

  • Compare applicable requirements with current policies.

  • Draft a gap report and assign proposed work to policy owners.

Resources and assets

Reference links and supporting material

Dataset notes

Supplied fictional starter records: Versioned rule records, Internal policy register, Company scope and policy owners. The overview includes the complete JSON bundle. Implement local mock services and extend the sample coverage.

Challenge setup

Configuration summary for this challenge.

Challenge input

Input details are not configured.

LlamaIndex

Data framework for LLM applications

Evaluated output

No output checks are configured.

Evaluation checks
  • No evaluation checks are configured.
Configured evaluation evidence
  • 1 public reference case
Configured runtime
  • 1 configured tool

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

Orchestration
  • LlamaIndex ยท Optional

Evaluation contract

  • No evaluation checks are configured.

Reference cases

  • 1 public reference case

Workflow tasks

No workflow tasks are configured.

Recipe freeze marker

No recipe freeze time is recorded.

Frequently Asked Questions about Build a Policy Change Monitoring and Implementation Agent