Build a Return Proof Evidence Reconciler and Seller Response Assembler — implementation

## Build
Cross-reference buyer damage evidence against courier delivery logs and seller packaging manifests. Synthesize structured dispute response dossiers for Beckn arbitration.

## User
E-commerce seller dispute specialist

## Workflow
1. Ingest contested buyer return claims and attached synthetic photo metadata from Beckn callbacks.
2. Compare delivery timestamp signatures against original courier proof-of-delivery records.
3. Evaluate seller pre-shipment packaging weigh-in logs against claimed transit damage patterns.
4. Assemble an objective dispute response dossier with recommended settlement terms for seller review.

## Interface
Split-screen evidence comparator showing pre-shipment weights, delivery photos, and draft Beckn response.

## Data
Synthesize paired pre-shipment warehouse logs, proof-of-delivery telemetry, and buyer return files.
Starter examples below are synthetic. They are not downloaded records.

## Source
[Beckn protocol specifications](https://raw.githubusercontent.com/beckn/protocol-specifications/master/README.md)
Adopts Beckn Core 1.0.0 post-fulfillment feedback, dispute response, and callback message structures.

## Tools
crewai, pydantic, fastapi.
Orchestrates specialized agent roles for courier audit, packaging analysis, and legal dispute drafting.
Local Llama 3 or hosted Claude model for dispute evidence extraction and response generation.

## Deliverables
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.

## Acceptance
- Match return claims against courier tracking events and pre-dispatch weight manifests.
- Calculate dimensional and weight discrepancies to detect transit tampering.
- Generate compliant Beckn response payloads containing dispute evidence attachments.
- Require merchant dispute specialist authorization before transmitting responses.

## Starter Examples
```json
[
  {
    "input": {
      "dispute_id": "DISP-552",
      "buyer_claim": "Received empty box without high-value silk sari",
      "dispatch_weight_kg": 1.25,
      "delivery_weight_kg": 0.35,
      "carrier_seal_intact": false
    },
    "expected_output": {
      "tampering_detected": true,
      "liability_assignment": "LOGISTICS_PROVIDER",
      "seller_reimbursement_eligible": true,
      "recommended_settlement": "FULL_BUYER_REFUND_VIA_CARRIER_INSURANCE",
      "beckn_status": "dispute_rebuttal_drafted"
    }
  },
  {
    "input": {
      "dispute_id": "DISP-881",
      "buyer_claim": "Broken ceramic bowl inside sealed container",
      "dispatch_weight_kg": 2.1,
      "delivery_weight_kg": 2.1,
      "carrier_seal_intact": true
    },
    "expected_output": {
      "tampering_detected": false,
      "liability_assignment": "SELLER_PACKAGING",
      "seller_reimbursement_eligible": false,
      "recommended_settlement": "SELLER_REPLACEMENT",
      "beckn_status": "dispute_accepted"
    }
  }
]
```

## Safety
Maintains mock dispute proceedings; does not issue financial debits or make binding judicial rulings.
Use mock external writes. Require human review before any real deployment.