Part of Atlas OS
Atlas can take on tasks, prepare decisions and work with your existing systems. You set what happens automatically, when your approval is needed and what stays off limits.
Part of Atlas OS and included in every deployment, never an add-on.
Six principles
What a person may see is decided by your user directory and the permissions in each connected system, not by Atlas.
An action that needs approval goes to the person accountable for it and waits for their decision. Boundaries are explicit and visible, and only a person can widen them, never Atlas itself.
Exceptions, approvals and policy stay with people. Atlas takes on coordination and routine work. Autonomy does not mean absence.
This covers current actions, running processes, the context each one works from and every point where a person is needed.
Each record holds what ran, on whose authority, against which context and what it changed.
Retention and classification are enforced by the same layer that does the work.
What Atlas may do
Every kind of task gets one of three answers: Atlas does it, waits for your approval, or leaves it. These are the defaults, and you adjust them to your company.
AutomaticAtlas carries this out on its own. Like every action, it is recorded.
| Class of action | Runs on its own | Needs approval | Does not execute |
|---|---|---|---|
| Reading a recordIn a connected system, within the permissions of the person asking | Runs on its own | ||
| Preparing workA draft document, a message, an analysis, a proposed decision | Runs on its own | ||
| Updating a recordWriting back to the system of record | Needs approval | ||
| Communicating externallyAnything sent to a customer, a supplier or an authority | Needs approval | ||
| Taking an irreversible stepDeletion and every other step that has no way back | Does not execute | ||
| Widening its own accessGranting itself a permission it was not given | Does not execute |
These boundaries apply to every product. Command recommends and never approves its own recommendation. Forge executes and stops at a step whose result it cannot verify. Systems not connected to Atlas stay untouched.
With every action
01 Before
Who asked, what they may see, which class this action belongs to and where its boundary sits. If the action lies beyond its boundary, it waits for approval or does not run.
02 During
What is running, what it has touched and whose approval it is waiting for. None of it is reconstructed from logs afterwards.
03 After
The record keeps the reasoning behind every action, so a later review sees why it happened.
Information security, data protection, access rights and organisational policy are part of the Atlas architecture: transparent, traceable and aligned with your company's governance.