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

Cryptographic payload attestation

← All revisions

8d9263d2 · PointSav Digital Systems ·

Correction: security/crypto-attestation.md describes an unbuilt client-side hash feature (EN+ES)

View the full record as of this revision →

@@ -9,12 +9,25 @@ quality: complete
short_description: "Mechanism by which PointSav edge nodes prove published text integrity to any viewer via client-side SHA-256 hashing, independently verifiable by any auditor."
status: active
bcsc_class: public-disclosure-safe
last_edited: 2026-04-30
last_edited: 2026-07-30
editor: pointsav-engineering
cites: []
paired_with: crypto-attestation.es.md
---

**Major correction (2026-07-30):** this article describes a live client-side
attestation feature — a browser `crypto.subtle.digest('SHA-256')` call that hashes the
visible article text and displays it "live into the sidebar's metadata block." No such
code exists in the wiki engine (`app-mediakit-knowledge`): a corpus-wide grep for
`crypto.subtle`/`SHA-256`/`digest`/`attest` across every `.rs` and `.js` file in the
crate returns zero hits. `static/app.js` (358 lines) has no hashing logic at all. The
engine's real sidebar (`src/ui/layout.rs:653`, `fn sidebar(...)`) renders site
navigation, category links, and the table of contents — no metadata block, no hash
display. This is the same unbuilt-feature pattern already found and corrected this
session in `capability-based-security.md`, `diode-standard.md`, and `genesis-protocol.md`.
**Flagged as a whole-article architectural mismatch, not line-edited** — needs
project-totebox confirmation of whether client-side attestation is planned or was
simply never built, before this article is corrected or rewritten.

> Cryptographic payload attestation is the mechanism by which PointSav edge nodes dynamically prove the integrity of their published text content to any viewer, using client-side SHA-256 hashing so that any auditor can independently verify a disclosure has not been altered in transit.
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 →