Skip to content

PointSav Documentation

The engineering library for the PointSav platform — operating systems and services for regulated businesses that own their data, their AI, and their record-keeping outright. Where the monorepo holds the code, this wiki holds the reasoning: architecture, services, security, and the governance commitments that bind future development.

PointSav Digital Systems

PPN command protocol

← All revisions

ad062fa7 · PointSav Digital Systems ·

fix(infrastructure): add dated Correction callouts to 9 of 19 infrastructure/ articles, verified against canonical origin/main throughout — fabricated cgroups/virtio_balloon mechanism (3 articles), os-orchestration scaffold, wrong UDP port/packet format/crate names (2 articles), hardware-vs-filesystem WORM enforcement overclaim (compliance-relevant, escalated), telemetry payload overclaim, shared-not-per-provider API key storage; 7 verified clean, 2 already correctly self-corrected

View the full record as of this revision →

@@ -14,6 +14,8 @@ last_edited: 2026-06-23
editor: pointsav-engineering
---

**Correction (2026-08-02, verified against canonical `origin/main`):** several specific claims below don't match the real implementation. (1) UDP port — the real, functioning implementation (`app-network-admin/src/main.rs`, `MESH_LISTEN_PORT`) uses **9206**, not 8090; port 8090 belongs to a separate, more minimal `system-udp` crate that uses JSON payloads, not the binary format described here. This exact port discrepancy was already flagged to Command during Round 4's PPN cluster merge (`command-20260801-ppn-wiki-consolidation-found-2-real-engi`), still unresolved. (2) Packet layout — the real frame (`app-network-admin/src/main.rs`) is `op_code: u16` (2 bytes) + `target_node: u16` (2 bytes) + `timestamp: u32` + 8 reserved zeroed bytes; there is no "operation-specific payload" field, and only PING/ISOLATE/PONG/unknown op codes are defined. (3) Crate names — real crate is `system-udp`, not `service-udp`; the real translate→authorize→broadcast flow is implemented in `app-network-admin`, not `os-network-admin` (which is a 44-line pairing-approval CLI poller with zero mesh/crypto logic). **Flagged, not resolved.**

The PPN Command Protocol is the wire format used by every `os-network-admin` control plane to issue commands to `os-infrastructure` nodes across the PointSav Private Network. It transmits fleet commands as 16-byte binary packets broadcast over UDP port 8090 on the WireGuard mesh — with no central broker, no queue, and no third-party service in the path. Every node in the fleet receives every packet simultaneously; only the addressed node acts.

## Design constraints
Important Information

Corporate structure. PointSav Digital Systems ("PointSav") is currently a trade name of Woodfine Capital Projects Inc. ("Woodfine"), planned to become a wholly-owned Woodfine subsidiary upon incorporation. PointSav does not itself offer, sell, or solicit any security. Any securities offering associated with Woodfine's real-property direct-hold solutions is made exclusively by Woodfine, and only by means of the applicable Private Placement Memorandum.

No investment advice. This wiki's content is provided for engineering, operational, research, and development purposes. Nothing on this wiki constitutes investment advice or a solicitation to invest in any Woodfine partnership or direct-hold solution.

Intellectual property. The PointSav name, trade name, wordmark, and marks, together with all current and future PointSav- and Totebox-branded products, services, and offerings — and the software, source code, documentation, design system, and all related materials — are proprietary to Woodfine and its affiliates, except for components identified as open source. No rights are granted except as expressly set out in a written license or agreement. The full trademark notice appears in the footer of every page on this site.

Open source components. Portions of the platform are made available under permissive open-source licenses identified in the accompanying repository. Use of those components is governed by their respective license terms.

No warranty; informational use. Content on this wiki is provided for general informational purposes only and does not constitute a representation, warranty, or commitment with respect to product functionality, availability, pricing, or roadmap. Some articles describe planned or intended features, capabilities, and milestones — language such as "planned," "intended," "targeted," "may," and "expected" marks this forward-looking content, which is subject to change and does not constitute a commitment regarding future performance.

Confidentiality. Where an article describes an operational or deployment detail that is not intended for public disclosure, that article is not published on this wiki. Content here is general-purpose engineering documentation, not customer-specific configuration.

Jurisdiction. Woodfine Capital Projects Inc. is organized in British Columbia, Canada. References to the Sovereign Data Foundation on this wiki describe a planned or intended initiative only, not a current equity holder or active governance body.

Changes to this notice. PointSav may update this notice from time to time; the version posted on this page governs.

Not a filing system. This wiki is not a securities filing system, an electronic disclosure repository, or a substitute for SEDAR+ or any other regulatory filing system. Formal securities filings are made through the applicable regulatory filing system, not through this wiki.

Full disclaimer. This notice supplements, and does not replace, the full Disclaimers article. In the event of any conflict, the full Disclaimers article governs.

Read the full disclaimer →