In progress. This work is being done now. It is not finished, and is not presented as finished.

Lab V1 Lite Foundation

The lab can now continue through documentation, synthetic data, PowerShell scaffolds and public evidence while Windows VM compute remains deferred.

Overview

Lab V1 Lite is the practical bridge between architecture planning and the future Windows VM build. It keeps ABD Labs producing useful evidence on the current public host without installing hypervisors or exposing management services.

Problem

The original Lab V1 requires Windows Server, Windows 11 and snapshots, but the current public host cannot safely provide nested virtualization. Stopping all work would waste momentum, while forcing VMs onto that host would create fragile infrastructure.

Constraints

  • No Proxmox, KVM/libvirt, Windows VMs or Azure paid resources on the current public host.
  • No public RDP, SMB, LDAP, Kerberos, DNS, WinRM or hypervisor console exposure.
  • Only synthetic data and sanitized outputs may be published.
  • Windows Lab V1 remains planned until compute and private access are approved.

Approach

Document the lightweight-first track, publish the decision publicly, keep improving synthetic datasets and automation scaffolds, and prepare future provisioning runbooks. The portfolio must clearly separate completed evidence from planned Windows implementation.

Key decisions

Keep using the current public host for public evidence only.

The host is already a working public portfolio and documentation/control layer, but not a Windows VM host.

Alternatives considered

  • Stop all lab work until compute is selected.
  • Attempt software-emulated or nested Windows VMs on the public host.

Treat Windows Lab V1 as a later handoff.

AD, domain join, GPO and workstation evidence should be verified on approved compute rather than simulated as complete.

Alternatives considered

  • Publish Windows lab work as if it were already implemented.
  • Move directly to Azure VMs without budget approval.

Use portfolio pages as an evidence ledger.

Public case studies are more credible when they show what exists, what is blocked and what has been verified.

Alternatives considered

  • Keep the planning private until the full lab exists.
  • Publish only a marketing roadmap.

Result so far

Interim evidence track
1

The project can keep shipping honest, reviewable evidence without spending on the wrong host or risking current services.

Learnings

  • A blocked infrastructure dependency does not have to block documentation, automation design or portfolio evidence.
  • Clear public boundaries make planned lab work easier to trust.
  • A good lab roadmap should preserve operational safety even during the learning phase.

Current Verification Boundary

Lab V1 Lite proves the project structure, public portfolio route and planning discipline. It does not claim that Active Directory, Windows Server or Windows 11 workloads are running yet.

The full Windows lab resumes after a compute host, private access method, licensing path, storage quota and snapshot policy are approved.

Working Method: Progress Without Pretending The Lab Exists

Lab V1 Lite follows a staged method designed for a constrained public host:

  1. Measure the boundary first. The host was assessed for virtualization support, capacity and its existing public-service role. The absence of usable nested KVM and the need to protect live services ruled out Windows compute on this VPS.
  2. Record the decision and alternatives. The constraint, rejected options and later compute paths are kept in architecture notes and decision records, so a future host choice has a traceable starting point.
  3. Build only safe, reviewable artefacts. Synthetic datasets, PowerShell scaffolds, diagrams, runbooks and portfolio records can be versioned and reviewed here without creating a tenant, VM, VPN or management endpoint.
  4. Publish evidence with its boundary. Public pages show the work that is real and the work that is still planned. They use sanitized material only; tenant data, credentials, administrative screens and management services remain private.
  5. Use an explicit approval gate. The Windows implementation begins only after compute, private access, licensing, storage and snapshot policy have been selected and approved. Until then, zero deployed VMs is a deliberate result, not a missing claim.
All projects