The Brain / Capabilities
Every capability, in plain language.
What WorkElate Chief, the Brain, notices, remembers, judges, is allowed to touch, and is allowed to say it did, with your data where it is.
What the Brain does inside a 200 to 2,000 person company
Each card names the work it removes; how it is built explains the one process behind all six.
It notices what changed, unasked.
It reads what your systems already record, treats a quiet thread as an event, and interrupts at most 40 times an hour, 5 per person.
It gathers the whole picture first.
One map of how deals, threads, tickets, documents and people connect, plus what was decided last time and what the contract says.
It judges each case, not a rule.
It weighs the context against what this role cares about, asks when ambiguous, and most of the time stays silent.
It does the work, a person decides.
Fifteen things it can be asked to do reach 287 actions, and the 71 that send, delete or share stop for a person.
It only claims what actually happened.
It checks the change landed before saying so, checks its reply against what the tools returned, and says no when it cannot.
Nothing replaced, acting only as who signed in.
Your systems keep owning the data, a twelfth system costs what the second did, and memory is never training material.
Every capability, on its own page
One page each: what it looks like on a Tuesday, how it works, and what it is not.
What it notices without being asked
It finds who really holds it, and tells them.
A message to a channel of twelve is a message to nobody, so the Brain works out who really holds an item and addresses them.
02It interrupts anyone only a few times an hour.
The Brain may interrupt anyone at most 40 times an hour across the company and 5 per person, and never raises the same item twice.
03It listens to what your systems already record.
Every tool your company runs already records its own events, and the Brain reads them as they happen instead of crawling a stale copy.
04It notices when nothing has happened for too long.
A thread quiet for nine days, an approval nobody chased: no system records these, so the Brain works them out from the last thing that did happen.
05It says what changed , not just that something did.
A notification says something moved; the Brain keeps which field, on which record, what it was before, who moved it and when.
06Work becomes urgent before the meeting asks.
Work is due before the meeting where somebody will ask about it, so urgency rises as that meeting approaches and drops after.
One memory where there used to be five
Ask about a client, get the client, not documents.
One map of how your deals, threads, tickets, documents and people connect, so a question about a client returns the client.
02Four spellings of one client, treated as one client.
Northbeam Ltd, Northbeam Limited, NORTHBEAM and northbeam-2019: the Brain decides those are one client, once, and everything stands on that.
03It remembers why, so you never explain twice.
The Brain writes back what was decided, when and on what grounds, so the next decision opens with the reason in hand.
04One client’s question reads that client’s folder, nothing else.
One folder holds the brief, deck, sheet, form and chat, whichever app made each; a question about that client reads that folder and stops.
05Your company’s memory stays your company’s.
Every fact it keeps is stamped with whose it is, and it only ever reads yours.
06Your contract, read at decision time, not typed-in rules.
The Brain reads the statement of work, the terms and your written policy at the moment it decides, not rules typed in once.
Judgment, not rules
A short morning list, each item with its reason.
A short ranked morning list, and every item carries why it is in front of you and what is holding it up.
02Change its behaviour by saying so in plain words.
Tell it nothing before nine, and that is the setting: how often the Brain may interrupt, when and to whom, kept as a sentence.
03Related work and the contract, read before answering.
The answer to a serious question lives in four places: the work next to it, the thread, the decision taken in March, the document you agreed.
04Small things run fast. Consequential things stop for you.
Reversible work runs fast and cheap; irreversible, client-facing or financial work gets the strongest reasoning and stops for a person.
05The same event ranks differently for each person.
The same event ranks differently for each person, read from what they carry and what they worked on this week.
06Three questions before it interrupts anyone.
Three cheap checks run before the AI is asked one question: does this deserve this person now, and why.
07Two possible meanings, one instruction. It asks which.
When a request could mean two things, the Brain asks which, because a confident wrong answer costs more than a question.
It does the work, and a person decides
Fifteen things it does. The list only gets shorter.
Fifteen verbs, find to assign, are the whole of what the Brain can be asked to do, and adding an app never adds one.
02Filed where the next question finds it.
The Brain creates and files in one action, into the folder holding the client’s brief, sheet and thread, so the next question finds it.
03One date changes everywhere, and it checks it did.
A date that reaches three systems through three people is written once, into the system that owns the field, then checked.
04One request, several steps, one confirmation.
A four-step request runs as one piece of work across apps, and only the step with consequences stops for a person.
05The move proposed, evidence beside it. A person confirms.
The Brain proposes a state change or an owner when the evidence exists, shows the evidence beside it, and a person confirms.
06The reply is already drafted. You read and decide.
The Brain gathers from the thread, the document and the tasks around the thing being written, composes it, and stops for you to decide.
07Whatever sends, deletes or shares stops for a person.
71 of the 287 actions the Brain can take reach outside: send, delete, share.
What it is allowed to claim
It checks the change landed before it says so.
A success flag is a self-report, so before the Brain says a change is done it goes back and looks for the record.
02What it tells you is checked against what happened.
Before a reply reaches you it is compared to what the systems returned, so an update that matched nothing is reported as such.
03When it cannot, it says so, naming what’s missing.
Either the Brain knows exactly what you asked for, or it says so and names what is missing.
04Wrong calls become tests it never fails again.
Every decision the Brain got wrong is kept as a stored case with the right answer, so a change that would reintroduce it fails first.
The parts a CIO asks about first
From something happening to something finished, one path.
Every change takes one path: noticed, put in context, judged, acted on with a yes, remembered.
02It acts only as the person who signed in.
Every action carries who is asking and which company they belong to, both read from the sign-in, never from the AI.
03The alert and your question, one thread that remembers.
An event from your systems and a typed question take the same path, read the same memory, and land in the same thread.
04The twelfth system costs what the second one cost.
Integration platforms rot because a list has one row per system; the Brain keeps no such list, each app describes itself.
What this is not
Not a search box, not a chatbot on one application, not a rules engine, and not a system you migrate into.
Updated 15 September 2026 · WE_AINA