SYS.03 — SERVICE LINES

AI agent
training.

An agent on your own machine, doing the firm’s work, with your hand on it from wherever you are. Zyrn trains the people who will run it — install, brief, approve, deploy — on the method this site was built with.

INSTALL  /  BRIEF  /  APPROVE  /  DEPLOY  /  REMOTE
00 — YOUR MACHINE 000%
  1. 00Your machineLOCAL · YOURS
  2. 01Installed01 AGENT · ASKS FIRST
  3. 02The briefFROM YOUR PHONE
  4. 03The work— FILES · — CHECKS
  5. 04The gate— APPROVAL · YOURS
  6. 05Handed backPREVIEW · ON YOUR PHONE

Everything runs here, on hardware the firm owns. Nothing of yours leaves it unless you send it. The programme starts by making that true, and then by making it comfortable: the agent lives where the work lives.

What it covers

Six modules. By the end, the person who trained runs the loop without us.

06a

Install

The agent on the firm’s own machine, pointed at the firm’s own work, with permissions set to ask before every change.

06b

The private link

A name only your own devices can reach, so the phone in your pocket is a door to this machine and to nothing else.

06c

The brief

How to write the sentence an agent can act on: what to build, what to keep, where to show it. The standard is in the sentence.

06d

The gate

Which actions the agent may take alone, which it must ask for, and how an approval reaches you wherever you are.

06e

The record

Every session leaves a record on the machine: what was asked, what was changed, what was checked. It stays with you.

06f

Deploy

Shipping from the machine to wherever the firm’s work goes live, with the check that proves it, and a way back.

How this site was made

Counted out of this repository on 2026-10-03. The method the programme teaches is the one that built the page you are reading — Axes, our own agent, running line 01 on ourselves.

  • MACHINE One. Every page here was written by an agent on a single desk machine in Amman, directed by the people who own it.
  • CHECKS 29 verification scripts in the repository — fit, motion, links, taps, the entrance — each one run before a change ships, each one written by the agent that made the change.
  • THE GATE Nothing on this site has gone live without a person saying so. The rule is written down in the repository and the agent reads it before it starts.
  • THE RECORD 36 commits, 27 of them carrying the agent’s signature beside the person who approved it. The site’s own history is the record the programme leaves behind.

How it runs

Three phases, the same three every line runs. Measured at each one.

P.01

Install

One day, at your desk. The agent on your machine, the private link to your phone, and the permissions written down. You leave with the loop working once.

P.02

Run

Two to four weeks, on your own backlog, with us a message away. Briefs, gates, deployments — yours, reviewed with you at the end of each week.

P.03

Hand over

The last session is run by you with us watching. The record, the permissions and the link are yours; the only thing that leaves is us.

What changes

Signals the programme watches, and the direction they are expected to move.

  • WHO CAN RUN IT From nobody to the people who own the work. The agent is a colleague with a desk, not a vendor with a login.
  • WHERE THE WORK IS On your machine, under your name. Nothing leaves it unless you send it, and what you send you can read.
  • WHAT GETS DECIDED By you, at the gate, from wherever you are. The agent proposes; a person disposes.
  • EXIT There is nothing to cancel. The method is in your hands and the machine was always yours.

Shape the programme

Who is trained, how far the agent may act alone, and where it runs. The loop recomposes around your answers — then send exactly that.

Your machine.
Your hand on it.

The programme closes when the person who was trained runs the loop alone, and we are not in the room.