Skip to content

Limitations

Hostwright 0.0.2-dev is not production ready. The complete v0.0.2 outcome is split across 15 phases and 167 child workstreams. Planned scope is not current support.

  • Explicit Manifest v2 with a restricted fail-closed parser, deterministic legacy migration preview, validation, planning, and capability JSON.
  • Narrow Apple container observation and confirmation-gated create/start/restart/delete paths through the runtime boundary.
  • SQLite schema v7 with desired/observed/event/operation/ownership/health/ restart/recovery records, Hostwright UUIDs, provider binding, fencing, and initial saga fields.
  • Bounded logs, local events/recovery/diagnostics, safe doctor checks, local policy/team profiles, secret references/read-only Keychain evidence, a one-shot Control API v2 subset, and reviewed-local extension handshake.
  • Foreground non-autonomous daemon loop, advisory scheduler/resource models, narrow stack import, and unsigned developer artifact/benchmark evidence.
Missing or partial outcome Phase
Trusted install, secure defaults/state, upgrade/rollback/uninstall 02
Full Apple CLI and Containerization provider conformance 03
Complete manifest, lifecycle, probes, updates, automatic rollback 04
Images, registries, Keychain/provider lifecycle, supply-chain trust 05
Volumes, snapshots, backup/restore, quotas, fencing, reclaim 06
Networks, DNS, ingress, TLS/mTLS, policy, tunnels 07
Autonomous daemon, recovery, GC, complete observability 08
Persistent API, identity/RBAC/admission/audit, WASI/XPC plugins 09
Real scheduler, optimization/pressure, host-native accelerators 10
Multi-Mac consensus, HA, remote operations/storage/discovery 11
Kubernetes CRI/CNI/CSI/Helm through a real pod sandbox 12
Docker/Compose/Podman/Testcontainers/CI/IDE interoperability 13
Native GUI, team/MDM, optional offline-safe cloud control 14
Security/fuzz/soak/conformance/performance/docs/signed GA 15
  • private/undocumented Apple APIs;
  • Intel or old-macOS emulation;
  • cluster mutation without quorum;
  • silent telemetry and automatic upload;
  • unauthenticated public control;
  • destructive garbage collection of unmanaged resources.

Homebrew-core acceptance and direct guest accelerator passthrough are external constraints, not excuses: the vendor tap and authenticated host-native Metal/Core ML/MLX service are required fallbacks.