Ktema SystemsKtemaContact
KtemaRecordKletosExecutionKrisisJudgmentDeltaOperationTelosTransportKleisAuthorization

Replayable Agentic Computing

Every autonomous act, accountable.

AI agent books shipment. Drone turns back. Insulin pump holds dose. Robot stops line. Later, someone asks why. System answers from record: what was asked, what it did, and what limited it.

We turn intent into verified work, bind the act and the record together, and let the operator ask and prove the decision from the inside. One open format, from a two-dollar chip or a typical applications to a hyperscale data center, and your infrastructure stays as it is.

Contact
Space systemSmart meterVision cameraFactory PLCLaptop and mobileMCU droneROS robotMedical deviceWearableVehicle ECUData centerEdge gateway
One space and format, from chip to orbit. Each agent, service, or machine keeps its own record. A record from one is read at the same coordinate by another, with no translator between them. The record is the trail from the past to this moment, and the longer it runs, the smaller the space of what happens next. Connect through your own infrastructure, or through our mission control.

Stack

Spatiotemporal Record. Accountable Execution. Portable Control. Verifiable Seal.

Ktema Systems is the whole stack, and each part stands on its own: one record, from a service to a two-dollar part, for execution that can be trusted and checked.

  1. Ktema · the record

    The record engine, with no index to maintain

    Intent, act, and outcome in one record, kept beside the database you already run.

  2. Kletos · the execution

    An intent becomes work, and the work becomes a fact

    The operating system for a full-stack agent workflow: the chain from the ask to the act, in one record.

  3. Krisis · the authority

    The rules the work runs inside

    Smart contracts and governance: who moved this agent, with what authority, and on which terms.

  4. Delta · the cockpit

    The cockpit where a run is seen and changed

    Software agents, robots, drones, and the people who run them, orchestrated from inside the run.

  5. Telos · the transport

    A step to another place is an address

    Live state moves between agents, people, and spaces.

  6. Kleis · the seal

    It decides who enters

    The key a holder presents, the seal that makes a copy open nothing, and the proof that the holder was in control.

01/ 06

Scroll

Operations

One space for the work.

Delta is the cockpit, Kletos is the operating system for the agent workflow, and Krisis is the terms the work stays inside.

  1. The run

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

    Survey and thermal drones map the perimeter, a relay holds the link over the strait, and crawlers and boats take the shore. One intent carries every machine, and the operator changes it while the run moves.

    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 workforce runs on one intent

    Servos, conveyors, cameras, maintenance robots, software agents, and the people who run them, in one cell view. An intent is written once, and the cell runs on it.

    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 satellite at 35,786 km to a drone over the site, with the helicopters, the escorts, and the hospital on the same map.

    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.

  4. The seat

    The operator stands inside the run

    On the island, the operator stands in the run: the drones, their record, and the bounds around them, with the intent changed from where the record is read.

  5. The chain

    The ask and the act stay one chain

    A request is stated, claimed, performed, and written as a result, with the link back to the request. One chain across agents, people, machines, and outside systems.

  6. The terms

    The rules are written before the work starts

    A smart contract or a governance rule sets which model may act, at what cost, and on whose authority. The record is checked against it.

  7. The campaign

    A run another team can replay

    A finished run becomes a package that can be handed on and compared against another. The next campaign starts from it.

01/ 07

Scroll

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

Accountability

Inside the intent, on the record.

Accountable execution for an autonomous system: the intent bounds the work, the act stays on the record, and the run replays.

  1. The intent

    The intent is the boundary

    A person states the work and the constraints once. The gate that binds an agent to them sits above the machines, not inside them. A call an agent originates is denied by default.

  2. The chain

    The act and the record are one chain

    What was asked, who claimed it, what was done, and what it produced stay one chain. Nothing is joined from separate logs after the fact.

  3. The replay

    The run replays from the record

    Every act carries an address anyone can recompute. The run replays from the record itself, on any target, years later.

01/ 03

Scroll

Engine

One engine, from a data center to the smallest part.

The range runs from a server to the smallest part a product ships. The engine has validated at this absolute limit.

  1. The Validation

    $2MCU45g1,648B

    A two-dollar chip on a 45-gram airframe

    A $2 module with 8 MB of flash and 512 KB of RAM. The engine executes multi-axis queries and maintains its record within a 1,648-byte footprint.

    The initial boot prepares the volume; all subsequent boots operate within this peak.

    A small flight-controller board with an ESP32-S3 module, its battery, and a USB bridge.

  2. The hard end

    64 KB of SRAM, and no operating system

    On the RISC-V reference part, 256 KB of flash and 64 KB of SRAM, the engine and its storage take 32,812 B of static SRAM and 123,782 B of flash. Its heap peaks at 2,163 B, and no resident index grows with the record count.

  3. The comparison

    What the same question costs elsewhere

    A general database needs an operating system and 100 KB or more of heap. An embedded key-value store keeps one axis and a RAM index. The engine resolves across axes with no resident index and no operating system.

  4. Alongside the database

    Keep the database. Send it fewer questions

    A multi-axis question costs an index per axis. The engine resolves it from the record. Your database keeps transactions.

01/ 04

Scroll

Cases

One record, every agent.

A pump, a robot, a drone, a vehicle, a workflow, a software agent. The same record holds what was asked, what was done, and what bounded it.

  1. Pump03:14

    The dose was held.

    The questionHow did the dose and the response move together over the last 24 hours, and was the alarm justified?

    What the record must holdThree weeks of readings on the pump itself, the earlier occlusion they match, and the entry that held the next dose.

  2. Robot14:22

    The line stopped.

    The questionWhich decision led to the failure, and who authorized it?

    What the record must holdThe ask, who took it, what was produced, and who approved it.

  3. Drone09:41

    The link dropped.

    The questionWhat did the sensors see before it, and was the operator warned?

    What the record must holdThe readings on the airframe, ordered by time, with the last acknowledged command.

  4. Vehicle21:07

    The system intervened.

    The questionWhich sensor and which model agreed before the intervention, and which did not?

    What the record must holdBoth readings, the model's output, and the rule that allowed the action.

  5. Workflow08:12

    The hand-off failed.

    The questionWhich agent claimed the work, which tool did it call, and what did it hand on?

    What the record must holdThe intent, the claim, the tool call, and the record the next agent received.

  6. Software agent11:48

    The agent responded.

    The questionWhich model responded, at what cost, and on whose authority?

    What the record must holdThe model, the price, and the authority, in one record beside the result.

01/ 06

Scroll

Fit

Where the record stands on its own.

The question combines several axes. It has to be settled where the record was made, inside the memory the system has.

  1. Everyday

    The same shape on things people already run

    A service that keeps a year of runs. A bike computer that keeps a season of rides.

    Which deploy cost the latency, or what changed since Monday, settled in the process itself. No account and no round trip.

  2. Critical systems

    Where the record has to survive the audit

    Ten to thirty years in service, and the organization that shipped it is accountable for what it did.

    Defense programs, medical device makers, vehicle programs, and energy operators. The machine outlives the deployment, and the record has to outlive the machine.

    Medical and automotive: the EU AI Act requires logging over the life of a high-risk system. Industrial and energy: the CRA reporting duty has applied since 11 September 2026, with main obligations from 11 December 2027. Defense answers to its own regime.

  3. The boundary

    The line sits above the engine

    The engine holds the record. Everything above the line is yours.

    A record made where the work runs is proved from its own history. Your database, your cloud, and your services stay above it, and the format does not change.

01/ 03

Scroll

Contact

Building a system that has to answer for itself?

Write to us. Bring the system that has to answer for what it did.

Write to us