Build an OCDS Procurement Implementation Document Auditor — implementation

## Build
Cross-reference OCDS procurement implementation releases against vendor certification registries. Flag active projects where required insurance credentials expire during the physical delivery phase.

## User
A public-contract implementation milestone evidence request coordinator for oversight teams.

## Workflow
1. Parse OCDS releases focusing on contract and implementation milestone arrays.
2. Match contracted supplier identifiers against internal vendor credential registries.
3. Compare implementation execution dates against supplier document expiration timestamps.
4. Assemble an implementation audit memo highlighting active contracts with lapsed certificates.

## Interface
A contract award staging interface listing tender parties, documentation validity dates, and exception notices.

## Data
Utilize open sample releases from the Open Contracting Data Standard repository alongside mock supplier certificate files.
Starter examples below are synthetic. They are not downloaded records.

## Source
[Open Contracting Data Standard](https://standard.open-contracting.org/latest/en/schema/reference/)
Parse OCDS release schema sections including parties, awards, and supplier organization references.

## Tools
qdrant, pydantic, fastapi.
Qdrant enables vector similarity lookup across multi-lingual supplier names and tender descriptions.
Local or hosted embedding model for semantic party matching.

## 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
- Parses OCDS release JSON payloads extracting parties with supplier roles.
- Compares contract award dates against supplier document expiration timestamps.
- Outputs a structured audit report summarizing award eligibility and documentation deficiencies.

## Starter Examples
```json
[
  {
    "input": {
      "ocid": "ocds-213kz6-0012",
      "implementation": {
        "status": "active",
        "milestones": [
          {
            "id": "m-1",
            "dueDate": "2024-06-30T10:00:00Z"
          }
        ]
      },
      "supplier_registry_entry": {
        "id": "GB-COH-9921",
        "insurance_expiry": "2024-04-30",
        "status": "active"
      }
    },
    "expected_output": {
      "ocid": "ocds-213kz6-0012",
      "supplier_id": "GB-COH-9921",
      "has_expired_credentials_during_implementation": true,
      "expired_items": [
        {
          "document": "insurance_expiry",
          "expired_on": "2024-04-30"
        }
      ],
      "audit_verdict": "implementation_compliance_failed"
    }
  },
  {
    "input": {
      "ocid": "ocds-213kz6-0013",
      "implementation": {
        "status": "active",
        "milestones": [
          {
            "id": "m-2",
            "dueDate": "2024-10-30T10:00:00Z"
          }
        ]
      },
      "supplier_registry_entry": {
        "id": "FR-RCS-1144",
        "insurance_expiry": "2025-01-01",
        "status": "active"
      }
    },
    "expected_output": {
      "ocid": "ocds-213kz6-0013",
      "supplier_id": "FR-RCS-1144",
      "has_expired_credentials_during_implementation": false,
      "expired_items": [],
      "audit_verdict": "implementation_compliance_cleared"
    }
  }
]
```

## Safety
Demonstration uses mock procurement records. No real government procurement bids or contracts are affected.
Use mock external writes. Require human review before any real deployment.