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 · f25eaab1

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

Cryptographic payload attestation

Correction — rehedged to planned/intended (2026-07-30): this article originally described a live client-side hash-attestation feature in unhedged present tense. No such code exists: confirmed via both a single-crate check (app-mediakit-knowledge's static/app.js and src/ui/layout.rs — no hashing logic anywhere; the real sidebar renders only nav/categories/TOC) and a broader cross-archive sweep for crypto.subtle.digest/SHA-256 (the only match anywhere in the fleet is an unrelated save-integrity hash in app-workplace-proforma's spreadsheet tool, not a wiki attestation feature). Per operator direction, the body below is rewritten to present this as planned/intended design, not current behavior.

Cryptographic payload attestation is a mechanism by which PointSav intends its edge nodes to dynamically prove the integrity of their published text content to any viewer, using client-side SHA-256 hashing so that any auditor could independently verify a disclosure has not been altered in transit. This is a planned feature, not yet implemented.

Cryptographic payload attestation, once implemented, would be the process by which PointSav public-facing edge nodes prove the integrity of their textual content to any viewer without requiring trust in the server delivering the content. The design intent, per the platform's DARP (Direct, Auditable, Reproducible, Plain-text) requirements, is for public-facing edge nodes to dynamically compute and display a SHA-256 hash of their visible language content, so any institutional investor, auditor, or counterparty could independently copy the text, compute the hash locally, and confirm the displayed hash matches. No such mechanism exists in the wiki engine (app-mediakit-knowledge) or anywhere else in the monorepo today. See also cryptographic ledgers and zero-execution routing.

How it is intended to work

The design calls for the native browser crypto.subtle.digest('SHA-256') API to:

  1. Extraction: read the current visible text of the language block (English or Spanish).
  2. Encoding: encode the text into a Uint8Array using UTF-8.
  3. Hashing: process the encoded array through SHA-256.
  4. Display: inject the resulting hash live into a metadata block beside the content it attests.

None of this is implemented today — the wiki engine's static assets carry no hashing logic, and its real sidebar renders only navigation, categories, and the table of contents.

Intended security posture

Once built, the attestation would be zero-execution-server for the hash computation — the server would deliver the JavaScript and content, but the hash would be computed by the browser using only local data. The intended effect: a man-in-the-middle attacker modifying content in transit would produce a detectable hash mismatch, and any viewer with a SHA-256 calculator could independently verify the attestation.

Intended applications

Once implemented, cryptographic payload attestation is intended to apply to:

  • Public regulatory disclosures displayed on PointSav-operated edge nodes.
  • Content wiki articles served at documentation.pointsav.com.
  • Any content surface where a reader needs to confirm they are reading the published version.

Intended limitations

Even once built, the attestation would only prove integrity at the moment of viewing — it would not prove the content was published at a specific time or that it has not been legitimately updated since a prior version. Time-stamped proof of prior content states already exists independently of this planned feature, via the WORM ledger architecture (service-fs) and monthly Rekor anchoring — both real, verified mechanisms.

See also

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 →