Build the application

## Build
Develop a vessel-owner legal entity evidence briefing tool that joins synthetic vessel manifests with GLEIF entity data. Standardize fragmented maritime ownership formats using automated reconciliation to prevent incomplete global compliance profiles.

## User
Maritime compliance officer

## Workflow
1. Ingest synthetic vessel manifest records containing raw owner entity names and registration details.
2. Query a synthetic GLEIF API Golden Copy using fuzzy matching to reconcile the raw owner entity strings.
3. Extract canonical Legal Entity Identifiers (LEIs) and registration status for mapped maritime companies.
4. Output a vessel-owner legal entity evidence briefing combining the manifest data with verified LEI attributes.

## Interface
Dashboard displaying reconciled vessel manifests, LEI matches, and alerts for orphaned maritime entities.

## Data
Generate synthetic vessel manifests in JSON format paired with mock GLEIF API responses containing standard LEI structures.
Starter examples below are synthetic. They are not downloaded records.

## Source
[GLEIF API](https://www.gleif.org/en/lei-data/gleif-api)
References GLEIF API capabilities for searching and mapping unstructured entity strings to standardized LEI records.

## Tools
mastra-ai, pydantic, httpx, pandas.
Provides workflow orchestration to manage API polling, entity string matching, and report generation logic.
General LLM for parsing fuzzy entity names and drafting the evidence briefing payload.

## 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
- Successfully matches and retrieves canonical LEIs from the synthetic GLEIF API data.
- Merges vessel manifest attributes seamlessly with standardized legal entity identifiers.
- Generates an evidence briefing payload correctly tracking harmonization success and unmatched entity alerts.

## Starter Examples
```json
[
  {
    "input": {
      "manifest": {
        "vessel_name": "Sea Breeze",
        "mmsi": "123456789",
        "declared_owner": "Zephyr Holding Services Ltd"
      },
      "gleif_api_response": {
        "data": [
          {
            "attributes": {
              "lei": "213800XYZ123456789",
              "entity": {
                "legalName": {
                  "name": "Zephyr Holding Services Limited"
                }
              }
            }
          }
        ]
      }
    },
    "expected_output": {
      "record_type": "simplified synthetic app records, not complete official schema files",
      "vessel_name": "Sea Breeze",
      "harmonization_successful": true,
      "assigned_lei": "213800XYZ123456789",
      "canonical_name": "Zephyr Holding Services Limited"
    }
  },
  {
    "input": {
      "manifest": {
        "vessel_name": "Nordic Trader",
        "mmsi": "987654321",
        "declared_owner": "Nordic Maritime AB"
      },
      "gleif_api_response": {
        "data": []
      }
    },
    "expected_output": {
      "record_type": "simplified synthetic app records, not complete official schema files",
      "vessel_name": "Nordic Trader",
      "harmonization_successful": false,
      "assigned_lei": null,
      "canonical_name": null
    }
  }
]
```

## Safety
Acts as a data enrichment layer; final determinations require human review of official registry documents.
Use mock external writes. Require human review before any real deployment.