Intent delivers.
The chain from ask to delivery stays one record.
The work a team owes gets done, and the team keeps the two ends: stating the work and accepting the outcome.
A project used to be the work a team owed. The project performs that work now.
One contract for a person, a model, a machine, and an outside system.
One call
The ask, the work, and the result stay one record
Every team owes work, and every container of it has a local name: a backlog, an ECO list, a work order list, a manifest. The call is how that work moves.
- Stated
- A person writes the work: what is asked, who asks, and what limits it.
- Claimed
- An agent, a machine, or a person takes it, and the claim is written.
- Performed
- The work runs on the machine that took it.
- Deposited
- The result is written with the evidence that the work was done.
A planner, a model, and an outside system ask the same way, and one record answers each of them.
How work arrives
A sentence, a model, an outside system
- A person
- A sentence on the console becomes the work.
- A model
- A model proposes the same work, and it is taken the same way.
- An outside system
- A system the layer does not own calls the same way, and reads each machine as a resource.
A model is optional. The layer runs without one.
The two ends
A person states the work, and a person accepts it
The first end is the ask: a person opens a project, writes a line, and watches it move.
The second end is the acceptance, written where the person and the agent both read it. It runs no work of its own.
Approval is a deployment setting: every action, actions on request, or none. A call that waits for an answer waits for the person who can give it.
The machine holds the middle. The two ends stay with people.
What it drives
Software, signals, hardware, people, outside systems
- Software
- Work inside a service or on a desktop.
- Signals
- Measurement and industrial signalling.
- Hardware
- Robots and automation.
- People
- Work where a person is part of the loop.
- Outside systems
- A system the layer does not own, read and written the same way as the rest.
One contract covers all five, so a deployment does not change shape when another kind of machine or agent joins it.
The scale
One host carries the fleet
A node is small enough that a host carries many, and the fleet still answers as one record.
- A node
- About 19 MB resident, with the editor, the terminals, and git inside that figure.
- A host
- Three nodes and seven projects under one operator.
- A device
- Acts within eighty milliseconds of being asked.
- A turn
- End to end on one host, including a request from a phone.
- A run, moved
- A workspace is sealed on one machine and built again on another, under the same record.
The run starts at the phone that asked, continues on the host that performed it, and is read back as one chain.
Contact
Put a run through the layer
If work moves through agents, machines, and people at once, we should talk.
Bring one queue and the people who work it, and we will show the same work as one chain on the record.