Sovereign Cognition

Build governed cognitionfor real work.

Models infer. Indwel engineers cognition.

Indwel is the operating system for engineered cognition. It admits organizational information as Evidence, gives models and tools bounded roles, and keeps enterprise action under human and institutional authority. Memory carries the Work forward, so software can investigate, decide, act, and continue without putting the model in charge.

Indwel OS

The model is a faculty.Indwel OS is the system.

A model can reason, but it does not know the whole undertaking around its answer. Retrieval can find information, but finding something does not make it Evidence. An agent can call a tool, but capability does not confer authority.

Indwel OS governs them together. The objective and the organization’s terms frame the reasoning. Evidence is admitted for a purpose, action remains inside the authority boundary, and the undertaking survives changes of conversation or model.

Indwel governs the whole cognitive act—not merely the model.

Work gives the undertaking an objective and durable state. Information can come from Indwel Sources, the Library, enterprise systems, or controlled web acquisition. Retrieval may find what matters; only admitted Evidence may carry evidentiary weight.

Cognition advances the Work by seeking clarification or evidence, using deterministic computation, and delegating bounded tasks. Probabilistic inference contributes judgment where needed. Models remain faculties; enterprise systems remain external; people and organizational rules decide what follows.

Authorized Effects reach the outside world through admitted capabilities. Indwel records what was attempted, observes the result, and settles the Work accordingly. Memory and Continuity carry that state forward, so the undertaking survives changes of session, model, person, or system.

One decision, end to end

A recommendation is not an authorization.

In supplier onboarding, Indwel can gather and admit relevant Evidence, reconcile contradictions, and reason toward a recommendation. Procurement still owns the decision.

Indwel can reach a judgment without granting itself the authority to cause the organizational outcome.

Work

Supplier onboarding · SR-184

Status

live work

Question

Should this supplier be approved?

Indwel recommends

Approve with conditions.

Required authority

Procurement

Result

Not approved.

Work remains open until procurement decides.

What Indwel OS governs

The whole undertakingremains one system.

Indwel separates the things that must remain distinct—information and Evidence, probabilistic inference and deterministic computation, capability and authority, action and observed outcome—while keeping them inside one continuing Work.

Work gives cognition something durable to be about.

Work owns the objective and commitments of the undertaking. Cognitive Contracts shape how it may proceed; decisions and approvals change its state; unresolved questions remain visible. Artifacts and Effects remain attached to the durable Work itself.

Memory and Continuity preserve what the Work has admitted and where it stands across sessions, people, tools, and model changes.

Sources, Library, and Collections establish custody and provenance for information entering the Work. Indwel ships with OpenSearch and PostgreSQL/pgvector retrieval, plus deterministic and source-specific paths. Other search or vector systems can enter through admitted adapters and APIs.

Retrieval still does not confer authority. The Evidence Firewall governs what may be admitted, for which purpose, with what provenance and scope, so broad search results, private context, and organizational Evidence do not collapse into one undifferentiated prompt.

Intelligence contributes to the Work without owning it.

Cognition advances the objective under those evidence rules. It can seek clarification, verify material, invoke deterministic computation, or delegate a bounded task. Inference contributes probabilistic reasoning through hosted, private, or local model routes. Inference does not own Work.

Governed Agents are bounded workers, not free-standing authorities. Each receives a defined mandate, limited scope, and an explicit result contract. Tools and external capabilities follow the same principle: capability does not confer authority. People and organizational authority remain first-class through the roles and approvals that govern the Work.

Action is not complete until its result is known.

When authority permits it, Effects can change an external system, issue a notification, or create an artifact. Indwel does not treat the tool call as completion: the recommendation remains distinct from authority to act, and execution remains distinct from the observation that determines the final state.

Settlement and the Log determine what actually happened, preserve receipts and current state, and keep remaining obligations visible. That is what allows consequential work to continue after the model response, after the action, and after the people involved have changed.

Cognitive Contracts

The organisation sets the terms.

Intelligence does not determine the conditions under which its own judgement becomes authoritative. Cognitive Contracts constitute those conditions outside inference. They determine what Evidence is required, which authorities may decide, what capabilities may be exercised, what constraints apply, and what must be true before cognition may change institutional state.

The model reasons within those terms. It does not get to rewrite them.

Explore Cognitive Contracts →Ask Indwel how this would govern your process →

Your enterprise stays your enterprise

Connect what matters. Do not rebuild everything around AI.

Indwel connects to the systems organizations already use: Microsoft 365—including SharePoint, OneDrive, Outlook, and Teams—alongside Google Workspace and Drive, Slack, Dropbox, and Box.

Systems of record and specialist platforms such as Salesforce, ServiceNow, Snowflake, Databricks, and GitHub can participate through integrations, standard APIs, webhooks, MCP-compatible capabilities, and adapters. The adapter estate grows with customer requirements.

Dedicated and Licensed deployments can extend that boundary to organization-specific systems and integration patterns without changing the cognitive architecture around them.

Organizational controls

Review Indwel’s control framework and standards mappings in the Compliance Atlas.

