Demiton · Schema
compliance_gate_verdict contract v1
The Compliance gate verdict register contract, version 1. JSON Schema (draft 2020-12); x-demiton-* keywords carry Demiton's own meaning and standard validators ignore them.
CompanyConstructionCivil EngineeringProject ManagementComplianceMCPArtificial IntelligenceOpen Contracting
Properties
| Name | Type | Description |
|---|---|---|
| verdict | string | The countdown state: COMPLIANT (>90 days out), EXPIRING_90, EXPIRING_30, EXPIRING_7, or EXPIRED (days_until_due < 0 - stays EXPIRED, never silently reverts, until the source record itself renews/retir |
| due_date | string | The obligation's expiry/next_due date the countdown is measured against, as an ISO 8601 date. |
| cause_category | string | The subcategory of the verdict's disease: the stage or control that failed. One of that disease's `causes[].key` in vocab/diseases.json, checked by the writer. Absent when the detector does not determ |
| days_until_due | integer | due_date minus the assessment date, in days. Negative once overdue - the alert cites how overdue, not just that it is (SD027 1's proof line). |
| obligation_ref | string | A human-readable label for the specific obligation (holder + credential type, or insured party + policy number) - what the alert names. |
| source_fact_id | integer | The specific feeder Fact row this verdict tracks - the citation's derived_from anchor. |
| obligation_type | string | What kind of compliance obligation this is, e.g. certification, insurance. One value per wired feeder register. |
| source_shelf_type | string | Which feeder register this verdict was derived from (certification_register, insurance_certificate, ...) - lets the alert cite its source (SD027 1's proof line: every number proves itself). |
JSON Schema
{
"$schema": "https://json-schema.org/draft/2020-12/schema",
"$id": "https://docs.demiton.io/registers/compliance_gate_verdict/v1.json",
"title": "compliance_gate_verdict contract v1",
"type": "object",
"required": [
"days_until_due",
"due_date",
"obligation_ref",
"obligation_type",
"source_fact_id",
"source_shelf_type",
"verdict"
],
"properties": {
"verdict": {
"type": "string",
"description": "The countdown state: COMPLIANT (>90 days out), EXPIRING_90, EXPIRING_30, EXPIRING_7, or EXPIRED (days_until_due < 0 - stays EXPIRED, never silently reverts, until the source record itself renews/retires).",
"x-demiton-requiredness": "required"
},
"due_date": {
"type": "string",
"description": "The obligation's expiry/next_due date the countdown is measured against, as an ISO 8601 date.",
"x-demiton-requiredness": "required",
"x-demiton-unit": "ISO 8601 date"
},
"cause_category": {
"type": "string",
"description": "The subcategory of the verdict's disease: the stage or control that failed. One of that disease's `causes[].key` in vocab/diseases.json, checked by the writer. Absent when the detector does not determine it.",
"x-demiton-requiredness": "optional"
},
"days_until_due": {
"type": "integer",
"description": "due_date minus the assessment date, in days. Negative once overdue - the alert cites how overdue, not just that it is (SD027 1's proof line).",
"x-demiton-requiredness": "required",
"x-demiton-unit": "days (signed)"
},
"obligation_ref": {
"type": "string",
"description": "A human-readable label for the specific obligation (holder + credential type, or insured party + policy number) - what the alert names.",
"x-demiton-requiredness": "required"
},
"source_fact_id": {
"type": "integer",
"description": "The specific feeder Fact row this verdict tracks - the citation's derived_from anchor.",
"x-demiton-requiredness": "required"
},
"obligation_type": {
"type": "string",
"description": "What kind of compliance obligation this is, e.g. certification, insurance. One value per wired feeder register.",
"x-demiton-requiredness": "required"
},
"source_shelf_type": {
"type": "string",
"description": "Which feeder register this verdict was derived from (certification_register, insurance_certificate, ...) - lets the alert cite its source (SD027 1's proof line: every number proves itself).",
"x-demiton-requiredness": "required"
}
},
"x-demiton-register-type": "compliance_gate_verdict",
"x-demiton-contract-version": "1.1.0",
"x-demiton-store": "tenant",
"x-demiton-axes": [],
"x-demiton-measures": [],
"x-demiton-provenance": {
"standards": []
},
"description": "The Compliance gate verdict register contract, version 1. JSON Schema (draft 2020-12); x-demiton-* keywords carry Demiton's own meaning and standard validators ignore them.",
"x-demiton-contract-url": "https://docs.demiton.io/registers/compliance_gate_verdict/",
"x-demiton-register-catalog": "https://docs.demiton.io/concepts/register-catalog"
}
Work with this as data
Every JSON Schema here is available over the APIs.io API and to AI agents over MCP.
MCP server
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
Tools for schemas
4 MCP tools reach this
find_json_schemasBrowse and filter every JSON Schema in the catalog.apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.resolveTurn a domain, URL or GitHub org into the provider it belongs to.find_cohortsEvery scored population of providers in the catalog.
Call it yourself
curl for this page
This JSON Schema
curl "https://apis.io/api/v1/json-schemas/demiton-io-compliance_gate_verdict-v1"
All schemas
curl "https://apis.io/api/v1/json-schemas?limit=25"
Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.
Get an API key
Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.
A second provider on the same verified email joins the account you already have.