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

OS network admin

← All revisions

20989afa · PointSav Digital Systems ·

editorial(systems): resolve os-network-admin's standing port-discrepancy flag (Track-B) — confirmed against app-network-admin/src/main.rs: real MESH_LISTEN_PORT is 9206 (PPN_MESH_LISTEN_PORT overridable), not 8090; port 8090 belongs to a genuinely separate crate (system-udp) with its own JSON-based broadcast protocol, not a naming inconsistency between two names for the same mechanism; same finding already established this session on infrastructure/ppn-mesh-architecture and ppn-command-protocol, reused here; HTTP command port 8085 and node-join ceremony port 9205 both reconfirmed accurate; register-clean EN+ES

View the full record as of this revision →

@@ -11,7 +11,7 @@ status: active
bcsc_class: public-disclosure-safe
language: en
paired_with: os-network-admin.es.md
last_edited: 2026-07-11
last_edited: 2026-08-22
editor: editorial
---

@@ -58,7 +58,7 @@ A full keyboard-driven TUI — with approve/deny keys (`a`/`d`), QR code display
`app-network-admin` is the F8 Terminal interface that runs on top of `os-network-admin`. It provides two surfaces:

- **HTTP command surface** at port 8085 — accepts plain-language operator intent, routes it through `service-slm` to produce an authorised command, and dispatches it to the mesh
- **UDP mesh broadcast** at port 8090 — sends signed 16-byte binary payloads to PPN peer addresses (Correction, 2026-08-02: the real `app-network-admin` binary this article describes defaults to port 9206 (`main.rs`, `MESH_LISTEN_PORT`), not 8090. Port 8090 does appear elsewhere in the real code — a different crate, `system-udp`, hardcodes 8090 as its own `MESH_PORT` — so this may be a genuine port-naming inconsistency between two real crates rather than a documentation-only error. Flagged, not resolved; needs confirmation of which port `app-network-admin` should use before correcting either side.)
- **UDP mesh broadcast** at port 9206 by default (`PPN_MESH_LISTEN_PORT` overrides it) — sends signed binary payloads to PPN peer addresses. Port 8090 belongs to a separate crate, `system-udp`, which speaks a different, JSON-based broadcast protocol on its own `MESH_PORT` — the two are distinct mechanisms, not two names for the same one.

The `os-` / `app-` split follows the standard Foundation/Application naming convention: `os-network-admin` is the OS substrate; `app-network-admin` is the operator-facing application that runs on it.
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 →