Demiton · Schema
document_filing_convention contract v1
Your conventions for where each document type is expected to live.
CompanyConstructionCivil EngineeringProject ManagementComplianceMCPArtificial IntelligenceOpen Contracting
Properties
| Name | Type | Description |
|---|---|---|
| _authored | object | Provenance of the human-approved write: who approved the profile and when |
| org_aliases | array | Alternative names for the org seen in the tree |
| stage_roots | array | The lifecycle-stage root folders under which numbered opportunity folders live; the tenant's document-geography spine. Mandatory key; an empty array is a valid value when no stage clears the coverage |
| org_display_name | string | The org's own display name, only when independently evidenced |
| seeded_templates | array | bytes for `size`, **unverified** |
| superseded_markers | array | Folder-name markers the tenant treats as stale-revision / do-not-use, after the LLM's semantic call. The marker vocabulary is tenant and contract defined, never reproduced here |
| submission_locations | array | Subpaths under a stage root where priced/schedule-named files cluster, ranked by occurrence — where a submission is expected. The subpath strings are tenant folder convention, never reproduced here |
| opportunity_ref_pattern | string | The tenant's folder-name pattern that identifies an opportunity/project folder; the anchor every other convention hangs off. Mandatory key; the value may be `null` when no candidate clears the bar |
JSON Schema
{
"$schema": "https://json-schema.org/draft/2020-12/schema",
"$id": "https://docs.demiton.io/registers/document_filing_convention/v1.json",
"title": "document_filing_convention contract v1",
"type": "object",
"required": [
"_authored",
"opportunity_ref_pattern",
"stage_roots"
],
"properties": {
"_authored": {
"type": "object",
"description": "Provenance of the human-approved write: who approved the profile and when",
"x-demiton-requiredness": "required"
},
"org_aliases": {
"type": "array",
"description": "Alternative names for the org seen in the tree",
"x-demiton-requiredness": "optional"
},
"stage_roots": {
"type": "array",
"description": "The lifecycle-stage root folders under which numbered opportunity folders live; the tenant's document-geography spine. Mandatory key; an empty array is a valid value when no stage clears the coverage bar",
"x-demiton-requiredness": "required"
},
"org_display_name": {
"type": "string",
"description": "The org's own display name, only when independently evidenced",
"x-demiton-requiredness": "optional"
},
"seeded_templates": {
"type": "array",
"description": "bytes for `size`, **unverified**",
"x-demiton-requiredness": "tenant-specific",
"x-demiton-unit": "null}>"
},
"superseded_markers": {
"type": "array",
"description": "Folder-name markers the tenant treats as stale-revision / do-not-use, after the LLM's semantic call. The marker vocabulary is tenant and contract defined, never reproduced here",
"x-demiton-requiredness": "tenant-specific"
},
"submission_locations": {
"type": "array",
"description": "Subpaths under a stage root where priced/schedule-named files cluster, ranked by occurrence — where a submission is expected. The subpath strings are tenant folder convention, never reproduced here",
"x-demiton-requiredness": "tenant-specific"
},
"opportunity_ref_pattern": {
"type": "string",
"description": "The tenant's folder-name pattern that identifies an opportunity/project folder; the anchor every other convention hangs off. Mandatory key; the value may be `null` when no candidate clears the bar",
"x-demiton-requiredness": "required"
}
},
"x-demiton-register-type": "document_filing_convention",
"x-demiton-contract-version": "1.0.2",
"x-demiton-store": "tenant",
"x-demiton-axes": [],
"x-demiton-measures": [],
"x-demiton-provenance": {
"standards": [
{
"code": "AS ISO 19650.1:2019 / AS ISO 19650.2:2019",
"title": "Organization and digitization of information about buildings and civil engineering works, including BIM - Information management using BIM - Part 1: Concepts and principles",
"access": "public_summary",
"region": "Australia",
"edition": "2019",
"checked_on": "2026-09-14"
},
{
"code": "AS ISO 19650.2:2019",
"title": "Information management using BIM - Part 2: Delivery phase of the assets",
"access": "public_summary",
"region": "Australia",
"edition": "2019",
"checked_on": "2026-09-14"
},
{
"code": "ISO 19650-1:2018 / ISO 19650-2:2018",
"title": "Information management using building information modelling - Part 1: Concepts and principles",
"access": "public_summary",
"region": "International",
"edition": "2018",
"checked_on": "2026-09-14"
},
{
"code": "ISO 19650-2:2018",
"title": "Information management using building information modelling - Part 2: Delivery phase of the assets",
"access": "public_summary",
"region": "International",
"edition": "2018",
"checked_on": "2026-09-14"
}
]
},
"description": "Your conventions for where each document type is expected to live.",
"x-demiton-contract-url": "https://docs.demiton.io/registers/document_filing_convention/",
"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-document_filing_convention-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.