Build the application

## Build
Evaluate vendor compliance onboarding documents using Frictionless Data resource schemas. Monitor expiration horizons for liability policies, tax certificates, and operating licenses to assemble automated re-certification notifications.

## User
Vendor Due Diligence Officer

## Workflow
1. Ingest supplier metadata and document package manifests defined as Frictionless Data Resource tables.
2. Validate document tables against schema constraints including license numbers, issuance dates, and expiration horizons.
3. Identify expired credentials and certificates approaching 30-day expiration thresholds across active suppliers.
4. Assemble structured supplier renewal tickets and warning packets specifying exact deficient document types.

## Interface
A tabular status view highlighting expiring certificates with an automated notification draft preview drawer.

## Data
Fictional CSV supplier document ledgers validated via Frictionless Python using synthetic corporate tax and insurance records.
Starter examples below are synthetic. They are not downloaded records.

## Source
[Frictionless data validation](https://raw.githubusercontent.com/frictionlessdata/frictionless-py/main/README.md)
Employs Frictionless Data Python validation routines, Table Schema specifications, and resource validation reports.

## Tools
langgraph, frictionless, pydantic.
LangGraph manages stateful multi-step cycles: schema validation, threshold calculation, and notice draft creation.
Standard API-hosted model for crafting concise formal vendor notification texts based on structured validation errors.

## 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
- Executes schema validation using frictionless-py without uncaught parsing exceptions on dirty input tables.
- Correctly flags documents where expiry_date is within 30 days or in the past.
- Generates structured renewal packets containing supplier contact ID, deficient certificate codes, and remediation deadlines.

## Starter Examples
```json
[
  {
    "input": {
      "supplier_id": "SUP-772",
      "documents": [
        {
          "doc_type": "INSURANCE_LIABILITY",
          "doc_id": "INS-99",
          "expiry_date": "2024-01-15",
          "status": "active"
        },
        {
          "doc_type": "TAX_CERTIFICATE",
          "doc_id": "TAX-12",
          "expiry_date": "2026-12-31",
          "status": "active"
        }
      ],
      "evaluation_date": "2024-02-01"
    },
    "expected_output": {
      "supplier_id": "SUP-772",
      "overall_status": "NON_COMPLIANT_EXPIRED",
      "expired_documents": [
        "INS-99"
      ],
      "expiring_soon": [],
      "action_ticket_generated": true
    }
  },
  {
    "input": {
      "supplier_id": "SUP-880",
      "documents": [
        {
          "doc_type": "ISO_9001",
          "doc_id": "ISO-01",
          "expiry_date": "2025-05-10",
          "status": "active"
        }
      ],
      "evaluation_date": "2024-02-01"
    },
    "expected_output": {
      "supplier_id": "SUP-880",
      "overall_status": "COMPLIANT",
      "expired_documents": [],
      "expiring_soon": [],
      "action_ticket_generated": false
    }
  }
]
```

## Safety
Performs administrative supplier document auditing without commercial vendor termination or autonomous account blocking.
Use mock external writes. Require human review before any real deployment.