Skip to main content
Challenge

Build a Merchant Onboarding Evidence Workspace with Fictional Checklists

Extract identifiers from unstructured notes against fictional onboarding checklist rules. Output normalized draft records for human review before conversion to Beckn catalog schemas.

Workflow AutomationHosted by Vera
Challenge brief

What you are building

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

Extract identifiers from unstructured notes against fictional onboarding checklist rules. Output normalized draft records for human review before conversion to Beckn catalog schemas.

Seller network onboarding specialist

Ingest informal merchant product descriptions and mock checklist configuration rules.

Extract raw text fields like item titles, prices, and alleged license numbers.

Perform format-only validation checks against the provided fictional checklist requirements.

Generate a normalized draft record that mandates human review before a separate versioned Beckn adapter handles schema conversion.

Split-screen review workbench showing source text on the left and extracted draft records on the right for human approval.

Construct synthetic item descriptions and fictional mock checklist JSON rule files for extraction targets. Starter examples below are synthetic. They are not downloaded records.

Beckn protocol specifications Utilizes Beckn protocol core catalog discovery specifications as the target format for approved adapter exports.

pydantic-ai, fastapi, pandas. Pydantic AI provides structured extraction capabilities for parsing raw text into normalized draft schema objects based on custom checklist rules. Local or hosted LLM with strong extraction and structured object generation capabilities.

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.

Extracts specified product details into a draft schema without asserting legal compliance.

Flags records lacking fictional checklist items for human review instead of triggering automatic rejection.

Never outputs a COMPLIANT status or automatic onboarding approval for any generated record.

Requires explicit human-in-the-loop signoff on the generated draft outputs.

```json [ { "input": { "raw_text": "Mustard Oil 1L. MRP 240. Lic No: 12345678901234.", "checklist_keys": [ "name", "price", "license_code" ] }, "expected_output": { "draft_record": { "name": "Mustard Oil 1L", "price": "240", "license_code_extracted": "12345678901234", "format_check": "passed" }, "requires_human_review": true, "note": "Simplified synthetic app record, not a complete official schema file." } }, { "input": { "raw_text": "Pickle Jar. Very tasty mango.", "checklist_keys": [ "name", "price", "license_code" ] }, "expected_output": { "draft_record": { "name": "Pickle Jar", "price": null, "license_code_extracted": null, "format_check": "missing_fields" }, "requires_human_review": true, "note": "Simplified synthetic app record, not a complete official schema file." } } ] ```

Evaluates synthetic item catalogs; does not connect to live commercial marketplaces or collect proprietary banking data. Use mock external writes. Require human review before any real deployment.

Rules

Participation guide

Evaluates synthetic item catalogs; does not connect to live commercial marketplaces or collect proprietary banking data. Use mock external writes and human review.

Delivery guide

How work is evaluated

Evaluation

Extracts specified product details into a draft schema without asserting legal compliance. Flags records lacking fictional checklist items for human review instead of triggering automatic rejection. Never outputs a COMPLIANT status or automatic onboarding approval for any generated record. Requires explicit human-in-the-loop signoff on the generated draft outputs.

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 informal merchant product descriptions and mock checklist configuration rules. Extract raw text fields like item titles, prices, and alleged license numbers. Perform format-only validation checks against the provided fictional checklist requirements. Generate a normalized draft record that mandates human review before a separate versioned Beckn adapter handles schema conversion.

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

Extracts specified product details into a draft schema without asserting legal compliance. Flags records lacking fictional checklist items for human review instead of triggering automatic rejection. Never outputs a COMPLIANT status or automatic onboarding approval for any generated record. Requires explicit human-in-the-loop signoff on the generated draft outputs.

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

Split-screen review workbench showing source text on the left and extracted draft records on the right for human approval.

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

Evaluates synthetic item catalogs; does not connect to live commercial marketplaces or collect proprietary banking data.

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 informal merchant product descriptions and mock checklist configuration rules.

  • Extract raw text fields like item titles, prices, and alleged license numbers.

  • Perform format-only validation checks against the provided fictional checklist requirements.

  • Generate a normalized draft record that mandates human review before a separate versioned Beckn adapter handles schema conversion.

Resources and assets

Reference links and supporting material

Dataset notes

Construct synthetic item descriptions and fictional mock checklist JSON rule files for extraction targets. 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 informal merchant product descriptions and mock checklist configuration rules. Extract raw text fiel...
  • Extracts specified product details into a draft schema without asserting legal compliance. Flags records la...
  • Split-screen review workbench showing source text on the left and extracted draft records on the right for...
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 Merchant Onboarding Evidence Workspace with Fictional Checklists