Plans on ZTD — Zero Trust Dev

vz — macOS backend (lima)

Mon, 01 Jan 0001 00:00:00 +0000

Plan — the `vz` macOS local backend (lima)

This plan delivers vz, ZTD’s fourth backend and its first for macOS operators: a disposable, isolated Linux guest running locally on Apple’s Virtualization.framework, driven by lima. It is the headline item of Phase 3 (roadmap).

It is delivered as a sequence of phases, each executed as one Opus-orchestrated red/green/verify cycle — see the red-green-verify skill. Do not attempt the whole backend in one pass; lock one behavioral contract per phase.

Standalone CLI (install + run anywhere)

Mon, 01 Jan 0001 00:00:00 +0000

Plan — the standalone, installable `ztd` CLI

Turn ztd from “a binary that must run inside a checkout of this repo” into a self-contained CLI you install (Homebrew on macOS, a downloaded binary on Linux) and run from any project directory: brew install ztd → cd my-project → ztd init → ztd up. The binary carries everything it needs; the only config a user ever touches is a single ztd.toml.

Backend cohesion & parity

Mon, 01 Jan 0001 00:00:00 +0000

Plan — backend cohesion & parity

Keep the backends (kvm, proxmox, ec2, vz) sharing one pipeline, branching only where the mechanism genuinely differs — so functionality and testing stay in parity as the set grows. Delivered as red/green/verify phases with an independent review, like the vz backend and standalone CLI plans.

The decision: centralize at the contract, NOT at Terraform

A tempting way to “unify” would be to route vz through Terraform too. Rejected, because it adds branching rather than removing it:

Plans on ZTD — Zero Trust Dev

vz — macOS backend (lima)

Plan — the vz macOS local backend (lima)

Standalone CLI (install + run anywhere)

Plan — the standalone, installable ztd CLI

Backend cohesion & parity

Plan — backend cohesion & parity

The decision: centralize at the contract, NOT at Terraform

Plan — the `vz` macOS local backend (lima)

Plan — the standalone, installable `ztd` CLI