ADR 0005: Profiles, Lanes, And Bootstrap Scope

Status: current Last reviewed: 2026-06-22 Superseded by: none Accepted: 2026-05-21

Context

The repo supports a personal workstation across multiple host contexts. The workflow needs a small supported surface rather than a public compatibility matrix.

Decision

The supported profiles are desktop and headless. The supported lanes are Windows, Ubuntu WSL, CachyOS, and the headless Ubuntu/Linux droplet Codex host lane. macOS remains parked until there is a real machine again. Existing bootstrap remains in the repo as backend capability, while active work stays focused on tracked workstation configuration, validation, and explicit host-lane setup. Vibe Core is retired from this repo and ShellKit is parked.

Consequences

• Do not add minimal or other profiles without a concrete need.
• Do not make macOS first-class without a new decision.
• Droplet renders shared Unix and agent CLI configuration but omits GUI, desktop, WSL bridge, Windows PowerShell, and CachyOS-specific assets.
• Bootstrap scripts and chezmoi rendering remain maintained, but they are not the first rewrite target.
• Changing supported lanes or profiles is a decision gate.

Alternatives considered

• Support every shell, distro, and OS. That expands scope without serving the current machines.
• Restart ShellKit before current pain points justify it. That would revive a parked subsystem without a clear active need.

Follow-up work

• Keep issue labels and validation commands aligned to the supported lanes.
• Document any host-specific validation gaps in issues rather than widening the support matrix.