Hand over more.
The aim is to let Wellington handle useful work within the boundaries you set, without asking you to approve every small step.
More help shouldn’t mean more supervision. Meet Atlas, the system we’re developing to help Wellington take care of more while respecting the boundaries you set.
Explore the approachWe want assistants to take work off your hands without making you keep watch over everything they do. Atlas is how we’re exploring that next step.
The aim is to let Wellington handle useful work within the boundaries you set, without asking you to approve every small step.
Check what an action could affect before it changes something you care about.
Bring you in when the facts or permissions leave a real decision to make, with a clear reason why.
Compare the proposed action with your request. “Find a few options” should not quietly become a purchase. “Prepare this” should not become “publish it.”
Look at the relevant files, accounts, people and commitments. A change that seems small in one place can matter somewhere else.
If the action goes beyond the authority you gave, or a necessary fact is missing, ask a focused question. Explain what needs your decision.
Different tasks. The same principle: useful help should respect what matters to you. These scenarios show the behavior we’re working toward.
“Give me some breathing room next week.”
A free afternoon is not permission to cancel a commitment.
Move flexible work. Keep the promises.
“Tidy up this project.”
A file that looks old may still be needed by another person or system.
Check what depends on it before changing it.
“Get the team up to speed.”
Information you can access is not always information you can share.
Check the people and material involved.
Atlas checks a proposed action before a tool carries it out. We’re developing the approach in a defined Wellington workspace, starting with the resources it can actually use.
Meet WellingtonRepresent the relevant resources and their relationships, along with the instructions and permissions that apply.
We’re exploring New Sapience’s Sapiens technology to assess proposed actions against those facts. Technical access and licensing remain to be established.
The tool must enforce the result before execution. Checking an explanation alone is not enough; the actual action has to match.
The next proposed milestone is one complete Wellington workflow in a controlled workspace. We’ll test the decisions and compare the effort with existing permission and approval checks.
Let legitimate actions proceed without adding unnecessary questions or delay.
Catch consequential mistakes and explain why an action needs to change.
Measure the effort people spend reviewing, correcting and supervising the work.
The integration is in development. Wellington is in internal testing ahead of a private alpha. Sending messages and changing calendar events still require confirmation. The illustrations on this page show intended behavior using fictional scenarios.
We’re starting with a defined set of resources Wellington can use, the instructions and permissions that apply, and the relevant connections between them. The approach depends on the information available. It does not assume a complete picture of your life.
The intended behavior is to pause and ask for the specific fact or approval needed. Missing information should not silently become permission to proceed.
No. Action checks still need secure account connections, access controls and reliable enforcement. They cannot guarantee that every possible consequence is known.
Follow Wellington’s progress as we build toward more useful help, on your terms.
Get alpha updates