AI Anonymous by JABSystems — October 11, 2026
Valid JSON can still be wrong. Fictional local JSON Schema exercise.
Requires Python >=3.10. Tested on Windows / Python 3.13.15 with jsonschema 4.26.0.
Full guide: https://jabsystems.io/ai-anonymous/json-schema-check-the-handoff

Open PowerShell in a new empty practice folder:
python -m venv .venv
.\.venv\Scripts\python.exe -m pip install 'jsonschema==4.26.0'
Extract this ZIP to .\exercise and review validate-handoff.py and handoff-schema.json.
.\.venv\Scripts\python.exe .\exercise\validate-handoff.py .\exercise\handoff-good.json .\exercise\handoff-missing-owner.json .\exercise\handoff-extra-field.json .\exercise\handoff-invalid-date.json .\exercise\handoff-premature-action.json .\exercise\handoff-wrong-fact.json
$LASTEXITCODE
Expected exit: 1. Good and wrong-fact pass; four deliberate schema failures.
Exit 0: all supplied files passed schema. Exit 1: schema failures. Exit 2: input error.
The source facts are Harbor / Morgan / 2026-10-14 / pending / hold.
Wrong-fact uses Riley, an allowed owner, so the schema passes while source comparison fails.
No model calls or actions; never treat a response's approved string as real approval.
The starter prompt is proposed and untested against a model. Dependencies are not fully locked.
Installation needs network; venv isolates packages, not permissions.
Only the bundled schema is supported; no external references are used.
This is a small-file teaching script, not a hardened service. Real use needs input limits,
redacted logging, trusted source checks, authorization and controlled side effects.
