Skip to main content
Challenge

Build a Trade Document Endorsement and Evidence Request Workspace

Review trade invoices and delivery proofs for missing digital endorsements. Construct TradeTrust verification queries and dispatch structured evidence requests to counterparties.

Business OperationsHosted by Vera
Challenge brief

What you are building

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

Review trade invoices and delivery proofs for missing digital endorsements. Construct TradeTrust verification queries and dispatch structured evidence requests to counterparties.

Trade finance operations analyst

Inspect trade document bundles containing bills of lading, commercial invoices, and inspection notes.

Validate cryptographic signatures and DNS-TXT identity proofs against TradeTrust specifications.

Identify missing endorsement chains, unverified counterparties, or altered hashes.

Generate structured evidence requests and notification dossiers for counterparty compliance.

Split-view workspace presenting document provenance tree, signature verification indicators, and an interactive evidence request drafter.

Synthesize normalized trade document envelopes utilizing TradeTrust test fixture formats from source 1. Starter examples below are synthetic. They are not downloaded records.

TradeTrust Adheres to TradeTrust DNS-TXT identity proof validation and document store verification specifications.

mastra-ai, ethers, zod. Mastra AI orchestrates deterministic schema verification tools combined with agentic evidence gap reporting. Instruction-tuned hosted model with structured JSON formatting and high extraction consistency.

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.

Verifies Secp256k1 digital signatures and DNS-TXT bindings on incoming trade packets.

Flags unendorsed bills of lading when transfer of ownership proofs are missing.

Drafts counterparty requests specifying precise missing document fields.

Outputs verifiable compliance status reports for audit logs.

```json [ { "input": { "document_id": "BL-SGP-2025-001", "document_type": "BillOfLading", "issuers": [ { "name": "PSA Logistics", "identityProof": { "type": "DNS-TXT", "location": "tradetrust.io" }, "has_endorsement": true } ], "transferee": "SingaTech Trading Pte Ltd" }, "expected_output": { "verification_status": "VALID", "missing_endorsements": [], "action_required": "PROCEED_TO_SETTLEMENT", "evidence_request_generated": false } }, { "input": { "document_id": "INV-MY-SGP-992", "document_type": "CommercialInvoice", "issuers": [ { "name": "Johor Agro Ltd", "identityProof": { "type": "DNS-TXT", "location": "unregistered-domain.xyz" }, "has_endorsement": false } ], "transferee": "SingaTech Trading Pte Ltd" }, "expected_output": { "verification_status": "FLAGGED", "missing_endorsements": [ "DNS_IDENTITY_MISMATCH", "MISSING_COUNTERPARTY_SIGNATURE" ], "action_required": "REQUEST_EVIDENCE", "evidence_request_generated": true } } ] ```

No real financial clearing or legal ownership transfer occurs; all endorsements are evaluated in a local sandbox. Use mock external writes. Require human review before any real deployment.

Rules

Participation guide

No real financial clearing or legal ownership transfer occurs; all endorsements are evaluated in a local sandbox. Use mock external writes and human review.

Delivery guide

How work is evaluated

Evaluation

Verifies Secp256k1 digital signatures and DNS-TXT bindings on incoming trade packets. Flags unendorsed bills of lading when transfer of ownership proofs are missing. Drafts counterparty requests specifying precise missing document fields. Outputs verifiable compliance status reports for audit logs.

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

Inspect trade document bundles containing bills of lading, commercial invoices, and inspection notes. Validate cryptographic signatures and DNS-TXT identity proofs against TradeTrust specifications. Identify missing endorsement chains, unverified counterparties, or altered hashes. Generate structured evidence requests and notification dossiers for counterparty compliance.

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

Verifies Secp256k1 digital signatures and DNS-TXT bindings on incoming trade packets. Flags unendorsed bills of lading when transfer of ownership proofs are missing. Drafts counterparty requests specifying precise missing document fields. Outputs verifiable compliance status reports for audit logs.

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-view workspace presenting document provenance tree, signature verification indicators, and an interactive evidence request drafter.

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

No real financial clearing or legal ownership transfer occurs; all endorsements are evaluated in a local sandbox.

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

  • Inspect trade document bundles containing bills of lading, commercial invoices, and inspection notes.

  • Validate cryptographic signatures and DNS-TXT identity proofs against TradeTrust specifications.

  • Identify missing endorsement chains, unverified counterparties, or altered hashes.

  • Generate structured evidence requests and notification dossiers for counterparty compliance.

Resources and assets

Reference links and supporting material

Dataset notes

Synthesize normalized trade document envelopes utilizing TradeTrust test fixture formats from source 1. Supplied starter examples are synthetic, not source extracts.

Challenge setup

Configuration summary for this challenge.

Challenge input

Input details are not configured.

Mastra AI

TypeScript agent framework.

Evaluated output

No output checks are configured.

Evaluation checks
  • Inspect trade document bundles containing bills of lading, commercial invoices, and inspection notes. Valid...
  • Verifies Secp256k1 digital signatures and DNS-TXT bindings on incoming trade packets. Flags unendorsed bill...
  • Split-view workspace presenting document provenance tree, signature verification indicators, and an interac...
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
  • Mastra AI · Optional
Orchestration
  • Mastra 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 Trade Document Endorsement and Evidence Request Workspace