Build the solution · 2 / 5

Offer valid delivery states

Give producers a predictable status vocabulary.

YOUR TASK

Make this happen

3 steps

Add a status property allowing dispatched or delivered, defaulting to dispatched. Preserve trackingId.
Keep the working capabilities from the previous lesson and connect the new pieces to the same solution.
Check the complete solution, then inspect any unmet requirements.

THE IDEA BEHIND IT

What this step adds

Add a status property allowing dispatched or delivered, defaulting to dispatched. Preserve trackingId.

Files to work in

contract.json. Other files are the working baseline. New files include named resource skeletons and TODO guidance. Complete their fields and connect them using the objectives, schema completion and reference guide.

Defaults are annotations

A default documents a useful value; JSON Schema validation does not promise to insert it into incoming data. The application must choose whether to apply defaults.

Enums are contract choices

An enum limits accepted values. Keep the default inside it and agree on transitions with the provider; schema validity alone does not implement a state machine.

Local IaC input checks and lesson contracts do not replace platform JSON Schema/OpenAPI processing. No external references, uploads or embeddings run here.

Files to change: contract.json

What you’re building: Define a reliable supplier delivery contract, then make its API discoverable.

This step starts with the earlier solution and one new challenge. Each lesson keeps its own draft.

Read the starter files

main.cococo

external_schema "supplier" {
  name = "Supplier delivery contract"
  format = "JSON_SCHEMA"
  sourceText = file("contract.json")
}

contract.json

{
  "$schema": "http://json-schema.org/draft-07/schema#",
  "title": "Supplier delivery",
  "type": "object",
  "properties": {
    "trackingId": {
      "type": "string",
      "minLength": 1
    }
  },
  "required": [
    "trackingId"
  ],
  "additionalProperties": false
}

Reference: schemas · authoring schemas · external-schemas