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 checksSource evidence is checked for current eligibility. Current authority and independent action controls permit dispatch. Verified provider postconditions support completion. The contract preserves missing or uncertain 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, owned authority and required execution controls.

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 binds the invocation to exact supported profile/control versions and verifies current owned caller, tenant and delegation ancestry before collecting eligible evidence. Actual recipient, processor, purpose and retention rules apply at each data stage. Untrusted source instructions cannot grant 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 one shared rulebook for what an agent sees, decides, changes and records. Your runtime enforces it, and a task counts as done only when the result is actually observed.

01

Show the agent only what it needs, and where it came from.

Every fact keeps its source, and missing facts stay visible. Text the agent reads can never give it permission to act.

02

Check permission in code, every time.

Right before an action runs, check who is asking, what they are allowed to do, and whether the right people approved this exact action.

03

Keep proof of what really happened.

Tie every result to something you can verify, like the payment provider's record. If the outcome is unclear, say so; "cancelled" is not the same as "never happened".

Beyond the refund

Different work. The same questions.

Each kind of work has its own definition of done and its own permissions. The pattern stays the same: link the request, the permission and the verified result.

Customer operations

RequestRefund this order.

AuthorityThe agent's own permissions, plus approval for this exact refund.

Accepted resultThe provider confirms the permitted refund.

Incident response

RequestRestore this service.

AuthorityApproval for this exact change, limited to the affected service.

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.

Start with the open spec, schemas and reference code. Pick the risk level that fits your workflow, then test that it does the right thing, refuses the wrong thing and recovers from failures, in the runtime you already use.

Adopt the contractPick your risk levelProve it worksAssess an existing harnessTest your judgment in Agent Gate