> ## Documentation Index
> Fetch the complete documentation index at: https://docs.leedab.com/llms.txt
> Use this file to discover all available pages before exploring further.
# Introduction
> Operators that run your back office while you sleep.
## What LeedAB is
LeedAB is an AI operating system for your back office. You describe your business once, and LeedAB hires you a team of **operators**: specialist AI workers (LeedAB calls them Artificial Beings) that do real work across your portals, inboxes, ERPs and spreadsheets.
They are not a chatbot bolted onto a dashboard. Each operator has a job, takes actions, and reports back. A **COO** ties the team together and sits on every screen, surfacing what needs your decision and routing the work. Every action, whether a person clicked it or an operator proposed it, is governed and written to a tamper-evident audit trail.
Each workspace is one company's operating system. Spin one up in about two minutes.
The specialist workers you hire. Built-in or custom, each with a job and a code.
The orchestrator that lives on every screen, surfaces decisions, and routes the work.
Operators propose, you confirm. Authority is enforced server-side and every action is logged.
## How it works
Tell LeedAB your role and what you spend most of your time on. It reads your operation and hires the right operators for your industry, from a template or tailored to you.
Your operators land in a workspace, already briefed. They draft work, flag what needs a call, and act on what you approve.
The COO surfaces the next move on every screen. You approve, redirect, or ask a question. Nothing consequential happens without a human confirm, and everything is on the record.
## Why it is different
* **It does the work, it does not just answer.** Operators take governed actions, not just replies.
* **One brain, one set of numbers.** Every operator and every dashboard reads the same live data, so they always read the same numbers.
* **Safe by construction.** An operator cannot exceed its authority. Authority is re-derived on the server, never taken from what the model says, so a hijacked or hallucinating operator cannot move money or push a change through on its own.
* **Auditable end to end.** Every action lands in a hash-chained log you can filter, export, and lock by period. Exactly the evidence an auditor asks for.
Create your workspace, meet your operators, and run your first action.
See every built-in operator, its code, and what it is authorised to do.