Business App Engine

Build business applications on Indwel.

Business App Engine turns an application definition into a versioned runtime on Indwel. Your code defines the business model and workflow. Indwel supplies the execution authority and durable record around each Run.

Example Company Answers · evidence-backed answers with durable review and re-execution.

HTTP Client Business App Engine

POST https://api.indwel.ai/v1/organisations/acme/projects/risk/apps Send

Illustrative requestapplication/json

{
  "name": "Company Answers",
  "slug": "company-answers",
  "description": "Evidence-backed company answers."
}

201 Createdapplication/json

{
  "operationId": "op_20260922_001",
  "resourceId": "app_company_answers",
  "status": "accepted",
  "receiptId": "rcpt_20260922_001"
}

Illustrative request body; endpoint, 201 Created response, and OperationAccepted fields follow the public Platform contract.

Application model

Application boundary.

An App Definition is the durable domain contract for one application: its schemas, workflow states, admissible actions, and business policy. It can move on its own release cadence without moving identity, evidence custody, or execution into application code.

The App Definition carries domain semantics. Indwel supplies execution authority, evidence custody, receipts, and Settlement.

Company Answers, for example, owns the question model, answer workflow, review requirements, and application interface. The Platform resolves the effective Cognitive Contract, admits evidence, executes governed Runs, records receipts, and preserves Settlement. Those responsibilities stay stable even as the application itself evolves.

Business App Engine does not replace systems of record. A Case stores the durable state needed to move the matter forward and references evidence or external records where they already live.

Release model

Application releases.

Draft definitions remain editable until publication. Publishing creates an immutable App Version. A Deployment selects the version for an environment; an Installation binds it to an authorized workspace. Existing Cases retain their original version attribution.

Run Cognitive Unit Tests before publication to verify evidence requirements, authorization, workflow transitions, and Effects.

01Create versionPOST…/apps/{appId}/versions

02ValidatePOST…/versions/{versionId}:validate

03PublishPOST…/versions/{versionId}:publish

04DeployPOST…/apps/{appId}/deployments

05InstallPOST…/deployments/{deploymentId}:install

Runtime

Cases and Runs.

A Case is the durable business matter. It carries the application state that must survive beyond any single execution: participants, evidence references, review state, deadlines, decisions, and the App Version that governs the matter.

One Case can outlive many Runs.

Company Answers can receive a question once, admit additional evidence later, pause for review, execute, and execute again when evidence or policy changes. Those executions do not overwrite the Case. Each Run remains attributable to the App Version, effective Cognitive Contract, admitted evidence, and authority that governed it.

Before execution, Indwel materializes a Run Plan: the declared requirements, evidence posture, authority, and permitted capabilities for that attempt. The resulting Run becomes the durable execution record for inference, decisions, Effects, receipts, and Settlement. Developers can inspect later executions without reconstructing prior state from logs.

Human authority

Human review and approval.

Business App Engine treats human action as part of the execution record. A Case can stop because evidence is incomplete, separation of duties requires another actor, an exception remains unresolved, or a business condition has not yet matured.

A pause preserves the Case, admitted evidence, prior decisions, and version attribution while work waits. When a reviewer or approver acts, the Platform records the identity, scope, decision, and authority under which that action was taken.

Cognitive Governors evaluate whether the next transition is permitted. Deadlines and recurrences can reopen work without rebuilding control state. Approved Effects and Settlement stay attached to the same durable Work record, so the application does not have to infer authority from application logs after the fact.

Platform API

Business App Engine API.

The API family covers authoring, immutable publication, deployment, installation, diagnostics, compatibility, and rollback. Most integrations use a small set of lifecycle calls; the complete operation set remains in API Reference.

Create the applicationPOST …/projects/{projectId}/apps

Publish an immutable versionPOST …/versions/{versionId}:publish

Inspect an installationGET …/installations/{installationId}/diagnostics

Continue with API Reference, Schemas, Artifacts, or the Developer Guide.