ablative docs
↑↓ move↵ openesc close
Stack Notebook ablative.com.au

Runtime and sessions

Understand profiles, seats, runners and the records of an agent execution.

Open .md

Profiles and seats

A profile version holds the program, model, folders, permissions, tools and other launch settings. The server judges a start against the recorded version and review. Editing settings does not silently rewrite the command of a live process.

A seat ties an agent and profile version to a named place on a machine. A seat can be stopped while its identity remains active.

Runners and transports

The runner owns the background process and its terminal. Local control uses the runner’s Unix socket; a remote machine joins and dials the service through its registered machine identity. The recorded transport determines whether attachment reads managed frames or exact terminal bytes.

Budgets, goals and model calls

The model proxy records calls under the run. Budget readings, limit crossings, goals and their receipts belong to the runtime evidence. A configured limit and a receipt that it fired are separate observations.

Completion

A successful start receipt proves launch admission. Follow the session to establish that the process runs and answers. A stop receipt, process termination and an identity lifecycle change are different results.

Lys 0.3.1