Staff

What you need, when you need it.

Staff is a personalized digital operator that works continuously across your work and life. It maintains context, prepares what matters before you ask, challenges your thinking and helps turn decisions into action. You remain in control while Staff builds knowledge, tracks commitments and keeps approved work moving between interactions.

How the pieces came together

Built around you

One relationship across work and life.

Your decisions do not fit neatly into separate systems. Work, family, travel, relationships, interests and financial responsibilities compete for the same time and attention. Staff starts with that reality. It brings together the context needed for the decision in front of you while keeping the boundaries between sources, roles and responsibilities intact.

You work with one Staff. Behind it, company information, personal context, research, communications and specialist capabilities remain separated by identity, source and policy. without asking you to manage a collection of disconnected assistants.

One Staff. The right context and capabilities brought together around each decision.

01

Reality changed

At 07:20 ET, Kate — the procurement lead at Insprod — moved Thursday's signing to Monday. Nobody told you, and your calendar still assumes the original plan.

02

Staff adapted

Staff re-sequenced the week, told Jack and Amit to hold the two approvals that only matter before signing, flagged the changed date for the board pack, and wrote Marketing to freeze Thursday's release while the announcement decision is resolved.

03

It asked for your judgment

One thing Staff did not decide: whether you still announce on Thursday without a signed copy. That affects your credibility with Insprod and the board, so Staff brought the decision to you rather than making it for you.

7:24
StaffNow

Since yesterday

Three things changed. One needs you before lunch.

Insprod signing moved to Monday

Kate confirmed 07:20. Four dependent items re-sequenced.

Handled

Two approvals held

Jack and Amit — released automatically once signing confirms.

Handled

Announce Thursday without a signed copy?

Board pack and Insprod both affected. Marketing is holding the release.

Decide

Hold to talk

Continues in the car — same context

Illustrative Staff surface. The real interface is in development.

One Staff, guided by cognitive governance across all your relevant domains.

Each domain keeps its own identity, permissions and source and trust boundaries. Staff works across all of them as one operator rather than a collection of separate assistants — using what is relevant and permitted for the decision in front of you, without merging the domains into one pool. The set is extensible; these are the ones Staff operates across today.

GUIDE is the set of principles behind that governance, applied the same way in every domain: , , , and .

Deep dives+

Why now

Forty years of technology are converging.

Almost forty years ago, Apple’s Knowledge Navigator imagined something extraordinary: computing that understood context, worked through conversation, connected ideas and prepared ahead of a request. The vision was far ahead of the technology available at the time.

Since then, the missing layers have arrived one by one. Personal computing brought capability closer to the person. Networks and mobile made it continuously available. Digital systems made work observable. Cloud and APIs made services composable. Data platforms made knowledge richer. Modern AI made broad reasoning practical. .

Staff brings those capabilities together around one person. It spans the technology timeline rather than becoming another box at its end. As new models, devices and forms of computing arrive — , , — Staff can absorb what is useful without asking you to rebuild your context, knowledge and way of working around each new technology.

The technology will continue to change. Your operating relationship should continue to compound.

Select any technology change below to explore what shifted, what it enabled and how it contributes to Staff.

2026

Governed agentic AI

Staff capability: Action + authority

What changed

Agents that plan, call tools and carry work forward move into routine use, which turns the governing question — what may they decide alone — into a practical one.

What Staff carries forward

Authority, policy, audit and follow-through sit around execution, so Staff can act usefully without acting beyond what you have delegated.

What it enables

Accountable autonomy

Deep dives+

One continuous day

A day with Staff.

Luke leads the commercial business for interactive retail displays at a European specialist monitor company. He owns revenue, product direction and the P&L while the business expands into the United States. His day crosses customers, product, people, budget and delivery — alongside lunch, an airport pickup and a late call from home.

Staff carries the same context across the day. It prepares before Luke asks, moves between work and personal commitments, challenges the apparent problem and keeps approved work moving when Luke turns his attention elsewhere.

Nine moments. One continuous operating context.

Every moment reads the same way: what happened, what Staff prepared, what Luke decided.

Interface shown is illustrative, on the Staff shell described in the design programme.

0107:15

Staff: Here is the shape of your day.

What happened?

Overnight the day changed shape: two items carried over, Sue's flight was confirmed for 16:40, and the commercial review moved into the morning.

