✔️ JSON Schemahard

9. Forbid unknown fields (additionalProperties)

Write a strict schema: an object with a required "name" (string) and NO other properties allowed. A doc with an extra key like "extra" must be rejected.

How to approach this

By default JSON Schema IGNORES properties you didn't list — a typo'd key sails through. Setting "additionalProperties": false locks the object to exactly the properties you declared, so a stray or misspelled field is caught. This is the difference between a permissive and a strict contract (Kubernetes CRDs and API validators lean strict).

schema.json