Skip to content
ContextOS in action

Useful work.
Visible control.

An agent can propose a refund. A reliable harness must establish whether it is eligible, whether it is permitted, and whether it actually happened.

Explore one request
One request, three distinct checksEvidence establishes eligibility. Current authority permits the action. Observed provider state establishes completion. The ContextOS contract connects these checks and retains their evidence.01ELIGIBLE?Source evidence02ALLOWED?Current authority03DONE?Observed resultOne inspectable contractEVIDENCE CONNECTS EVERY CHECK
The interactive walkthrough

Follow the run. Change the conditions.

Illustrative data · no live payments
Choose a case

Current evidence, permitted caller, valid finance approval.

Request

“Refund order ord_881 for INR 4,200.”

usr_771 agt_support
Boundary 01 / 06What do we know?
Scoped source evidence

Evidence enters through a scoped lookup.

The application resolves the caller and tenant before collecting order and policy evidence. Untrusted instructions in source material cannot grant new authority.

Caller
usr_771 via agt_support
Tenant
tenant_acme_prod
Order lookup
ord_881 · current source
Policy source
POLICY_RETURNS_V4

Useful context starts with sources you can identify and access.

Read this contract
Following the run · Find evidence

Select a boundary to inspect it, or follow the run in order.

0 example write attempts

This interactive story models the documented refund contract. It does not execute the reference compiler, call a model, evaluate live policy, or connect to a payment provider. Your implementation supplies and tests those controls.

What this changes

The model proposes.
The boundaries make it accountable.

ContextOS gives teams a common contract for context, decisions, effects and evidence. The implementing runtime enforces it; the observed outcome earns acceptance.

01

Keep context relevant and inspectable.

Retain source provenance and visible gaps. Retrieved text cannot grant itself permission.

02

Make permission an enforced decision.

Check the caller, tenant, actual arguments and current approval at the effect boundary.

03

Keep the evidence after the answer.

Connect accepted outcomes to tool results, controls and replay references. A transcript alone does not establish success.

Beyond the refund

Different work. The same questions.

Define domain-specific acceptance criteria and authority. Then preserve the connection between the request, permission and observed result.

Customer operations

RequestRefund this order.

AuthorityA scoped caller and current approval.

Accepted resultThe provider confirms the permitted refund.

Incident response

RequestRestore this service.

AuthorityAn approved action on the affected environment.

Accepted resultService health meets the recovery criteria.

Software delivery

RequestFix this defect.

AuthorityChanges stay within the granted repository scope.

Accepted resultThe change passes the declared checks and review.

Put it to work

Bring one workflow.
Make its boundaries explicit.

The specification, schemas and compiler reference are open. Start with accepted outcomes and prohibited effects in the runtime you already use.

Adopt the contractAssess an existing harness