Jsonforge: Schema Cards

Before: a candidate JSON Schema tightens one field — say amount must now be greater than zero — and nobody on the team can say which of last month's real payloads would start failing. After: Jsonforge replays every captured payload against both the baseline and the candidate contract and hands you a verdict per file — stable, regression, recovered, or still failing — each backed by exact JSON Pointer evidence and a SHA-256 fingerprint. The workflow is a flight recorder for API contracts. Keep a corpus of observed payloads beside two schema revisions, edit either side in the Schema Bay, and replay the corpus to watch the impact matrix recompute. When it is time to migrate documents, author an RFC 6902 patch in the Patch Lab and apply it with per-operation pre-state evidence and a generated inverse. - Strict RFC 8259 parser that rejects duplicate keys and trailing commas instead of guessing - JSON Schema 2020-12 subset validator that fails closed on unsupported keywords - Structural contract diff separating required, type, and constraint changes - Everything computes on this device; the binary contains no network client and your corpora never leave it - RFC 6902 patch engine covering test, add, remove, replace, move, and copy with a provable inverse - Revision snapshots with fingerprints you can restore and re-replay - Evidence reports exported as Markdown or JSON through the share sheet - Projects saved as portable .jsonforge packages via the Files app Replay classifications describe how sample payloads evaluate against your schemas; they are informational and no substitute for your own release testing.