Workspace profile

Your conventions for where each document type is expected to live.

Part of Platform in the register catalog.

Register ID

workspace_profileUse this name to ask for the register. The API calls it a shelf ID.

Each record is

A stateThe current value of something, replaced when it changes.

Status

AvailableFilled today from connected systems, uploads or public data.

Data

OrganisationPrivate to each organisation's own workspace.

Version

v1Current version.

Download JSON SchemaSee an example record

Standards

This register holds records these standards and laws ask for. Holding them does not by itself certify compliance.

• ISO 19650Information management using building information modellingInternational

Connectors

Connected today

Demiton keeps this register current from these systems now.

No system fills this register yet.

On the roadmap

Systems in the planned connector rollout that can fill this register. Partial means the system holds only some of its fields.

• Oracle AconexPartial
• SitematePartial

Fields

8 fields: 3 required, 2 optional, 3 defined by each organisation.

Required

Every record carries these fields.

opportunity_ref_patternText

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.

Example: ^\d{3,5} - .+$

stage_rootsList

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.

_authoredGroup of fields

Provenance of the human-approved write: who approved the profile and when.

Optional

Present when the source system records them.

org_display_nameText

The org's own display name, only when independently evidenced.

Example: Bridgeworks Group

org_aliasesList

Alternative names for the org seen in the tree.

Defined by each organisation

Their contents come from the organisation's own forms or systems, so they differ between organisations.

submission_locationsList

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.

superseded_markersList

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.

seeded_templatesList

Bytes for size, unverified

Example record

A sample from Bridgeworks Group, Demiton's demonstration company. The values are illustrative; the shape is exactly what the contract describes.

workspace_profile.example.json

{
  "_authored": {
    "approved_at": "2026-06-10T00:00:00Z",
    "approved_by": "kim.tanaka@bridgeworks.example"
  },
  "opportunity_ref_pattern": "^\\d{3,5} - .+$",
  "org_aliases": [
    "Bridgeworks Group Pty Ltd",
    "BWG"
  ],
  "org_display_name": "Bridgeworks Group",
  "stage_roots": [
    "01 Pursuing",
    "02 Tendering",
    "03 Won",
    "04 Delivering"
  ],
  "submission_locations": [
    "Submitted",
    "Priced Schedule"
  ],
  "superseded_markers": [
    "OLD",
    "SUPERSEDED",
    "DO NOT USE"
  ]
}

Use this contract

The contract is a standard JSON Schema (draft 2020-12) document, so any JSON Schema validator can check a record against it. Keywords starting with x-demiton- add Demiton's own meaning, such as units and requiredness, and validators ignore them.

Schema URL

https://docs.demiton.io/registers/workspace_profile/v1.json

Show the full JSON Schema

Loading the schema…