Research promoted into implementation

Research is not implementation

Earlier investigations remain useful evidence and threat-model input, but they cannot close a v0.0.2 issue. Each area below now has runnable outcomes and strict evidence requirements.

External orchestration

Planned Phase 12 owns a real pod-sandbox VM/guest agent, CRI v1 RuntimeService/ImageService/streams, CNI, CSI, kubelet, Kubernetes/Helm translation, scheduler/devices, and conformance. Phase 13 owns the negotiated Docker Engine API, authenticated context, Compose, Podman, Testcontainers, CI, and IDE matrices.

The earlier protocol research explains why unsupported fields/endpoints must fail explicitly and why Kubernetes pod semantics require a real shared guest boundary.

Multi-Mac platform

Planned Phase 11 owns cluster CA, managed pinned etcd, replicated desired state, node agents, remote execution, fencing, placement, drain, discovery, remote volumes, leader leases, failover, mixed-version upgrades, and disaster recovery. Quorum loss stops mutation.

Secure exposure

Planned Phase 07 owns project networks, DNS, TCP/UDP, dual stack, ports/sockets, guarded host/LAN access, ingress, TLS/mTLS, ingress/egress policy, first-party Hostwright tunnels, and third-party provider SPI.

Local Network permission, PF loss, Private Relay, sleep/wake, network switching, certificate rotation/revocation, asymmetric connectivity, conflicts, and cleanup are test inputs rather than documentation caveats.

Apple silicon accelerators

Planned Phase 10 owns accelerator inventory/reservations and a signed authenticated host-native Metal/Core ML/MLX service. Direct guest GPU/ANE passthrough is added only if Apple provides a supported public API; the host-native service is the required fallback.

Scheduler and optimization

Planned The current advisory model is retained as narrow evidence. Phase 10 implements requests/limits/reservations, hard filters, multi-resource best-fit-decreasing packing, dominant-resource fairness, topology, preemption/disruption budgets, anti-churn hysteresis, explainability, thermal/battery/sleep/pressure policy, and memory reclamation.

Qualification uses one million seeded cases and at least 10,000 exact-oracle comparisons with zero invalid placement, starvation, nondeterminism, or unbounded churn.

How status changes

Status changes only when the linked workstream’s executable behavior and clean unit, integration, live, migration, security, resilience, performance, multi-host, interoperability, accessibility, and cleanup evidence pass as declared. A mock, fixture, document, research result, or blocker never upgrades the support claim.