Schemas
JSON Schema is the contract; drift is this capture against the last one.
- Tracked
- Loading Tracked
- Captured
- Loading Captured
- Subnets
- Loading Subnets
- Moved
- Loading Moved
- Not captured
- Loading Not captured
Drift. Which schemas changed, and how much surface changed with them.
Loading Schemas that changed since the last capture
Schemas that moved
Loading schema captures · snapshot
Size. How much each captured spec actually documents.
Loading Captured schemas by size
Loading captured schemas · snapshot
Why drift is published
A schema that changes silently breaks every generated client built against it. Each snapshot is diffed against its predecessor and the difference is served as a first-class record, so a consumer can see a breaking change as a fact rather than discovering it as an exception in production.
What a schema here guarantees
That the document was fetched from the operator's own source at the timestamp shown, not that it is correct. Where a published schema disagrees with the endpoint's actual behaviour, the disagreement is the finding — and the probe record is what settles it.