Rules, execution
and evidence.

OWAI OS / DEMOS

Allowed. Held.
Refused. Recorded.

Two recordings of OWAI OS running on a single server. Every decision card in the videos was drawn from the system’s own responses during that run.

DEMO 1 · SUPPORT AGENT AND REFUNDS

Your AI agent answers customers.
It can also refund them.

Recorded 6 October 2026 · OWAI OS 0.1.92 pilot build · one Linux server with Docker · no sound · about 3 minutes. The agent and the customer follow the demo script; the decisions, policy versions, times and audit check are the system’s answers.

Allowed

A £120 refund is within the stored policy: automatic up to £500, within 30 days. The decision names policy version 1.

Held for a person

A £2,000 refund is above the limit and is held for a human decision.

The agent cannot raise its own limit

The agent attaches its own £5,000 limit to the request. The request is held and the policy in force stays unchanged: a request can only lower a limit.

Refused

A refund for an order from 45 days ago is outside the refund window. An attempt to extract the agent’s instructions is refused and recorded in the audit trail without its text. A draft reply with a card number is refused; the same reply without it is allowed.

Asked again before the payout

The same £300 refund is allowed under version 1. The company lowers the limit to £200 (version 2), and the payment step asks again just before paying out: held, under the policy in force now.

Recorded

A table of every decision with its policy version and time, and the chat guard’s audit chain checked: verified.

OWAI OS decides; your payment system pays out. A person’s decision happens in your own system, and refund decisions carry a policy version rather than a signature.

DEMO 2 · CODING AGENT AND MEMORY

Stopped. Signed.
Forgotten. Detected.

Recorded 6 October 2026 · OWAI OS 0.1.92 pilot build · one Linux server with Docker · no sound · the pause for questions is shortened.

Refused

Calls signed with a key that is not on the signed list, or that belongs to another tenant, are refused at every entry point.

Held, then signed

A proposed code change waits until a named approver signs it. The gateway decision and the approval each carry their own signature.

Verified

The gateway checks that exactly the approved change is applied, and the downloaded package matches what was signed.

Memory under control

A password the agent wants to remember is refused. Data waiting for consent cannot be read. Forgotten data stays forgotten, even after a restore.

Detected

A bulk write into the vector store that bypasses the gateway is detected, and the altered entries are rejected.

WHAT THESE RECORDINGS ARE

An honest
pilot build.

The model, the search index and the vector store are test stand-ins, labelled on screen. In the refunds demo the agent and the customer follow a script. The demos show what OWAI OS does with a proposal, not the quality of a model.

OWAI OS is in pre-production. The recordings show one server without high availability; it is not a production deployment and carries no certification. Consent is recorded, not verified.

A pilot runs the same checks on your server, with your policy, your agent and your data, within scope agreed in the pilot terms.Discuss a pilot