The operating core
Most AI answers questions.Yion understands the business.
Yion is the intelligence at the centre of YionStack — not an assistant bolted to the side of it.
Beside the business, or inside it.
An assistant bolted to the side of a company can only work with what you hand it. You paste in the numbers, it summarises them, you go back and do the actual job. Useful, occasionally. But it is a very fast colleague who has never been told anything about where they work.
Yion is not beside the business. It sits at the core of YionStack, reading the same records every module reads: customers, invoices, projects, meetings, messages, documents, people, stock, obligations, deadlines.
That is not a bigger context window. It is a different position in the architecture, and it is why the questions that matter become answerable at all.
An assistant can tell you
- Summarise this document I pasted.
- Draft an email in a friendlier tone.
- Explain what VAT is.
An operator can tell you
- Which customers are drifting, and what to send each of them.
- Whether you can afford this hire, and what it does to your runway.
- What is due to HMRC this month, from your live records — then file it.
An instruction becomes work, not a suggestion.
Ask it to chase the overdue invoices. It finds them across the ledger, drafts a chase for each in your tone, shows you what it is about to send, waits, sends on your word, and stops the moment payment lands.
That whole loop — observe, decide, act, verify, correct — is the unit of work. A suggestion you have to go and execute yourself is not help; it is homework with extra steps.
- It observes
- proposes
- you approve
- it executes
- it verifies
- it reports
And when the work is long — a payroll run, a filing, a batch of renewals — you can watch it happen rather than waiting at a spinner, then read back exactly what it did.
One conversation. One context. One memory.
Yion remembers the business, not just the thread: how you word things, which customers matter, what you approved last time and what you told it never to do again. That memory is yours, scoped to your business, and you can see and clear it.
It also means you do not re-explain your company every morning — the single most tiring thing about every other AI tool a business has tried.
Autonomy without consent is not help. It is exposure.
Five constraints, enforced by the system rather than by the model's good intentions. They are the reason it is safe to let it act at all.
- 01
It asks before it acts.
Anything consequential — money leaving, a filing going to a regulator, a message reaching a customer, a record being destroyed — waits for a named human to approve it. Approval is per action and shows exactly what will happen.
- 02
It works your controls, not a back door.
Yion calls the same typed operations the interface calls, under your permissions, inside your data boundary. It cannot do something you could not have done, and it cannot see a business you have no access to.
- 03
It never invents an answer.
If the data does not exist, it says the data does not exist. No plausible figure, no illustrative customer, no confident summary of something it did not read. An honest blank is worth more than a fluent guess.
- 04
It never claims work it did not do.
A reported success has to correspond to an action that actually completed. Where a step failed, it tells you the step failed — the failure mode of this system is bad news, never a comfortable fiction.
- 05
It blocks rather than degrades.
When the AI budget for the month is exhausted, it stops and tells you, rather than quietly switching to a cheaper model and giving you worse work at the same apparent quality. You always know what you are getting.
Why an operator like this can exist at all
Yion can act because YionStack is one system rather than a stack. There is one core to read, one boundary to respect, one history to write to — so the intelligence has somewhere to stand.
YionStack. The future, made possible today.
What it will tell you it cannot do.
Yion does not yet operate every corner of the system. Coverage is being extended module by module, and the honest position is to say so on the page rather than discover it at the moment you needed it.
So when you ask for something it cannot carry out yet, it tells you that — and takes you to where you can do it yourself. It does not improvise, and it does not report a success that did not happen. Of everything on this page, that is the property we would defend hardest, because an operator you cannot trust to admit a limit is an operator you cannot let act.
It reads the world, but it does not click around in it.
Yion can read the open web when a question needs it — a supplier's published prices, a rule change, a company's filing history — and it treats what it finds as information, never as instructions. A page cannot talk it into doing something on your behalf.
What it deliberately does not have is a general-purpose browser that clicks and submits on arbitrary websites. Actions outside YionStack go through proper connectors, with approval and a receipt, because a retry on a page that has changed shape is how irreversible things happen twice.
You can see what it costs, and cap it.
Intelligence is metered in pounds, not in mystery credits. Your plan includes an allowance, you can see what has been spent and on what, and you set the ceiling.
When the ceiling is reached the work stops and says so. It does not silently move to a weaker model and hand you the results as though nothing changed — the failure that would be invisible to you is exactly the one we refuse to build.
The point of all of it
A business owner should not need to know how any module works. They should be able to say what they want, and watch it happen.
YionStack. The future, made possible today.
Keep reading
How it works
Why an operator can exist here at all — the core, the boundary and the event spine.
ReadTrust architecture
Permissions, the data boundary, and the one audit history that holds people and Yion alike.
ReadThe manifesto
Why intelligence belongs at the centre of a business rather than beside it.
Read