The Brain / Capabilities / Role-aware scoring
REASONThe same event ranks differently
for each person.
A slipping milestone is the delivery lead’s first line, the finance lead’s fourth, and nothing to the CIO, and nobody configured a thing.
One signal, three inboxes, three answers
For the delivery lead, item one
She owns the engagement, edited the plan yesterday, and Thursday’s client review moves if this does not land today.
For the finance lead, item four
He owns the month, not the engagement, and a late confirmation pushes a milestone invoice past cut-off.
For the account director, nothing
She has not touched this engagement in six weeks, and raising it would spend one of her 5 interruptions per hour.
Two inputs, one thing deliberately absent
The role is read from the work
Who owns which engagement, who approves what, who is on the thread: the connected systems already hold those facts.
Recent activity counts, and it fades
What you read, reply to and edit raises the weight of the work around it, and a project left in April fades.
No per-role branch in the Brain
No code says if the reader is a CFO; the role is context handed to the AI, so an unusual operating model still gets a sensible order.
Three honest limits
Not a permissions model.
It does not know an org chart you never wrote down.
It will not rank a quiet week into an urgent one.
Updated 15 September 2026 · WE_AINA
Book a Diagnostic Sprint
Bring two people with different jobs and see one week ranked two ways.