What Hostwright is
Hostwright is a Mac-native desired-state container platform for Apple container workloads.
You declare services in a versioned hostwright.yaml manifest. Hostwright validates intent, computes a deterministic plan, persists exact desired/observed/operation identity, and crosses a typed runtime-provider boundary for every runtime action.
What works today
Section titled “What works today”hostwright --versionandhostwright capabilities --jsonexpose build and capability truth.hostwright init,validate, andplanprovide explicit Manifest v2, restricted fail-closed parsing, and deterministic planning.hostwright migrate previewproduces a deterministic non-writing preview for legacy v1/versionless manifests.status, boundedlogs,events,recovery, and local redacteddiagnosticsuse explicit state paths.- Confirmation-gated
applysupports only the currently declared narrow create/start/restart surface. cleanupclassifies first and deletes only exact cleanup-eligible Hostwright-owned non-running containers after token confirmation.hostwrightd --foregroundobserves, plans, checks bounded loopback health, and records events; it is not the autonomous Phase 08 daemon.- SQLite schema v7 establishes UUID identity, provider binding, fencing, saga intent, compensation, and verification records.
- Secret references, local policy/team profiles, a one-shot Control API v2 process, advisory scheduler models, and unsigned developer distribution evidence exist within their documented narrow boundaries.
Everything else is a current limitation with an owner, not a discarded non-goal. The 15-phase v0.0.2 program covers trusted install, both Apple providers, complete lifecycle, images/registries/secrets, storage, networking, autonomous recovery, security/extensions, scheduling/accelerators, multi-Mac HA, Kubernetes, Docker ecosystem, GUI/team/cloud, and GA qualification.
Locked contracts
Section titled “Locked contracts”| Contract | Version |
|---|---|
| Manifest | 2 |
| Control API | 2 |
| Runtime Provider API | 2 |
| Plugin ABI | 1 |
| State schema | 7 |
How these docs are organized
Section titled “How these docs are organized”| Section | Answers |
|---|---|
| Getting started | Honest source setup and the currently runnable safe loop. |
| Concepts | Desired state, providers, reconciliation, identity/state, policy, safety, and secrets. |
| Tasks | Walkthroughs labeled non-mutating, state-writing, or runtime-mutating. |
| Reference | Exact CLI, manifest, compatibility, limitations, error, policy, and evidence contracts. |
| Operations | Security, team workflow, daemon, events, diagnostics, and recovery. |
| Release | The v0.0.2 RC/GA process plus immutable historical notes. |
| Roadmap | All 15 phases and 167 workstreams; planned behavior is never current support. |
Where to start
Section titled “Where to start”- Read Why Hostwright and Desired state.
- Read Limits, fallbacks, and safety boundaries plus the exhaustive Limitations.
- Follow Install from source and the Quick start.
- Inspect the v0.0.2 roadmap before interpreting research or historical pages as current scope.
