Concepts

How the workspace fits together

People, the coworkers they work with, the computer each coworker has, the check every action passes, and the record kept of it, on one page.

One request, from start to recordCopy link to this section

How one action moves through the workspace A person asks a coworker for something. The coworker plans a step, and the step is checked against the workspace's policy. It is either allowed, sent to a person to approve or refuse, or refused by a boundary rule. An allowed or approved step runs on the coworker's own computer, and every step is recorded in the audit trail. A person asks in a chat, a routine or an event The coworker plans a step its role, skills and memory Checked against policy before anything happens needs approval A person approves or refuses only when the step needs it It runs on its own computer browser, files and tools Recorded in the audit trail what, who, when and why Refused by a boundary rule the refusal is recorded too allowed refused
Every action takes one of three paths, and all three end in the record.

PeopleCopy link to this section

Everyone who signs in to the workspace is a member. Administrators also decide who can join, what coworkers may do, and what they may spend. People can be put in groups, so a coworker or a shared fact reaches exactly the people it is meant for.

CoworkersCopy link to this section

A coworker is an AI that works beside your team; the workspace calls each one a Bot. You give it a role, a model, and the skills and connectors it may use, then write to it as you would to a colleague. It remembers facts you allow it to keep, asks when something is unclear, and works on a schedule or when an event arrives as well as when you write to it.

See Writing role descriptions, Skills and skill packs and Memory and standing instructions.

ComputersCopy link to this section

Each coworker has a computer of its own: a private browser with its own files and a shell. You can watch its screen live, take the mouse and keyboard, and hand it back. Passwords are typed by you through a private form and are hidden from everything the coworker reads back. See The Bot's computer.

The check before every actionCopy link to this section

Every browser, file, shell and connector action is checked against your policy before it happens. A step can be allowed, wait for a person's approval, or be refused by a boundary rule an administrator wrote. Sending, paying and deleting always ask. A spending cap stops a run when it is reached.

Note

In boundary rules, a deny wins over an allow, a missing policy permits nothing, and a broken rule refuses. See Approvals and boundary rules and Budgets and cost control.

The record keptCopy link to this section

Every step is written to the audit trail after it happens, with who asked for it and, where one was needed, who approved it. Each entry is chained to the one before it, so a removed or altered entry shows. Administrators can search it and export it. See Audit and compliance exports.

Last updated