Book a 30-minute diagnostic

An operating system for AI agents

Hand the work to AI.
Keep the decisions.

A simple loop that lets agents build for you, while you decide, see the evidence and sign. No code to read. Nothing closes without you.

  • Owner decides
  • Agent builds
  • Evidence, not promises
  • Works with Claude Code
See how the loop works Book a 30-minute diagnostic

Free core · open to inspect

01 · The idea

Three roles. One of them is you.

AI agents are fast and sometimes wrong. The loop gives each party one job, so speed never replaces judgment.

  • Owner · you

    Decides and signs

    Sets the goal, approves what matters, and is the only one who can close a risky piece of work.

  • Director

    Plans and checks

    Turns your intent into small, bounded orders and verifies the result against the disk, not against a summary.

  • Executor

    Builds, in a box

    The coding agent does the work inside limits: a budget, a scope, and files it is not allowed to touch.

Rule of the loop:an agent can propose and build. Only the owner can approve and close.

02 · The loop

Six steps. Every one leaves a trace.

  1. Step 1

    You say what you want, in your words.

    For example, you write “add a contact page”. Nothing else is needed from you yet.

  2. Step 2

    The director writes a small, bounded order with a budget.

    The order names its budget in minutes and attempts, its risk level and the checks that will prove it is done.

  3. Step 3

    The executor works inside the limits of that order.

    If the agent tries to edit an order or its checks, the tool blocks the edit before it happens.

  4. Step 4

    Automatic checks run. Nobody grades their own work.

    The checks were written by the director, not by the agent; a high-risk order runs them twice.

  5. Step 5

    Results are saved as files you can open.

    The report keeps the raw output of every check, next to the order it belongs to.

  6. Step 6

    You close it, or you send it back with a note.

    You type CLOSE for work that passed, or comment on a document; your note reaches the agent.

Tamper-evident log.Every step is written to a chained record. If anyone edits the past, the chain breaks and the tool tells you.

  • Interrupted? Pick up where it stopped; the tool shows what was left open.

  • Too risky? Higher-risk orders need your typed confirmation.

  • Lost a laptop? The project rebuilds from the repository in about an hour.

The loop at a glance · who does what
The loop flow Order, admit, build, verify, deliver, sign, and a dashed return from sign to order for continuous improvement. 1 · Orderyou define it 2 · Admitaos admit 3 · BuildClaude Code 4 · Verifypass or not? 5 · Deliverevidence + summary 6 · Signyou type CLOSE continuous improvement: what was learned comes back as an addendum
  • Person (decides and signs)
  • Automatic (aos)
  • Gate (pass / no pass)
  • Deliverable
  • Continuous improvement

Point at or tap a step to see what happens and who acts.

  1. Order — you define what you want; the director writes it down. Who acts: you.
  2. Admit — aos admit records the order and puts it in the queue. Who acts: the tool.
  3. Build — the coding agent works inside the order's limits. Who acts: the agent.
  4. Verify — the checks run; the work passes or goes back. Who acts: the tool, as a gate.
  5. Deliver — evidence and a summary are saved for you. Result: files you can open.
  6. Sign — you close it, or send it back with a note. Who acts: you.

03 · What you see

One screen to decide. Plain words.

$ aos sign
1 document(s) waiting for your review.
──────────────────────────────
Document: Hosting options for the new app (order ORD-0018)
  in short: one page, version 2

approve · comment · reject · open
> comment
  Your comment (what should change): the cost does not include the domain.
  Comment recorded: the agent will see it.

Decision brief · one page

Where should the app live?

Pick a home for the first customers. Each option shows its monthly cost and who keeps the keys.

Illustrative: no costs are shown on this page.
OptionMonthly costWho runs it
Managed platform ✓in the brief, with its dateProvider
Your own serverin the brief, with its dateYou

We need from you: choose one option.

  • Approve
  • Comment
  • Reject
Orders panel · Example
OrderGoalStateVerificationSignature
ORD-0001Project structureclosedall checks passedsigned by you
ORD-0002Home screendeliveredall checks passedwaiting for you
ORD-0003Contact pagerunning——
ORD-0004Sign-up flowblockedneeds your decision—
  1. event
  2. event
  3. event
  4. event
chain intact ✓

Illustrative screens · example orders

04 · Get started

Three steps. Then your first hour.

Before you start

About 10 to 15 minutes if you install only these.

  • Git, the program that keeps the project's history. Check: git --version
  • Node.js LTS, a free program the Loop uses internally, installed once. On nodejs.org, on Windows choose the “Windows Installer (.msi)” button and accept the defaults; on macOS use the macOS installer, and on Linux your system's package or the prebuilt download. Check: node --version
  • Claude Code, signed in.
  • The Claude desktop app, only if you want a chat with a connected folder.
  • An empty project folder.

You do not need Chocolatey, Visual Studio, Python or Docker.

  1. Add the pluginclaude plugin marketplace add AnaluciaAOS/analucia-aos
  2. Install itclaude plugin install analucia@analucia-aos --scope project
  3. Open Claude Code in your project folderNothing to type: the plugin starts by itself and its first message begins with “Status:”.

Book a 30-minute diagnostic
Book a 30-minute diagnostic