Henry
c7cc92382b
Co-authored-by: nova28 <17953305+nova28@users.noreply.github.com> Co-authored-by: Carlos Florencio <carlosmflorencio@gmail.com>
4.3 KiB
status, system, specification_version, migration, owners
| status | system | specification_version | migration | owners | |
|---|---|---|---|---|---|
| draft | executors | 1 | in_progress |
|
Executor system
Purpose
The executor system owns the runtime environments that execute agent work, including local, container, and SSH execution boundaries.
Ownership
This system owns executor profiles, environment construction, SSH lifecycle, runtime resource admission, process and port safety, agent process lifetime across a backend restart, and executor-specific failure and recovery contracts.
Exclusions
- Agent identity and provider capabilities belong to the agent system.
- Task ownership of worktrees belongs to the task system.
- Desktop process supervision belongs to the desktop system.
Specification map
Requirements
- Agent survival across a backend restart
- Survived session state and capability gating
- Standalone control-server ownership
- Standalone control-server single driver and unowned lifetime
- Executor-Profile Environment Precedence
- Port collision and backend ownership safety
- SSH Executor
- Remote SSH task-directory reclamation
- Kubernetes worker presets
- Kubernetes startup timing
- Kubernetes retained compute visibility
- SSH Session Transport Liveness
- SSH Host Reachability
System design
- Agent survival across a backend restart Part 1
- Agent survival across a backend restart Part 2
- Agent survival across a backend restart Part 3
- Executor-Profile Environment Precedence System Design Part 1
- Executor-Profile Environment Precedence System Design Part 2
- Executor-Profile Environment Precedence System Design Part 3
- Executor-Profile Environment Precedence System Design Part 4
- Executor-Profile Environment Precedence System Design Part 5
- SSH Executor
- Remote SSH task-directory reclamation
- Kubernetes worker presets
- Kubernetes startup timing
- Kubernetes retained compute visibility
- SSH Session Transport Liveness
- SSH Host Reachability
- SSH Host Reachability Surfaces
Migration record
Migration remains in progress while legacy source detail is extracted from the canonical requirement and system-design documents. Use the catalog command to find current sources.
The Kubernetes executor foundation remains the current lifecycle contract. The three Kubernetes pairs own additive presets, launch diagnostics, and retained-compute visibility. They do not replace the foundation's resource ownership, recovery, or cleanup rules.
Related systems
The compact task indicator contract is extracted into requirements and design, including automatic freshness and desktop/touch disclosure. The foundation retains task-page controls.