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

Presentation-layer routing and client-side script

← All revisions

c33bd730 · PointSav Digital Systems ·

fix(patterns): add dated Correction callouts to 9 of 12 patterns/ articles — deleted collab feature, fabricated deployment example, os-console web-metaphor mismatch, stale infobox/navbox claims, GIS UX naming, model-tier misattribution, kernel-hardcoding claim, and a SOC-3-relevant zero-JS claim contradicted by real code; 3 verified clean

View the full record as of this revision →

@@ -16,6 +16,8 @@ editor: pointsav-engineering



**Correction (2026-08-02) — compliance-relevant claim, does not match real code:** the real closest-matching implementation, `service-content/templates/pointsav-monolith.html` (and its sibling `woodfine-brutalist.html`), directly contradicts the "zero client-side JavaScript"/SOC 3 claim below — it contains a live `<script>` block that computes a SHA-256 hash on toggle and fires `navigator.sendBeacon` telemetry on page unload. There is also no root-vs-`/es/`-directory split anywhere in the repo for any presentation surface checked — the real template embeds both language blocks in one file, toggled by a single checkbox, not the structural two-file split this article describes. The CSS-checkbox toggle mechanism itself is real (confirmed in both templates), but "zero execution latency and no client-side script vulnerability" is false as a description of the real deployed page. **Flagged, not resolved** — this claim invokes SOC 3 compliance directly, so it needs correcting or re-scoping rather than left standing.

Platform presentation layers adhere to a zero-execution mandate, eliminating client-side JavaScript for core DOM manipulation, language routing, and file serving. This architectural constraint minimizes the attack surface and supports SOC 3 (Service Organization Control 3) compliance by relying entirely on deterministic files and native CSS state management. The pattern complements the [[machine-based-auth|machine-based authentication]] layer and the [[sovereign-ai-routing|sovereign AI routing]] architecture.

## Key Takeaways
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 →