Build an OpenFEMA Coastal Surge Claim Evidence Compiler
Correlate maritime port property loss claims against historical OpenFEMA disaster declarations and flood incident reports. Validate incident dates and county eligibility to prepare clean dossiers for independent claim adjusters.
What you are building
The core problem, expected build, and operating context for this challenge.
Correlate maritime port property loss claims against historical OpenFEMA disaster declarations and flood incident reports. Validate incident dates and county eligibility to prepare clean dossiers for independent claim adjusters.
Marine Insurance Claim Preparer
Receive commercial property claim metadata including loss date, damage scope, and county.
Dispatch OData query to OpenFEMA DisasterDeclarationsSummaries for the designated state and county.
Check temporal alignment between asserted loss dates and official declared incident windows.
Assemble structured claim validation packages highlighting verified disaster numbers and inconsistencies.
Next.js claims portal featuring declaration verification timelines and exportable evidence packages.
Query live OpenFEMA API endpoints with fallback to local mock JSON responses. Starter examples below are synthetic. They are not downloaded records.
FEMA OpenFEMA Use OpenFEMA query syntax with $filter ge/le date operators and incidentType matching.
dspy, httpx, pydantic. DSPy compiles robust prompt pipelines to extract and cross-reference loss narratives with FEMA dates. Instruction-tuned LLM capable of strict schema-compliant evidence synthesis.
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.
Parses ISO-8601 incident dates correctly from OpenFEMA records.
Detects claim loss dates falling outside official disaster declaration intervals.
Generates clean claim dossier with FEMA disaster number reference.
```json [ { "input": { "claim_id": "CLM-HURR-991", "county": "Galveston", "state": "TX", "loss_date": "2024-07-08T14:00:00Z", "fema_declarations": [ { "disasterNumber": 4798, "incidentBeginDate": "2024-07-05T00:00:00.000Z", "incidentEndDate": "2024-07-12T00:00:00.000Z", "designatedCounty": "Galveston" } ] }, "expected_output": { "claim_id": "CLM-HURR-991", "disaster_number": 4798, "temporal_alignment": "VALID_WITHIN_INCIDENT_WINDOW", "county_eligible": true, "claim_preparation_status": "READY_FOR_ADJUSTER" } }, { "input": { "claim_id": "CLM-HURR-992", "county": "Harris", "state": "TX", "loss_date": "2024-08-15T10:00:00Z", "fema_declarations": [ { "disasterNumber": 4798, "incidentBeginDate": "2024-07-05T00:00:00.000Z", "incidentEndDate": "2024-07-12T00:00:00.000Z", "designatedCounty": "Harris" } ] }, "expected_output": { "claim_id": "CLM-HURR-992", "disaster_number": null, "temporal_alignment": "OUTSIDE_DECLARED_INCIDENT_WINDOW", "county_eligible": true, "claim_preparation_status": "FLAGGED_DATE_MISMATCH" } } ] ```
Does not approve or deny claims; prepares organized evidence packages for certified human adjusters. Use mock external writes. Require human review before any real deployment.
Participation guide
Does not approve or deny claims; prepares organized evidence packages for certified human adjusters. Use mock external writes and human review.
How work is evaluated
Parses ISO-8601 incident dates correctly from OpenFEMA records. Detects claim loss dates falling outside official disaster declaration intervals. Generates clean claim dossier with FEMA disaster number reference.
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
Receive commercial property claim metadata including loss date, damage scope, and county. Dispatch OData query to OpenFEMA DisasterDeclarationsSummaries for the designated state and county. Check temporal alignment between asserted loss dates and official declared incident windows. Assemble structured claim validation packages highlighting verified disaster numbers and inconsistencies.
Missing or incorrect.
Partly complete, with documented gaps.
Complete, with reproducible evidence.
Correctness and evidence
Parses ISO-8601 incident dates correctly from OpenFEMA records. Detects claim loss dates falling outside official disaster declaration intervals. Generates clean claim dossier with FEMA disaster number reference.
Missing or incorrect.
Partly complete, with documented gaps.
Complete, with reproducible evidence.
Review interface
Next.js claims portal featuring declaration verification timelines and exportable evidence packages.
Missing or incorrect.
Partly complete, with documented gaps.
Complete, with reproducible evidence.
Safe execution
Does not approve or deny claims; prepares organized evidence packages for certified human adjusters.
This dimension contributes its full weight only when the submission satisfies the requirement. Partial credit is not awarded.
What you should walk away with
Receive commercial property claim metadata including loss date, damage scope, and county.
Dispatch OData query to OpenFEMA DisasterDeclarationsSummaries for the designated state and county.
Check temporal alignment between asserted loss dates and official declared incident windows.
Assemble structured claim validation packages highlighting verified disaster numbers and inconsistencies.
Reference links and supporting material
Query live OpenFEMA API endpoints with fallback to local mock JSON responses. Supplied starter examples are synthetic, not source extracts.
Challenge setup
Configuration summary for this challenge.
Challenge input
Input details are not configured.
DSPy
Prompt and LM program optimization framework.
Evaluated output
No output checks are configured.
- Receive commercial property claim metadata including loss date, damage scope, and county. Dispatch OData qu...
- Parses ISO-8601 incident dates correctly from OpenFEMA records. Detects claim loss dates falling outside of...
- Next.js claims portal featuring declaration verification timelines and exportable evidence packages.
- 2 public reference cases
- 3 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
- DSPy · Optional
- DSPy · Optional
- DSPy · 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.