Build a Consent Receipt Lifecycle and Data-Sharing Access Verifier
Inspect standardized digital consent receipts against active merchant data queries across open networks. Verify data disclosure limits, validity horizons, and revocation records to block unauthorized credential requests.
What you are building
The core problem, expected build, and operating context for this challenge.
Inspect standardized digital consent receipts against active merchant data queries across open networks. Verify data disclosure limits, validity horizons, and revocation records to block unauthorized credential requests.
Enterprise privacy and compliance officer
Ingest mock structured consent receipts conforming to electronic consent specifications and Beckn context headers.
Parse requester service types, data purpose codes, and permitted attribute retrieval scopes.
Cross-examine incoming buyer application data requests against active revocation registries.
Export verifiable consent compliance scorecards and quarantine non-compliant data access requests.
Compliance log console with policy rule match meters, access permit diffs, and revocation lookup status.
Generate synthetic JSON consent artifacts and sample data fetch requests modeling standard open network interactions. Starter examples below are synthetic. They are not downloaded records.
Beckn protocol specifications Adopts Beckn context header attributes (bap_id, bpp_id, timestamp) to establish consent transaction boundaries.
pydantic-ai, fastapi, pytest. Guarantees strict schema conformity and cryptographic field integrity on incoming consent receipt objects. Structured JSON reasoning model accessed via standard API or local Ollama endpoint.
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.
Detects expired consent artifacts based on timestamp and validity duration checks.
Identifies data scope overreach when queries request attributes omitted from the initial consent receipt.
Flags revoked consent handles immediately prior to data fetch dispatch.
```json [ { "input": { "receipt_id": "CR-7721", "granted_to": "bap.network.in/health", "purpose_code": "TELEMED_CONSULT", "permitted_fields": [ "allergies", "active_medications" ], "valid_until": "2024-12-31T23:59:59Z", "status": "active", "request_payload": { "requested_fields": [ "allergies", "active_medications" ] } }, "expected_output": { "verdict": "permitted", "scope_violation": false, "expired": false, "audit_code": "CONSENT_OK" } }, { "input": { "receipt_id": "CR-7722", "granted_to": "bap.network.in/retail", "purpose_code": "DELIVERY_FULFILLMENT", "permitted_fields": [ "shipping_address" ], "valid_until": "2024-12-31T23:59:59Z", "status": "revoked", "request_payload": { "requested_fields": [ "shipping_address", "phone_number" ] } }, "expected_output": { "verdict": "blocked", "scope_violation": true, "expired": false, "audit_code": "CONSENT_REVOKED_AND_SCOPE_BREACH" } } ] ```
Maintains a simulated policy review sandbox; does not process actual identity credentials or health records. Use mock external writes. Require human review before any real deployment.
Participation guide
Maintains a simulated policy review sandbox; does not process actual identity credentials or health records. Use mock external writes and human review.
How work is evaluated
Detects expired consent artifacts based on timestamp and validity duration checks. Identifies data scope overreach when queries request attributes omitted from the initial consent receipt. Flags revoked consent handles immediately prior to data fetch dispatch.
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 mock structured consent receipts conforming to electronic consent specifications and Beckn context headers. Parse requester service types, data purpose codes, and permitted attribute retrieval scopes. Cross-examine incoming buyer application data requests against active revocation registries. Export verifiable consent compliance scorecards and quarantine non-compliant data access requests.
Missing or incorrect.
Partly complete, with documented gaps.
Complete, with reproducible evidence.
Correctness and evidence
Detects expired consent artifacts based on timestamp and validity duration checks. Identifies data scope overreach when queries request attributes omitted from the initial consent receipt. Flags revoked consent handles immediately prior to data fetch dispatch.
Missing or incorrect.
Partly complete, with documented gaps.
Complete, with reproducible evidence.
Review interface
Compliance log console with policy rule match meters, access permit diffs, and revocation lookup status.
Missing or incorrect.
Partly complete, with documented gaps.
Complete, with reproducible evidence.
Safe execution
Maintains a simulated policy review sandbox; does not process actual identity credentials or health records.
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 mock structured consent receipts conforming to electronic consent specifications and Beckn context headers.
Parse requester service types, data purpose codes, and permitted attribute retrieval scopes.
Cross-examine incoming buyer application data requests against active revocation registries.
Export verifiable consent compliance scorecards and quarantine non-compliant data access requests.
Reference links and supporting material
Generate synthetic JSON consent artifacts and sample data fetch requests modeling standard open network interactions. 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.
- Ingest mock structured consent receipts conforming to electronic consent specifications and Beckn context h...
- Detects expired consent artifacts based on timestamp and validity duration checks. Identifies data scope ov...
- Compliance log console with policy rule match meters, access permit diffs, and revocation lookup status.
- 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
- Pydantic AI · Optional
- 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.