Getting started with the PointSav platform
docs(category-fit): move app-orchestration-command-* + totebox-archive to correct categories, merge quick-start into getting-started
@@ -14,6 +14,8 @@ last_edited: 2026-07-11 editor: pointsav-engineering paired_with: getting-started.es.md short_description: "An orientation to the PointSav developer platform: what it is, who it is for, where to start, and how the pieces fit together before the first task." aliases: - quick-start cites: [] --- @@ -26,4 +28,18 @@ The PointSav platform is an independently verifiable, operator-controlled softwa - **Authorization model** — [[machine-based-auth|Machine-Based Authorization]] describes pairing-as-permission, the device-identity model used across the platform. - **Data and GIS** — [[app-orchestration-gis|GIS Orchestration Platform]] covers the location intelligence engine. *This article is a stub. Full content is planned for a future session.* ## Prerequisites - Access to a PointSav Private Network (PPN) node via pairing approval. See [[machine-based-auth|Machine-Based Authorization]] for the pairing model. - Familiarity with command-line tooling. The platform has no graphical installer. ## First steps A task-oriented path to a working session, for an engineer opening the platform for the first time: 1. **Verify node access.** Confirm the WireGuard tunnel is up and the fleet controller is reachable. 2. **Review the architecture overview.** Read [[ppn-small-business-compute|PPN Small-Business Compute]] for the three-node stack (fleet controller, per-node agent, tenant proxy). 3. **Create a VM.** Issue a spawn request through the tenant proxy. See the operational guides in the [[guide-catalog|Developer Guide Catalog]]. 4. **Access the console surface.** The OS Console provides a terminal interface for provisioned VMs and platform management. *This article is a stub, merged 2026-08-03 with the former `quick-start` article (same onboarding purpose, overlapping content — see `redirects.yaml` and this file's `aliases:`). Full content is planned for a future session.*