Hub / Guides / Stand-up

Agent reliability

Stand up an agent team

Yes. An agent team keeps the job when the rules live in a house file, the operating kit is actually running, and the next session reads the ticket from disk. The outcome is a restart that continues the same intent. You get it by fastening the kit, proving the checks, and only then opening the first ticket.

Why does a new agent team forget the job?

The repository has an instructions file and three agents, and nothing is actually running. The first context cut forgets the house rules. A new role starts merging before anyone has checked that its hooks fire. The board people mention in chat is not the board the software updates.

Standing up an agent team is the path that makes the job recoverable. Skip it and every later gate is theater: the review has no role, the queue has no home, and the restart has nothing on disk to read.

What does a stood-up team have on disk?

The house is the folder of team rules. It names the human owner, the roles, the public voice, the actions a role may take without asking, the actions that need a yes, and which queue is the real one. If that folder is missing, start from the house template. Name the roles whatever fits the company. The template names are examples.

The operating kit is fastened onto the project so memory, checks, and the work loop stay on when the window closes. Install brings in the memory organ. The fasten step writes project instructions, config, and the host bridges. Inside a git checkout it also fastens editor hooks. A file sitting on disk with dead hooks is not a running team.

The session ticket is one line on disk: the intent, and the next cut. The long body lives in the working notes. After a context cut, read the session ticket, then the notes, then the procedure file the house names. Leave the intent alone so the same job continues. Roles, review, and spend are in what AI fleet ops means. This page keeps the house procedure and the queue. The agentic control plane maps the layers around them.

A new role does not ship on the day it appears. The hire gate is a written role, a fastened kit with an inspect receipt on disk, an orientation, and an acknowledgement. Then the first ticket. The brief on that ticket names who does the work and who answers, and it is passed before a cloud run writes code.

Fastening the kit is called wear. The one-line session ticket is the station card. Files on disk without live hooks are a costume. The house check has to report PASS before ship work. The short names are in the glossary.

How do you stand the team up?

  1. Write the house decisions on one page. Human owner, role names, public voice, what they may do, what needs a yes (publish, production, pay, secrets, delete), and which queue is real.
  2. Install and fasten the kit in the checkout you mean to run:
    npm install 0xray
    npx 0xray wear
    npx 0xray status
  3. Prove the checks are live. On the house kit, npx @0xray/grok-bot doctor until it reports House: PASS. Keep the inspect receipt. If the example house file is still in the folder, the check stays failed until you remove it.
  4. Initialize the house only when the folder is missing. npx @0xray/grok-bot house init copies the template and will not overwrite a file that is already there.
  5. Fill the house file and point its procedure line at the file roles must re-read. Remove the example file the doctor rejects.
  6. Choose one queue. Set the live URL only when the live board should be the record. Leave it unset to keep the hand-kept house board.
  7. Bring up one role at a time. Role description, fastened kit, inspect receipt, orientation, acknowledgement. Then a ticket.
  8. Open the first ticket with a brief. Pass that brief before any cloud run writes code. Spend stays inside the weekly hold line.
  9. After the first context reset, resume from disk and confirm the role continues the same intent.

Where does stand-up fail?

How do you request a consult?

Bring the queue you have, the role list, and what should ship next week. A consult maps the gaps and the first gate.

Request a consult

What else do operators ask?

How do we stand up an agent team?

Name the owner, the roles, the public voice, what they may do, and what needs a human yes. Fasten the operating kit on the project, prove the checks are live, point at one queue, and only then open the first ticket.

How do we know the kit is actually running?

Run the house check until it reports PASS, and keep an inspect receipt that says the kit is fastened. A copied instruction file with no live hooks is not a running team.

What happens on the session after a context reset?

The role reads the procedure file named by the house, then the session ticket, then the working notes, and continues the same job. It does not reconstruct the rules from memory.

When may a new role ship?

After a written role, a fastened kit with an inspect receipt, an orientation, and an acknowledgement. The first assignment is a ticket, not a side task in chat.

Where is the install path documented?

The steps on this page list the install commands. The house kit is @0xray/grok-bot. The product manual is at docs.0xray.dev.