The conversation
can end.The undertaking
cannot vanish.

Indwel gives an undertaking durable identity, objective, state, evidence, authority, obligations, actions, and history, making it the context through which the rest of the operating system can act. Even as people leave, models change, or time passes, the institution retains a coherent account of what it is doing and why.

A conversation may start the undertaking.It does not have to contain it.

We will follow one undertaking—a 2027 benefits renewal—long enough to show what durability means in practice, without suggesting that the example defines the product. The starting record is incomplete, but the objective is explicit; Indwel does not invent a recommendation merely because a conversation has begun.

Unity is the first-party view shown through this story, not the boundary of the product. The undertaking belongs to the Indwel operating plane.

The undertaking is where the wider system meets the business problem. Collections and retrieval, models and governed agents, deterministic services, tools and coding, connectors, memory, contracts, effects, observation, and settlement can all participate without collapsing into one model session.

Indwel Unity on Day 0 showing the 2027 Benefits Renewal established as durable work with an explicit objective and incomplete evidence posture. — Day 0. The undertaking exists before the evidence is complete.

DAY0 From the first exchange, the objective, governing conditions, admitted material, open questions, and obligations belong to the work itself.

Conversation can explain the undertaking and return to it. Other applications, APIs, agents, and scheduled processes can participate without requiring the conversation to remain open.

Evidence changes the Work without replacing it.

DAY12 Current formulary evidence changes what can responsibly be recommended.

Indwel does not start another case or reconstruct an earlier chat. New material enters the same undertaking through governed retrieval and evidence admission, against the objective and evidence already in force.

Close view of Unity on Day 12 showing admitted evidence, an excluded weaker source, a material conflict, and an objective clarification request. — Day 12. New evidence changes the decision frontier without replacing the undertaking.

The objective can change without changing the past.

DAY21 The institution makes the specialty-drug requirement explicit. Objective v2 becomes governing; objective v1 remains preserved as superseded. Earlier analysis remains attributable to the objective that governed when it was produced.

The undertaking changes without pretending it had always been different.

Indwel Unity on Day 21 showing objective v2 governing the benefits renewal while objective v1 remains preserved in lineage. — Day 21. The current objective changes; the history does not.

The work can wait.

Durability does not mean an agent runs continuously. State, obligations, evidence posture, memory boundaries, schedules, and external dependencies remain available while the undertaking is quiet.

When a person, source, date, system, or governed agent returns with something material, cognition resumes from governed state rather than from a reconstructed transcript.

Unity on Day 35 restoring the governing objective, established facts, open questions, and current frontier without reconstructing the old transcript. — Day 35. The conversation ended. The undertaking did not.

DAY35 Two weeks later, the user asks to be brought current. Indwel restores what governs, what has been established, what remains open, and what now needs attention.

Unity on Day 50 showing a remembered presentation preference while preserving the boundary between memory and evidence. — Day 50. Memory may shape presentation without becoming evidence.

DAY50 Personal continuity can help without becoming factual authority. A remembered preference may change how the work is presented; it cannot change what counts as evidence or which conclusion the record supports.

Unity on Day 65 showing scheduled cognition returning after a carrier formulary update and preserving the evidence boundary. — Day 65. A date or external change can bring the undertaking back into active cognition.

DAY65 The undertaking can wait on a person, a date, a source, a permission, a system, or an external condition. Resumption does not erase the distinction between what returned and what the institution may rely upon.

Decision-ready is not decided.

DAY78 By then, the material questions have been resolved. The alternatives have been tested against the governing objective, the evidence has standing, and the recommendation can be defended. The Benefits Committee still owns the consequential decision.

Indwel carries the decision packet, lineage, evidence, and residual risk into that handoff without transferring authority to the models, agents, tools, or application that prepared it.

Indwel Unity on Day 78 showing the benefits renewal decision-ready while Benefits Committee authority remains required before plan selection. — Day 78. The recommendation is decision-ready. Institutional authority remains elsewhere.

SETTLEMENT

The Work ends when reality warrants it.

DAY90 Approval is not completion. An attempted effect is not an observed result. The renewal settles only after the selected plan is actually observed and the record warrants the conclusion.

Open-enrollment implementation remains separate work because it has its own objective, obligations, effects, and ending.

Indwel Unity on Day 90 showing the 2027 Benefits Renewal settled from observed plan selection while open-enrollment implementation continues separately. — Day 90. The decision work has settled. The next undertaking remains distinct.

The domain changes.The operating plane remains.

The benefits renewal is one undertaking, not a product category. The same operating plane can carry a software release, an engineering investigation, an analytics program, a procurement decision, or another institutional undertaking.

The domain supplies its language, objectives, evidence, systems, decision rights, and consequences. Indwel supplies the common machinery that makes the work durable, intelligent, governable, and programmable.

Operational detail from Release Readiness showing Build 417, readiness gates, effect authority, and release lifecycle without the surrounding application showcase. — A close reading from Release Readiness: different software, different domain, the same need to bind evidence, authority, effect, observation, and settlement.

The application inherits more than governance.

Unity is Indwel’s first-party experience, not the boundary of the system. Applications can use their own interfaces, domain language, and interaction models while inheriting the operating plane beneath them.

That plane carries collections and retrieval across vector-backed stores, with adapters for additional stores and enterprise systems. Model and governed-agent fleets, deterministic services, tools and coding, durable state and memory, scheduled execution, connectors, and effect handling can all participate.

Cognitive contracts, identity, observation, receipts, and settlement keep those faculties inside institutional authority.

Indwel is therefore both an enterprise operating plane and a software-development platform. It is not merely a governance layer around model calls; it supplies governed runtime resources through which an inference-based application can retrieve, reason, use tools, act, observe, and continue work.

Release Readiness makes that concrete. Its real application manifest binds evidence, authority, effect, and settlement policies, and its runtime creates cases, run plans, and runs through the Platform API. The interface is its own. The operating plane is Indwel.

release-readiness.manifest.jsonPlatform application definition

{
  "workflowId": "release-readiness",
  "name": "Release Readiness",
  "inputSchemaId": "release-readiness.request.v1",
  "outputSchemaId": "release-readiness.result.v1",
  "policyIds": [
    "release-readiness.evidence.v1",
    "release-readiness.authority.v1",
    "release-readiness.effect.v1",
    "release-readiness.settlement.v1"
  ]
}

# The application then executes through the governed Platform runtime.
POST /v1/organizations/{organizationId}/workspaces/{workspaceId}/cases
POST /v1/organizations/{organizationId}/workspaces/{workspaceId}/cases/{caseId}/run-plans
POST /v1/organizations/{organizationId}/workspaces/{workspaceId}/cases/{caseId}/runs

Real Platform authority from the Release Readiness manifest.

The business surface can be radically different. The operating plane remains inspectable underneath it.

From here, collections and integrations show how information enters; cognitive contracts and settlement show how authority and consequence remain governed; architecture and the Platform expose the wider system beneath the undertaking.

The institution should
still know
what it is
doing tomorrow.

People can change. Models, agents, tools, stores, providers, and applications can change. The undertaking remains attributable to the institution that owns it until the Work has honestly finished.

If you already have Work you are ready to improve, the Governed AI Review turns one consequential undertaking into a concrete production design.

Governed AI Review

The conversation can end.The undertaking cannot vanish.