Domain: Runtime / Lifecycle
Status: Canonical
The Runtime Lifecycle defines how dev.kit initializes, orchestrates engineering tasks, and finalizes repository state. It ensures a high-fidelity environment for resolving drift between intent and reality.
Interface: bin/scripts/install.sh, dev.kit doctor.
- Symlinks the deterministic engine into the user's
$PATH. - Verifies required software, CLI meshes, and authentication state.
- Loads shell completions and environment-aware aliases.
Interface: dev.kit task, workflow.md.
- Filters chaotic user requests through the Normalization Boundary.
- Transforms ambiguous intent into a deterministic execution plan.
- Maps dependencies and resolves repository-bound skills.
Interface: dev.kit skills run.
- Executes bounded steps through the hardened CLI boundary.
- Leverages the Worker Ecosystem for isolated, deterministic runtimes.
- Triggers Fail-Open Path if specialized tools encounter failure.
Interface: dev.kit sync.
- Groups changes into logical, domain-specific commits.
- Captures the resolution logic back into the repository as a new Skill.
- Prunes stale context and ephemeral task state from the workspace.
The Runtime Lifecycle is grounded in canonical UDX infrastructure and patterns:
| Phase | Grounding Resource | Role |
|---|---|---|
| Hydration | udx/worker |
Base container for deterministic environment setup. |
| Execution | udx/reusable-workflows |
Patterns for automated, multi-step logic. |
| Finalization | udx/worker-deployment |
Standard patterns for final environment orchestration. |
The engineering heartbeat is grounded in systematic lifecycle and evolution patterns:
- Tracing Software Evolution: Drawing parallels between the evolution of systems and engineering phases.
- Developing Lifecycles: Essential practices for smooth, predictable project progress.
UDX DevSecOps Team