Packet

Problem

Procurement systems exchange PDFs, Word files, and ad hoc spreadsheets. Each document can introduce facts the packet never contained. Audit trails break when a printed field cannot be traced to a canonical source.

This standard defines a strict procurement packet as JSON: organization, parties, line items, quotes, award, delivery, inspection, payment, and generated document references in one schema-validated record.

Package contents

• Draft 2020-12 JSON Schema with additionalProperties: false at the root
• Plain-language SPEC.md rules beyond what JSON Schema alone can enforce
• Data dictionary and field-coverage maps from printed forms to JSON paths
• Valid, schema-invalid, and spec-invalid example corpora for validator testing
• Implementation guidance for producers, consumers, renderers, and archivers

{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "title": "Procurement packet",
  "type": "object",
  "additionalProperties": false,
  "required": [
    "standard",
    "packet",
    "organization",
    "office",
    "parties",
    "items",
    "quotes",
    "award",
    "delivery",
    "inspection",
    "payment",
    "acknowledgement",
    "documentReferences",
    "signatories",
    "accountingEntries",
    "documents"
  ]
}