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

Revision as of · 89c36c1a

Historical revision — this record as it stood on 5 September 2026, not the current version. View the current record →

service-pointsav-link — planned PointSav fleet adapter

service-pointsav-link names a concept, not a shipped package: a hot-pluggable adapter that would connect an os-* node to fleet management, translating authority commands into subject-executable operations. No crate by this name, and no pointsav-protocol package, exists anywhere in the platform's source. The concept appears in internal planning material with a status of "conceptual" — scoped and named, not built.

What the design would do

The described shape, as recorded in planning material: a Subject node ships with the adapter absent by default, so it carries no code capable of initiating contact with an authority. An operator activates it with a single command, which installs the adapter and registers the node with a fleet pairing registry. If the adapter crashes or is removed, the Subject keeps running its own workloads — only the fleet's visibility into it goes dark. This shape, if built, would be one concrete implementation of the Diode Standard: an authority-to-subject channel with no reverse path for commands.

What exists instead

The platform's real one-directional mechanisms are documented on Diode standard, which covers each in detail: a pull-and-wipe egress pair, a pull-based telemetry pipeline, an ingestion component that names its own logic "the ingress diode," and a directional code-promotion pipeline with hard reverse-flow guards. None of these is the adapter described here, and none is a general-purpose fleet-command link — each satisfies the one-directional rule for its own narrow purpose.

Whether this specific adapter is a planned component not yet built, or a design renamed or superseded by one of those other mechanisms, is an open question flagged for the owning engineering group. This article does not guess at an answer.

See also

  • Diode standard — the design rule this adapter would implement, and the real mechanisms that follow it today
  • Machine-based authorization — how two machines authenticate before any connection, real or conceptual, is permitted
  • OS network admin — the authority side this adapter's design would connect to
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 →