Skip to Schemas
Developers

Schemas

Inspect JSON schemas

Use the published JSON Schema contract to validate durable resources, generate types, and inspect the fields your integration exchanges with Indwel.

514 published schemasJSON Schema draft 2020-12OpenAPI 3.1.2

Run.schema.jsonpublished
JSON Schema#/$defs/Run
{
  "type": "object",
  "description":
    "Governed cognition execution…",
  "properties": {
    "runId": { "type": "string" },
    "workId": { "type": "string" },
    "caseId": { "type": "string" },
    "status": { "type": "string" },
    "contractResolutionId":
      { "type": "string" },
    "receiptIds": { "type": "array" }
  }
}
Exact resource shape comes from the published contract; runtime authority is resolved separately.

Schema browser

Find a schema

Search names, descriptions, and fields across the complete published contract. Choose a resource to inspect its fields or raw JSON Schema.

Press / to search

Published schema

Run

Object schema6 named fieldsNo required array published#/$defs/Run

Governed cognition execution with explicit identity, contract, evidence, economics, artifacts, and receipts.

Schema defines shape. Authorization, Cognitive Contracts, evidence obligations, and required human participation are resolved by the Platform at runtime.

Schema is not authority

Three distinct instruments, one governed Case

A schema defines the structure of data an integration exchanges with Indwel. An App Version defines the application’s business transitions, including the evidence and people those transitions require. The institution’s own Cognitive Contracts govern who holds authority and which obligations apply to the Case; a Run Plan records the admissible basis and capabilities for one attempt. A well-formed JSON body can request an operation, but it cannot create a decision right.

App schema

What a vendor packet, question, or release candidate may contain.

manifest.schemas[]
Cognitive Contract

Which evidence and independently authorized participants are required to move business state.

manifest.workflows[].cognitiveContract
Run Plan

Which admitted basis and permitted route apply to this Case's next execution.

POST …/cases/{caseId}/run-plans
Vendor Risk Review · transition contract
"transitionId": "record-disposition",
"fromStage": "review",
"toStage": "decided",
"evidenceRequirements": [{
  "requirementId": "evidence.vendor-risk-packet-custody"
}],
"humanAuthorityRequirements": [{
  "requirementId": "authority.risk-owner",
  "authorityClass": "risk-owner",
  "decisionPolicy": "single-authority"
}]

The excerpt is intentionally partial; the full source fixture also declares accepted evidence sources and eligible tenant roles.

Follow the governed transition

The decision boundary

Who may authorize the decision?

In this supplier review, the installed application can require admitted evidence and an eligible decision-maker. Which office is eligible, what information it may consider, and which obligations apply come from the institution and the particular Work. Other institutions can allocate those responsibilities differently without changing the distinction between valid data and legitimate authority.

Institutional authority

Each part of the institution speaks within its own remit: enduring policy, professional standards, team obligations, and the purpose of the Work. Other institutions might vest those duties in divisions, regional offices, committees, or individual officeholders.

Independent contracts can apply together, including contracts owned by departments that are peers rather than parent and child. Their resolution protects legitimate authority while leaving inquiry free to discover an answer the original sponsor did not expect.

Published application contracts

The App Version declares the domain schema and workflow. Its indwel.cognitive-contract.v1 records evidence, human participation, and transition requirements. The Run Plan establishes the basis for an attempt; the Case persists beyond that Run.

The published interfaces describe application obligations and individual Run Plans—not a general editor for every institutional jurisdiction.

The semantic resolver currently identifies baseline, organization, team, Work, source, and question scopes. Department is shown as an institutional jurisdiction within that wider model, not as a separately proven live contract-authoring endpoint. Contract resolution, browser execution, and administrative assignment must be qualified independently of the published schema.

Explore layered governance in context

Use API Reference for operations, Developer Guide for integration patterns, and Artifacts for machine-readable bundles and generated types.