# Fleet operations

https://demo.ktema.systems/delta/

Browser Host Kletos Delta

Every step, sensor reading and phone reach of a fleet resolves at one address, and the audit finds it offline.

The cockpit for a working fleet: intents and records on the left, the cell in the middle, the ground on the right, the timeline below. Ten scenes, opening on a factory cell in Penang. Read-only, on mock data.

Launch Demo A one-time code is sent by email before the Delta demo opens; the address is used only to send it, and the session lasts 24 hours.

### About this screen

- Delta is the operating layer of the stack: one space where a fleet, a cell, and the people running them are read together.

- It reads the record. It does not keep it: the engine that keeps a record and answers from it is Ktema, and it is not part of this screen.

- Execution and judgment are other layers. Kletos turns an ask into verified work, and Krisis decides what the work may do.

- Transport and authorization are other layers too. Telos moves live state, and Kleis proves who was in control.

- This deployment is read-only. No command reaches a machine, and nothing here writes to a fleet.

- It can run over any backend. On the Ktema stack it is the accountable cockpit, reading the record the engine keeps.

- Every campaign, machine, reading, and operator in this demonstration is synthetic. Delta is planned to be open source.
