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

Structural positioning

← All revisions

67d6fdc8 · PointSav Digital Systems ·

fix(reference): add dated Correction callouts to 9 of 23 reference/ articles, verified against canonical origin/main — stale repo-rename references, Do-Not-Use vocabulary, wrong license claim + unbuilt service-search presented as complete, fabricated hardware specifics, sibling-article RAM-figure conflation, wrong LoRA training framework/rank/precision/GPU tier, compliance-relevant deployed-vs-planned overclaim (escalated), retired research category still listed; 14 verified clean

View the full record as of this revision →

@@ -32,7 +32,7 @@ Structural positioning is the approach PointSav uses to describe the architectur

The customer base the platform serves does not buy software based on vendor comparisons. Asset managers, regulated professionals, and fiduciary institutions buy based on defensibility: can the system answer an auditor's questions directly from its own structure, without a vendor attestation letter?

Structural positioning addresses this directly. Every commitment in the table below is either present in the deployed substrate or it is not — no marketing claim intervenes. An independent auditor can verify the append-only property of the ledger, the absence of the delete verb from the code path, or the unidirectional constraint on the [[diode-standard|Diode adapter]], without relying on a vendor's self-reported controls summary. [^2]
Structural positioning addresses this directly. Every commitment in the table below is either present in the deployed substrate or it is not — no marketing claim intervenes. An independent auditor can verify the append-only property of the ledger, the absence of the delete verb from the code path, or the unidirectional constraint on the [[diode-standard|Diode adapter]], without relying on a vendor's self-reported controls summary. [^2] (Correction, 2026-08-02 — compliance-relevant, escalated: this "deployed, not marketing" framing is contradicted by this wiki's own more authoritative sibling article, `governance/compliance-and-continuous-disclosure.md`, which explicitly marks 3 of this table's 8 rows as "Planned"/"intended," not deployed: asset resolution on vendor failure (DARP), machine-readable compliance (OSCAL/SBOM/HBOM), and continuous audit (`service-audit`, which that same sibling article calls "an intended immutable log... intended to run below the OS" — `service-audit` doesn't exist as a crate at all). The append-only ledger row does check out as genuinely current. Flagged, not resolved — needs re-hedging the 3 planned rows to match the sibling article's own correct language.)

Named-competitor comparisons are specifically avoided. The customer segments the platform targets make institutional purchasing decisions that outlast any two-vendor comparison table; the commitments described here hold regardless of what the competitive landscape looks like when the decision is reviewed.
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 →