The day-0 steps for a Linux Mint laptop of class partner-secure-dev, what each one asks, and what to check afterwards.
dvoid-io/workbench · partner
The day-0 path for a Linux Mint laptop of class partner-secure-dev, in order. What the class
does and why is in README § Secure laptop and the
class file; this page
is only the steps, what each one asks, and what to check afterwards. Rehearsed end to end on the
Linux Mint 22.3 Cinnamon ISO in a KVM VM (2026-10-21) — everything except the two sign-ins and
the disk encryption, which only the real laptop has.
Install Mint 22.x Cinnamon with "Encrypt the new installation" ticked (Installation type →
Advanced features → "Use LVM" + "Encrypt the new Linux Mint installation"). It asks for a
disk passphrase, asked again at every boot. It cannot be added later; dvoid doctor's
posture:luks-root reports it.
Git and GitHub CLI, then sign git in. Both prompt:
Skipping gh auth setup-git makes every private clone (your org's repos, its dotfiles) fail
with "git has no working credential … gh auth login, then gh auth setup-git" — fast, not a
hang — and bootstrap ends with a warning saying gh auth login && gh auth setup-git; run
that, then dvoid update.
dvoid, as in Getting started § Install dvoid (the
Linux tab). Success prints Installed dvoid-linux-x64 at ~/.local/bin/dvoid and the version.
Sign in to your org — dvoid login --org your-org. A browser opens on your org's sign-in;
use your org account.
Preview, then bootstrap:
dvoid bootstrap --plan --class partner-secure-dev --org your-org # writes nothingdvoid bootstrap --class partner-secure-dev --org your-org # your sudo password, once
Signed in, the plan also shows your org's repos, templates and plugin changes. The run takes a
few minutes and ends bootstrap complete (or converged with warnings — read each ⚠).
Signed out, it says so in the dvoid login and org-settings rows; sign in, then dvoid update.
Open a NEW terminal (PATH, the env opt-outs and the starship prompt arrive there), then:
dvoid doctor # every row green — belowdvoid harness # pi onlydvoid claude # refused: "runs only pi: claude is refused here"
If your org names dotfiles, chezmoi managed lists them; dvoid update keeps them current.
Disk encryption — the boot passphrase prompt, and posture:luks-root green. The probe was
checked on Mint's LVM-on-LUKS shape, never on a real root.
Screen lock — leave it idle 5 minutes: it locks, and asks for the password at once. The VM
proved the Cinnamon settings, not a lock.
DNS over TLS on your own networks — home, phone hotspot, office. A captive portal (hotel,
airport) cannot be passed while strict DoT is on: resolvectl dns <iface> <portal-dns> for
that moment, then dvoid update to restore.
Chrome, if you install it — chrome://policy shows MetricsReportingEnabled: false.
(Firefox's about:policies showing DisableTelemetry was proven on the VM.)
Firmware — fwupdmgr get-updates sees the vendor; updates stay manual (fwupdmgr update).
Your org's repos — the plan lists them; after bootstrap each one is in ~/dvoid/repos, or
named in one line as no access (a GitHub grant for your operator to give).
pi on the fleet — dvoid pi answers. A secret repo's workstream refuses every other harness.
The console — dvoid opens it in Ghostty; the browser pane draws (needs a real display).