Execution boundaries

A workflow executes in the browser or on the user's computer. Real API calls originate there. Hosted xEntropy processes simulated service calls only; it does not proxy arbitrary real endpoints or run the whole workflow.

A service agent receives its selected context, operation, incoming input, scenario, and own run-scoped state. It does not receive assertions, expected outputs, the full graph, or other services' private state. User-supplied text is behavior data, not authority to access another account or operator credentials.

Accounts own definitions, run snapshots, outputs and history. Clerk tokens and scoped runner credentials authorize access. Local secret-header references are resolved at execution and must never be included in graph exports or recorded evidence. Uploaded files are subject to path, byte and count validation.

HTTP disconnection is not cancellation. Explicit cancellation stops outstanding simulated work where possible and prevents new graph work. A real request may already have reached its destination; cancellation does not undo external side effects. The runner never retries real writes automatically.

Completed and cancelled runs release active service state. Run history retains diagnostic data, including selected inputs/outputs; it is not initial state for future runs. Only deliberately non-sensitive examples should be published as evidence.

Graph run assertions establish the tested cases, not universal equivalence to a real service. Client-originated real-call traces are labeled client-reported. Agent/provider failure is never converted to an invented successful service response.