STAFFMorning brief

Now

Attention

Work

Agents

Office morning — commercial review first

Lunch at 12:30

US expansion prep before 15:00

Pick up Sue from the airport at 16:40

Take the late call from home

Two open items carried from yesterday

Context

Calendar

Overnight

Staff prepared

Calendar, open commitments, travel and overnight work are already reconciled into one view.

Luke decided

Adjust one timing assumption and move on.

0209:00

Staff: Your first meeting is prepared.

What happened?

The commercial review starts in fifteen minutes. Two of its agenda items need a decision from Luke, and no position has been prepared.

STAFFCommercial review

Now

Attention

Work

Agents

US expansion update

Retail partner pipeline

Pricing decision

Product roadmap dependency

Two decisions need Luke

Context

Numbers

Decisions

Staff prepared

Latest numbers, prior decisions, stakeholder context and the unresolved pricing question are assembled around the decisions required.

Luke decided

Review the decision points instead of preparing the meeting from scratch.

0310:30

Staff: Yesterday's post is getting unusual traction.

What happened?

Yesterday's post kept running overnight. Among the comments is an MD at a company already in the sales pipeline.

STAFFReaction summary

Now

Attention

Work

Agents

61 reactions · 18 substantive comments

Top theme: continuity during rollout

Kate — MD, SouTech — added a useful client angle

Response prepared

Note for Pete in Sales prepared

Context

Kate, SouTech

Pipeline

Staff prepared

Staff recognizes the reaction as a commercial signal, connects Kate to an active sales context and prepares a response and internal note.

Luke decided

Approve, adjust or hold the response.

0411:20

Luke: How ready is the research for the proposal?

What happened?

Luke asks, in the middle of the morning, whether the research behind the proposal is actually ready to stand behind.

STAFFResearch position

Now

Attention

Work

Agents

Financial-report review is current

Bloomberg prediction still holds against the evidence

Potential client concern: continuity

Next useful test: product-roadmap cross-reference

Deeper comparison can continue by voice in the car

Context

Financials

Evidence

Staff prepared

Maintained research has already been tested against new financial evidence, with the next useful comparison ready.

Luke decided

Ask Staff to continue the product-roadmap cross-reference.

0512:55

Staff: The flower shop is on your way back.

What happened?

Luke is finishing lunch. Sophie's birthday is Saturday, the flowers were ordered on Tuesday, and the shop holding them is two streets from the restaurant.

STAFFOn your route

Now

Attention

Work

Agents

Sophie — birthday Saturday

Flowers ordered Tuesday, ready now

Bergmann's — 200m, on your walk back

Held until Friday if you'd rather not

Afternoon preparation unaffected

Context

Personal

Route

Staff prepared

Staff placed the order when the date approached, then held the reminder until Luke was near the shop with time in hand rather than firing it that morning.

Luke decided

Collect them on the walk back, instead of adding an errand to the evening.

0613:45

Staff: The release is at risk — but not for the reason the team is debating.

What happened?

A long Marketing and Product thread has spent two days arguing about the release date, and the argument is about the wrong constraint.

STAFFCritical-path deviation

Now

Attention

Work

Agents

Source: long Marketing / Product email thread

Root constraint: staff allocation

Secondary constraint: budget

Impact: release timing is now at risk

Decision: protect release by reallocating budget

Context

Thread

Budget

Staff prepared

Staff connects the email thread to the release commitment, resourcing plan and budget, exposing the actual constraint.

Luke decided

Direct Finance to test the reallocation and inform the team.

0715:35

Staff: You need to leave in ten minutes. I can switch the brief to voice.

What happened?

The airport run is ten minutes away and the brief for the next meeting has not been read.

STAFFChannel hand-off

Now

Attention

Work

Agents

Meeting objective and two decision points

One customer relationship to handle carefully

Proposal research parked at the deeper comparison

Pick up Sue remains protected

Continue by voice when driving

Context

Meeting

Research

Staff prepared

The same meeting context, research position and commitments are ready to continue by voice.

Luke decided

Leave on time without restarting the work.

0817:05

Luke: Move dinner an hour later.

What happened?

Luke is driving home after the airport run. The 19:00 dinner is now uncomfortably tight.

STAFFVoice — on the way home

Now

Attention

Work

Agents

