Infrastructure
← All revisions
content(infrastructure): PPN cluster consolidation — merged the one genuine duplicate (pointsav-private-network.md into ppn-mesh-architecture.md; confirmed same subject/structure, plus fixed 2 real factual defects: wrong address range 10.50.0.0/24 vs the real 10.8.0.0/24, and a nonexistent route-network-admin name vs the real os-network-admin). The other 9 of 11 flagged articles confirmed legitimately complementary, not merged — audit's 'over-covered, fragmented' framing overstated the problem. Trimmed a duplicated architecture intro in ppn-tenant-vm-isolation.md and added a missing cross-link in sovereign-mesh.md, both per the verified draft plan. Updated infrastructure/_index.md MOC + redirects.yaml + aliases for wikilink resolution.
@@ -41,7 +41,7 @@ How a deployment is provisioned, updated, and maintained across on-premises and How fleet nodes communicate and how observability signals are collected without centralising identifiable data. - [[sovereign-mesh]] — The WireGuard-based peer-to-peer mesh that connects PointSav fleet nodes without a central routing authority. - [[pointsav-private-network]] — The private WireGuard mesh that connects Woodfine's fleet nodes, providing encrypted transport without granting application-layer access to the services on those nodes. - [[ppn-mesh-architecture]] — The private WireGuard mesh that connects Woodfine's fleet nodes, providing encrypted transport without granting application-layer access to the services on those nodes. - [[ppn-command-protocol]] — The command protocol used over the private mesh: compact binary packets carried inside WireGuard tunnels. - [[sovereign-telemetry]] — Zero-state telemetry: the V4 Intent Beacon collects behavioural and hardware signals from edge clients without cookies, session identifiers, or third-party analytics. - [[telemetry-architecture]] — End-to-end telemetry pipeline: collection at production edge nodes, encrypted transport, locally controlled processing, no third-party cloud dependencies.