Ktema SystemsKtemaContact
KtemaRecordKletosExecutionKrisisJudgmentDeltaOperationTelosTransportKleisAuthorization

Single-Space Agentic Operations Platform

Every agent, mobilized in one space.

A cockpit where operators see and command robots, drones, codebases, agents, and the people who run them in one unified space. It can run over any backend; on the Ktema stack, every interaction and campaign is recorded and replayable.

What the machine does is the sum of the intents that enter the loop.

Talk to us

Operations

Three runs, one space.

Delta is the cockpit of a campaign: the machines, the people, and the record of a run, read together. Each case is read from the seat inside the run.

  1. The run

    A fire on an island, answered by the fleet already there

    Delta puts every machine, person, and record of the run in one space. Survey and thermal drones map the perimeter, a relay holds the link over the strait, and crawlers and boats take the shore, each intent claimed by a different machine under the same wind and keep-out bounds. The operator changes the intent from the same record, and the fleet answers the new one without stopping.

    The reference campaign: one situation, one record, and a fleet that answers together.

    Rescue Wing: Island Fire. The intents and records on the left, the cell view of survey, thermal, photo and relay drones with crawlers, boats and rovers in the middle, the island and its shoreline on the right, and the timeline below.

  2. The cell

    A factory cell runs on one intent

    Servos, conveyors, cameras, maintenance robots, and the people who run them, read in one cell. An intent is written once, and every agent under the cell answers from it. The operator sees the whole cell and the record of each agent in the same view.

    The cockpit on a factory cell: the intents and records on the left, the feed and the cell view in the middle with servos, conveyors and maintenance robots, and the timeline along the bottom.

  3. The span

    35,786km

    Land, air, and orbit in one view

    A rescue run reaches from a geostationary satellite at 35,786 km to a drone over the site, with the helicopters, the escorts, and the hospital on the same map. Each element is read where it is, and the operator follows one record from orbit to the shoreline.

    A rescue campaign on the map and in the cell view: satellites at 550, 1,200 and 35,786 km, rescue and medevac aircraft, escorts, the hospital, and the operators on one space.

01/ 03

Scroll

The campaign data in these views is simulated. Delta is planned to be open source.

The seat inside it

The run, read from the inside.

Delta is the entity's own coordinate space: its record and the constraints that bound it, read and acted on from the same place the intent is changed. The operator, the machines, and the auditor read one object.

To the past

The entity's point of view at the moment before an incident, replayed from the record.

To the edge

The entity's own space with the link down.

Across borders

The record a regulator asks for, produced from the machine.

The loop

Intent enters a moving run

A run is not a command. The loop comes first, then one run where intent enters while the work is moving.

  1. The premise

    A run is not a command

    A command asks for an output and waits. An autonomous system keeps running, and a person can enter at any point with a new intent, a limit, or a correction. What the machine does is the sum of those entries.

    The runIntent entersWork is claimedResult is writtenOperator readsOperator
    The operator can enter intent at any point in the run. What the machine does is the sum of those entries.

  2. The run

    The villa evacuation

    An emergency lift on the Monaco coast. The operator calls the lift. The hospital adds a 75-second bound for the scan. Both enter while the work is moving. The run starts when the emergency is declared and ends when treatment begins.

    One run, three entries, one 75-second bound.

    Emergency liftcomplete
    1. Emergency declared8s
    2. Operator calls the lift28s
    3. Robot reaches the patient74s
    4. Scan reaches the hospital80s
    5. Treatment begins176s
    The operator calls the lift at 28s. The hospital's 75-second bound for the scan enters at the start, and the scan reaches it at 80s, three seconds inside the window. Treatment begins at 176s.

01/ 02

Scroll

Campaigns

A run becomes a campaign

A campaign is one run inside a project: a situation, a briefing, the objectives, the constraints, and the record of what happened. The island run above is the reference campaign.

What a campaign holds
The situation, the briefing, the objectives, the constraints, and the record of the run.
What the platform does
Plays the run, reads the objectives at the cursor, and compares two runs on the same record.
What a finished run becomes
A package that can be replayed and handed to another team.

Contact

Bring a run to the platform.

If you run a system where intent changes while the work is moving, we should talk. Write to us.

Write to us