Dinner moved to 20:00 — confirmed

Restaurant notified

Tomorrow's first meeting starts 10:00

Move your alarm back 30 minutes?

Nothing else this evening moves

Context

Personal

Tomorrow

Staff prepared

Staff changed the booking, then noticed tomorrow's first meetings had already shifted later and offered the alarm change rather than making it quietly.

Luke decided

Confirm both by voice, without opening anything.

0917:20

Staff: I will keep the proposal work moving while you are offline.

What happened?

The working day ends with the proposal research parked halfway through a comparison.

STAFFBackground continuation

Now

Attention

Work

Agents

Cross-reference product roadmaps

Retain supporting evidence

Check for contradictions

Prepare the next question, not a long report

Surface when Luke is ready

Context

Roadmaps

Contradictions

Staff prepared

Staff continues the bounded research task, checks for contradictions and prepares the next useful question.

Luke decided

Switch off knowing the work will return when it needs attention.

Deep dives+

Built for trust

More capability. Your authority remains intact.

Staff is designed to become more capable without becoming less accountable. It can prepare broadly, reason across several sources and keep bounded work moving. What it may know, decide and do remains governed by identity, source, policy, risk and your authority.

The Personal Operator Architecture is the operating foundation behind Staff. It maintains current state, knowledge, attention, reasoning, authority, execution and evidence as Staff assets — independent of any single model, tool or interface. We call the discipline .

That allows new models, devices and integrations to strengthen Staff without taking ownership of your context or changing who remains in control.

Five commitments to you

Guard
Protects identity, boundaries and authority.
Understand
Maintains context and current state.
Integrate
Brings together relevant knowledge and capabilities.
Decide
Prepares judgment without taking it away.
Evolve
Adds capability without resetting the relationship.

Personal Operator Architecture

The operating architecture that keeps Staff continuous, personal and accountable.

Executive Experience

Brings forward what changed, what matters and what needs your judgment.

Select any part of the architecture to see how it supports Staff, then open it for the full explanation and its deep dives.

Deep dives+

Go deeper

Explore the thinking behind Staff.

The public page explains the product and the experience. The Capabilities paper describes how state, knowledge, reasoning, authority and execution work together across eleven pages. The Investor Summary sets out the situation, the day and why the market keeps widening, in three.

Technical

Staff Capabilities →

Eleven pages on state, knowledge, cognition, attention, authority, execution, provenance and runtime.

Investor

Staff in three pages →

A morning that went wrong, a day that did not, and why the market keeps widening.

The vision

Personalized digital operators are the next evolution of personal computing.

Every era of computing has moved capability closer to the person. The mainframe served an institution, the personal computer served a desk, the network served a household, the phone served a pocket. Each step was real. Each step also arrived with machinery the person was expected to operate: files to organise, applications to choose between, accounts to reconcile, context to carry from one tool to the next.

That machinery has never actually gone away. It was redistributed. The work of being the integration layer — knowing which system holds which fact, restating the same background to a different tool, noticing that something changed and deciding what it means — still lands on the person. Capable models did not remove that work. In many settings they added to it, because now there is also a model to choose, a context window to fill and an output to check.

Staff takes the opposite position. The durable thing is not the model, the device or the interface — all three will be replaced, probably more than once. The durable thing is the operating relationship: what it knows about your situation, how it works with you, and . Those are held outside any component that can be swapped.

This is what makes the coming changes additive rather than disruptive. Models will keep improving. More reasoning will move to private and on-device environments, for reasons of latency and cost as much as privacy. Interfaces will expand from screens to voice, wearables and ambient systems. Under this design each of those arrives as more capability underneath an unchanged relationship, not as a migration you have to survive.

It also sets the limit deliberately. More capability is not more permission. A system that can act on your behalf has to be explicit about what it may know, what it may decide alone and what it must bring back to you — and that boundary should move only when it has been earned, visibly, in a specific domain, rather than granted wholesale because the underlying technology got better.

The direction of travel is consistent even though the parts mature at different rates: from explicit workflows toward quieter orchestration, from connected systems toward ambient context, from scheduled preparation toward continuous readiness, from bounded action toward earned autonomy. That is a direction, not a roadmap with dates.

Deep dives+

As technology expands capability, the machinery should increasingly disappear. What remains unique is you.

What you need, when you need it.