View Compliance

Use or build

Use Indwel directly. Build applications of your own.

The same cognitive operating system appears in two forms: Indwel’s first-party workspace for people, and the Business Application Engine for software your organization builds.

Unity

The native workspace for using Indwel itself.

Unity is Indwel’s first-party application. It has the conversational immediacy of a modern AI workspace, but the conversation is only the visible surface of durable Work underneath.

People can work conversationally while bringing files and enterprise Sources into the same undertaking. Evidence and tools remain available inside the Work, and artifacts or decisions do not disappear when the conversation ends. Memory preserves what is unresolved, who holds authority, and where the undertaking stands.

Unity lets people inhabit continuing cognition under organizational authority.

Indwel Platform · Business Application Engine

Build cognitive applications on the same operating system.

Indwel Platform is the software-facing expression of Indwel OS. The Business Application Engine starts from the organization’s own domain and operating rules. Workflow and evidence policy determine how a case advances; the authority model defines who may intervene; completion conditions define when a case can close.

Indwel OS supplies the common substrate beneath those applications. Retrieval and Evidence determine what may be relied upon; inference and tools contribute capability; Memory and Continuity preserve state; Effects and Settlement carry authorized action to an observed result. The Platform API exposes this programmatically without becoming a second operating system.

You build the application. Indwel governs cognition within it.

What it can accomplish

Useful where the work is harder than the answer.

Indwel matters when an answer is only one step in a larger undertaking. The Work may need to persist, draw on several systems, involve responsible people, or cause real-world effects. Indwel preserves the grounds for decision and keeps human approval, deterministic checks, agent contributions, and external effects inside the same accountable Work.

What remains unresolved does not vanish with the session. Needed Evidence, pending decisions, active watchpoints, and existing artifacts remain attached to the Work. Through the Platform API, the Business Application Engine carries that same structure into business software.

For a disposable question that needs nothing beyond a model response, much of this machinery may be unnecessary. Indwel is built for cognition with consequences: evidence, authority, continuity, and an observed outcome.

Deployment

Choose how your Indwel estate operates.

The operating model changes who runs the estate and how much isolation and custody you require. It does not change the constitutional architecture.

Identity and access remain controlled. Evidence bounds what cognition may rely upon; authority bounds what it may cause. The estate must remain secure, resilient, observable, and economically controlled. Continuity and Settlement remain part of the same Indwel OS.

Managed

Choose it for the fastest path and lowest operating burden.

Indwel operates the infrastructure, releases, observability, and recovery. Your organization governs what its Work may access and who may authorize it, while Indwel carries the service burden.

Boundary: you operate inside the available managed regions, networking, release policy, and service envelope.

Dedicated

Choose it when policy, risk, scale, or custody warrants stronger isolation without taking over operations.

Indwel operates a customer-specific estate with isolated identity, network, data-plane, and cryptographic boundaries. Private inference can be added where the required model and network posture support it.

Boundary: greater cost and deployment complexity; releases and operating changes are coordinated rather than entirely unilateral.

Licensed

Choose it when operating sovereignty and customer control outweigh managed-service simplicity.

Your organization or operating partner runs licensed Indwel OS inside infrastructure it controls, including cloud, private-cloud, on-premises, or admitted disconnected estates. Identity, keys, custody, and release timing remain under the operator’s control.

Boundary: the operator assumes materially more responsibility for keeping that estate secure, resilient, observable, current, and integrated.

Private, local, and air-gapped are technical/custody postures—not separate editions.

They can be applied principally to Dedicated or Licensed estates where the required dependencies support them. Sovereign Cognition is the architecture across these operating postures, not another deployment edition.

Go deeper into the architecture

Paradigm. Problem.
Mechanism. Application.

01 · InferenceThe new computational paradigm.Why probabilistic judgement changes software architecture.02 · DichotomyThe failure of model-centred authority.Why inference cannot safely govern its own jurisdiction.03 · Cognitive ContractsThe positive constitutional mechanism.How organisational policy becomes binding authority over cognition.Ask IndwelApply the architecture to your Work.Bring your process, policy, Evidence, authorities, and deployment constraints.

Public-cloud portability

The operating system should not belong to one cloud.

Cloud infrastructure supplies capability. It does not supply institutional cognitive law. The governing semantics of Objective, Evidence, authority, Effects, Settlement, and continuity belong to Indwel OS rather than to the infrastructure provider.

AWSAvailable

Supported today for the current public-cloud foundation.

Microsoft AzureIn active development

Engineering is underway to carry the same governed operating model onto Azure.

Google CloudPlanned next

Planned to follow the first Azure deployment.

Cloud-provider status is separate from Managed, Dedicated, and Licensed operating posture. Research direction does not constitute product availability.

Ask Indwel

Go as deep as you need.

Ask Indwel to take the architecture all the way into your organization, your systems, and your work.

Ask how Unity differs from a conventional AI workspace. Ask how the Business Application Engine would express your process. Or bring one of your own workflows and ask what Evidence, authority, systems, and deployment boundary it would actually require.

Ask Indwel →Talk to Indwel →