Skip to content
XS1
Work with XS1 Automation

Automation fails when it is delivered as a one-off. Every XS1 Automation system moves through the same four phases (Map, Design, Deploy, Improve) and keeps tightening around the real work it does.
Work with XS1 AutomationRead the safety model

The four phases

Map and design once, then deploy and improve on repeat

Map and Design happen before anything runs. Deploy and Improve repeat for as long as the loop is in service. When the work itself changes or the scope grows, what Improve learned goes into a new map.

Phase 01 of 04MapWhere does the work stall, and which decisions need a person?
Select a phase to stop on it.

Autonomy

Autonomous, within limits a person sets.

Routine, in-scope steps run on their own. Anything sensitive, destructive or visible outside your team waits for the workflow owner's approval.

Workflow owner
The named person on your team who owns a workflow, approves sensitive actions and can pause any loop at any time.

Runs on its own

Routine, in-scope steps

  • Scheduled and event-triggered runs
  • Reading from the sources in scope
  • Drafting, summarizing and checking
  • Status updates to the workflow owner

Waits for the workflow owner

Sensitive, destructive or external actions

  • Anything sent outside your team
  • Deleting or overwriting records
  • Payments, purchases and access changes
  • Anything outside the agreed scope

Safety model

Six rules engineered into every system

These constraints are built into the system, not promised in a document. They are what make it reasonable to leave a loop running.

  1. Rule 01

    A person stays in charge

    Every system answers to a named workflow owner on your side, and no agent can override their decision to pause it.

  2. Rule 02

    Scoped permissions

    Each agent works inside a defined scope of tools, data and actions, with its own least-privilege credentials.

  3. Rule 03

    Approval before anything sensitive

    Approval gates are part of the workflow itself: the run holds at the gate until the workflow owner signs off, and the sign-off is recorded.

  4. Rule 04

    Visible while it runs

    Task state, approvals and blockers can be seen as the work happens, not only after it finishes.

  5. Rule 05

    Traceable and reversible

    Every action is logged with the agent that took it and why, and changes are made so they can be rolled back.

  6. Rule 06

    Credentials kept out of context

    Credentials never enter agent context. Personal data is limited to what a task needs and is not echoed into transcripts or reports.

Start here

Map one workflow with us.

The first phase is a conversation about how the work runs today. Tell us which workflow you have in mind and who owns it.

Work with XS1 AutomationContact