Carlos Florêncio
1.7 KiB
1.7 KiB
status, system, specification_version, migration, owners
| status | system | specification_version | migration | owners | |
|---|---|---|---|---|---|
| active | launcher | 1 | in_progress |
|
Launcher system
Purpose
The launcher system starts and supervises Kandev processes for the dev,
start, run, and service entrypoints. It gives operators one startup result,
one reachable access URL, and useful failure evidence.
Ownership
This system owns launch-mode dispatch, managed-process startup and shutdown, port selection, backend readiness probes, startup output, and supervisor handoffs.
Exclusions
- The backend owns HTTP routes and the
/healthresponse. - The common configuration system owns configuration discovery, precedence, parsing, and validation.
- Authentication owns forwarded-header trust after the backend accepts a request.
- Agent runtime launch and ACP probes are not backend startup readiness.
Specification map
Requirements
System design
Migration status
The startup-recovery documents are authoritative for bind-aware readiness and launcher failure output. Configuration discovery and precedence are defined by startup configuration parity. The native launcher migration also incorporates the Go development launcher requirement. No removed legacy path remains authoritative.
Related systems
- Platform specifications: define cross-cutting startup configuration and diagnostic-log behavior.
- Authentication specifications: define trusted-proxy behavior.