Artifacts · 2026-09

Build against the published contract

A generated client can describe a Case, submit a Run, and inspect a receipt. It cannot confer an institution's authority or prove that a consequential effect succeeded. Indwel's versioned publication provides the API shapes, events, and integration specimens needed to build against those boundaries—and to preserve the exact contract your software was validated against.

Publication2026-09

Operations321

Schemas514

Operation families26

Manifest-covered files53

Published contract

One publication for your toolchain

The same versioned contract is published in the formats modern toolchains expect. OpenAPI remains the SDK-generation authority; JSON Schema carries reusable resource and transport shapes; AsyncAPI defines event channels. Postman, curated TypeScript declarations, registries, and executable examples make that authority practical without creating competing sources of truth.

HTTP APIOpenAPI JSONCanonical API contract for generators and tooling.1.03 MB

HTTP APIOpenAPI YAMLHuman-reviewable form of the same API contract.725 KB

Resource modelJSON SchemaPublished resource and transport shapes.203 KB

Resource modelTypeScript declarationsHand-curated core declarations for contract-aware editors and builds.1.5 KB

EventsAsyncAPIPublished event channels and payload contracts.1.5 KB

Client workspacePostman collectionGenerated requests across the public Platform surface.272 KB

Reference dataReference catalogAll 321 operations organized into 26 families.106 KB

CapabilitiesCapabilitiesMachine-readable projection of published Platform capabilities.5.1 KB

Supporting registries Event types Lifecycle states Error types OAuth scopes Postman environment

Implementation

Take the contract into your toolchain

Choose the artifact that matches the work: generate a client, validate payloads, exercise the API, consume events, or test governed behavior. Each path stays anchored to the same published contract, so convenience layers never become competing authority.

Generate an SDKUse OpenAPI 3.1.2 while preserving Problem Details, operation IDs, idempotency, preconditions, pagination, and unknown additive fields.SDK generation guide →

Validate resourcesValidate persisted or exchanged payloads against the published JSON Schema bundle.JSON Schema bundle →

Exercise the APIImport the Postman collection and public environment for exploratory and integration calls.Postman collection →

Integrate eventsPair AsyncAPI with the event registry and webhook semantics for delivery, retries, deduplication, and authoritative re-read.Events and webhooks →

Test governed behaviorKeep Cognitive Unit Testing beside the contract so regression criteria survive model, provider, retrieval, App Version, and deployment changes.Cognitive Unit Testing →

Executable governed RunThree minimal integrations against the same Case-bound Run Plan path.

cURLAuditable shell request. TypeScriptNode integration example. PythonStandard-library integration.

Protocol semantics Authority & scopes Idempotency & concurrency Errors & refusals Versioning

Release custody

Pin the exact publication

The manifest establishes custody for the published developer artifact set. Every covered path records its byte count and SHA-256 digest. The publication ZIP carries all 53 covered files plus the manifest, so teams can pin the exact contract beside generated clients, architecture review, and release evidence.

Manifest version2026-09

IntegritySHA-256

Covered files53

Publication ZIP132 KB

OpenAPI JSONa16673a47b1256a7e1503cd9ff897aa30a35a6048021a9efcd1fe828425439fe

OpenAPI YAML2a7b2298c134ecf81adc1d9c279997df0ef99ae4fc3eef017c923acd6961c4da

Reference catalogf2dbbb4bd774a721e0864051946675b203f9b0c364b2bdeab919de8aec929e05

curl -O https://developers.indwel.ai/downloads/developer-artifact-manifest.json
curl -O https://developers.indwel.ai/downloads/indwel-platform-developer-artifacts-2026-09.zip

What the record can actually prove

From source to judgment to receipt

A convincing account is not itself an authorized decision or proof of an external outcome. Preserve the sources actually admitted, alternatives investigated, the decision legitimately made, any effect attempted, and what the observed result proves. An inquiry may continue while an unauthorized act is held; an accepted operation is not verified Settlement.

The record should preserve the origin of each applicable obligation, the sources admitted, the Run’s supported conclusions, the accountable decision, and any external outcome actually observed. Different institutions can distribute those responsibilities among different offices, including peers whose contracts govern the same Case. The installed workflow, source rights, and question still impose distinct boundaries. Published artifacts define the interfaces for inspecting that record; they do not grant institutional authority.

Evidence

What source or fact was admitted, under which custody and applicability conditions.

GET …/runs/{runId}/evidence

Artifacts

What alternatives, supported conclusions, unresolved questions, and work products were produced for human review.

GET …/runs/{runId}/artifacts

Governance

Which requirements, business stage, and human participation govern a Case's next act.

GET …/cases/{caseId}/governance

Receipts

What operation or effect was recorded; inspect its result rather than guessing from acceptance.

GET …/runs/{runId}/receipts

These are separate source-backed resource families—not interchangeable claims of completed Work. Compare three reference applications to see how evidence, decision rights, and verification differ with the work.

Continue in the contract

Move from contract to implementation

The machine-readable release is the authority. These web surfaces provide faster ways to explore the same contract by route, schema, integration workflow, or governed application model. The authority for an institutional decision remains distinct from any answer artifact or receipt; the layered contract example explains that boundary.