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.
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“Refund order ord_881 for INR 4,200.”
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.
Useful context starts with sources you can identify and access.
Select a boundary to inspect it, or follow the run in order.
0 example write attemptsThis 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.
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.
Every fact keeps its source, and missing facts stay visible. Text the agent reads can never give it permission to act.
Right before an action runs, check who is asking, what they are allowed to do, and whether the right people approved this exact action.
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".
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.
RequestRefund this order.
AuthorityThe agent's own permissions, plus approval for this exact refund.
Accepted resultThe provider confirms the permitted refund.
RequestRestore this service.
AuthorityApproval for this exact change, limited to the affected service.
Accepted resultService health meets the recovery criteria.
RequestFix this defect.
AuthorityChanges stay within the granted repository scope.
Accepted resultThe change passes the declared checks and review.
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