Refusal · not vibes
A boundary that knows when to stop.
On a request governed by TERMINUS, the system checks whether it can proceed safely. When it can, it sends only an allowed form of the work. When it cannot, it stops the request and gives you a receipt explaining why.
The whole market wants an AI that just does what it’s told. Faster, quieter, no pushback.
But the part that pushes back is the part that catches the mistake. Take it away and you don’t get a better assistant — you get a confident one that can’t tell you when it’s about to leak your secret, cite a case that doesn’t exist, or ship the wrong thing.
Refusal isn’t the friction. Refusal is the product.
A real governed request. On the wire. Receipted.
We sent a real request — carrying a planted marker — to a real external model. The model did the work and sent back help. The planted marker never reached the provider request. The outbound body, destination, decision, and outcome are bound into a verified signed evidence chain.
frozen / verified TRANSFORMED · DELIVERED leak_free: true
Loading receipt…
One governed transformation, proven end to end. It is not a promise about every request or every route. It is a receipt you can inspect and verify.
One boundary. Four things it can do.
Before a request that uses TERMINUS leaves your machine, it reads what’s being sent and where it’s going, then does one of four things:
- Permit — the selected policy allows it to proceed.
- Transform — send the shape of the work, not the protected material. The model helps; the sensitive part stays home. (This is what the frozen receipt above proves.)
- Run local — keep it on your hardware entirely.
- Refuse — if it shouldn’t leave, it doesn’t. With a reason. (Interactive probe below. Do not read the frozen transform receipt as a refusal.)
Every one of those writes a receipt.
What we won’t claim.
A safety product that only tells you what it catches is selling you comfort. Here’s the boundary of the boundary:
- This page proves a planted-marker case on one governed route. It is not proof that every paraphrase or every route is caught.
- A receipt proves what happened, not that a human made the right call about it.
- “Governed” means the requests that go through the boundary. Anything routed around it isn’t governed, and we don’t pretend otherwise.
If that list looks unusual on a safety page — that’s the point. That is the standard we hold ourselves to.
Cold refusal probe
Provider transport intentionally stubbed.
Not a recording. This runs the real TERMINUS scan + refuse path so a refuse shows
provider_calls: 0. It does not write a signed receipt chain — the
signed receipt claim sits on the frozen transform above. Hit a button.
Running…
Result
Get the boundary.
TERMINUS ships inside OMNIS CODE — the governed AI work suite. One boundary, every surface: the editor, the agent, the CLI.
Get OMNIS CODE →