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

Architecture decisions

← All revisions

6fd0a504 · PointSav Digital Systems ·

fix(governance): add dated Correction callouts to 9 of 17 governance/ articles, verified against canonical origin/main throughout — Ring-1/Ring-2 service-input misattribution, reversed unicast/broadcast ADR-16, stale pre-ratification license table, missing favicon, unhedged SOC2 claim inconsistent with sibling article; disproven findings (Rekor anchoring, WORM-ledger-stub, SSH key names, ADR-10 unbuilt gate) correctly not applied

View the full record as of this revision →

@@ -65,7 +65,7 @@ The systemd init system, required on current Debian cloud nodes, is formally cla
All operator console pages are served with cache-disabling headers and versioned fetch parameters. The decision eliminates a failure mode that appears in regulated operational tools: a browser presenting a stale cached state of the console while the underlying data has changed. An operator acting on a cached console view may take an action based on information that no longer reflects the platform's state. The platform prevents this by construction rather than by operator discipline.

**ADR-16 — Peer commands travel as unicast, not broadcast.**
Commands sent to peer nodes in the platform's mesh network travel as individual unicast deliveries — one command per node — rather than as a network broadcast. Native UDP broadcast is incompatible with the WireGuard encrypted mesh the platform uses for inter-node communication. The unicast loop preserves delivery guarantees without requiring a separate broadcast layer.
Commands sent to peer nodes in the platform's mesh network travel as individual unicast deliveries — one command per node — rather than as a network broadcast. Native UDP broadcast is incompatible with the WireGuard encrypted mesh the platform uses for inter-node communication. The unicast loop preserves delivery guarantees without requiring a separate broadcast layer. (Correction, 2026-08-02: this is factually reversed. The real `system-udp/src/main.rs`, verified on canonical `origin/main`, implements a literal `broadcast_intent()` function using `socket.set_broadcast(true)` to a hardcoded broadcast address `10.8.0.255` — a "Zero-Broker UDP Mesh," not a unicast loop. Flagged, not resolved.)

**ADR-18 — The operator console is a heads-up display.**
The operator console is designed as a heads-up display that bridges operators to the platform's derivative data architecture. Each function key maps to a distinct cartridge viewport — a bounded view of one part of the platform's data — rather than to a free-form interface. The design limits the surface area of each operator interaction, which reduces the categories of error an operator can introduce in a single session.
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 →