Carlos Florêncio
2.9 KiB
2.9 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, 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
- 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
System design
- 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
Migration record
Migration remains in progress while legacy source detail is extracted from the canonical requirement and system-design documents above.
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.