PPN VM resource pool architecture
docs(documentation): fix 147 broken wikilinks -- console-os/os-totebox word-order typos (71 occurrences), path-style syntax errors, stray topic- prefixes, PPN/os-console/service-fs/GIS alias-consolidation retargets (57 occurrences), plus 14 links converted to plain text or proper category links where no wikilink target applies (2 flagged as genuine content gaps: app-mediakit-shell has no article; mount is TOML syntax, not a slug)
@@ -11,7 +11,7 @@ audience: vendor-public bcsc_class: public-disclosure-safe language_protocol: PROSE-TOPIC index_group: compute-and-vm-fabric last_edited: 2026-08-22 last_edited: 2026-08-24 editor: pointsav-engineering paired_with: ppn-vm-resource-pool.es.md short_description: "The PPN VM resource pool is a three-service stack that provisions, places, and accounts for VMs across a heterogeneous WireGuard mesh spanning cloud and physical nodes." @@ -19,7 +19,7 @@ forbidden_terms_cleared: true cites: [] --- The [[pointsav-private-network|PointSav Private Network]] (PPN) VM resource pool is a three-service stack that provisions, places, and accounts for virtual machines across a heterogeneous WireGuard mesh. The pool combines cloud nodes with physical hardware, forming a distributed compute substrate that spans different capability profiles. The [[ppn-mesh-architecture|PointSav Private Network]] (PPN) VM resource pool is a three-service stack that provisions, places, and accounts for virtual machines across a heterogeneous WireGuard mesh. The pool combines cloud nodes with physical hardware, forming a distributed compute substrate that spans different capability profiles. Three services partition the responsibility surface. The [[service-vm-fleet|fleet controller]] maintains a global view of node capacity and handles placement decisions. The host agent runs per-node as the spawn authority, communicating with the hypervisor and holding the local state for each VM. The [[service-vm-tenant|tenant proxy]] sits at the customer boundary, enforcing authentication, tenant namespace isolation, quota limits, and an immutable audit trail.