
KITFORMA · PRACTICAL WORKBOOK
JSON a Colleague Can Validate
Agree on fields, types and missing values before exchanging records
People handing structured records between tools, developers or small operational systems.
One-time payment, not a subscription. Applicable taxes appear at checkout.
What you will work through
- Distinguish valid JSON from a valid business record.
- Specify required fields, absent and null values, identifiers and extra-field policy.
- Reproduce positive and negative contract checks before a handoff.
Contents
- 01Define the handoff before its file format
- 02Separate syntax, structure and business meaning
- 03Choose identifiers that remain exact
- 04Make absence and null mean different things
- 05Turn a sample into a reviewed schema
- 06Use exact paths when discussing a failure
- 07Build examples that can prove the boundary wrong
- 08Plan changes before sending a new version
- 09Capstone: deliver the North inventory contract
- 10Keep the agreement useful after the first exchange
Scope and limitations
- The inventory and organizations are fictional teaching examples.
- The included checker validates this small exercise contract; it is not a general JSON Schema implementation.
- No production API, database migration or real inventory update is performed.
- Schema inference cannot discover business meaning or prove compatibility with an undocumented consumer.
How delivery works
Checkout is handled by Lemon Squeezy. After a successful purchase, download access appears on the provider’s order page and receipt email. Buying a book does not change your KitForma Pro plan.