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 ledgers

← All revisions

94ee0405 · PointSav Digital Systems ·

correct(security): flag Noise-Protocol/four-tier-taxonomy vs real system-gateway-mba mechanism (machine-based-auth, EN+ES); flag C2SP tlog-tiles as not-yet-built vs real flat-log implementation, confirm Rekor monthly anchoring is accurate (cryptographic-ledgers, EN-only — ES pair never made this claim)

View the full record as of this revision →

@@ -9,7 +9,7 @@ quality: complete
short_description: "Cryptographic ledgers are the immutable-state storage pattern in the PointSav platform, where any alteration breaks a verifiable hash chain, not just an access-control rule."
status: active
bcsc_class: public-disclosure-safe
last_edited: 2026-04-30
last_edited: 2026-07-28
editor: pointsav-engineering
cites: []
paired_with: cryptographic-ledgers.es.md
@@ -45,8 +45,26 @@ If the hashes match and the inclusion proof verifies, the record is intact. If e

The [[pointsav-overview|PointSav]] cryptographic ledger uses C2SP tlog-tiles format — the same on-disk structure used by Certificate Transparency logs and Sigstore Rekor. Tiles are static, base64-encoded text files containing 256 entries each at the leaf level, with intermediate [[merkle-proofs-as-substrate-primitive|Merkle-level]] tiles above them. This format is human-readable, independently verifiable, and compatible with standard Certificate Transparency tooling.

**Correction (2026-07-28):** the on-disk format is currently a single flat
newline-delimited JSON log file per tenant (`<root>/<moduleId>/log.jsonl`), not a
C2SP tlog-tiles multi-file structure — verified against `service-fs/src/posix_tile.rs`,
whose own doc comments describe "segment-batched tile files (256 entries per sealed
segment)" as "the natural performance upgrade and a follow-up commit," not yet
implemented; the file's `PosixTileLedger` struct holds one `log_path`, not a tile-file
set. The cryptographic properties this article describes — hash-chained entries,
Ed25519-signed checkpoints, inclusion and consistency proofs — are real and implemented
in that same file, just not in the specific tile-file on-disk layout named here. The
Monthly Rekor anchoring claim below, by contrast, **is verified accurate** — see the note
after that paragraph.

Monthly, each tenant's signed checkpoint is submitted to the Sigstore Rekor v2 public transparency log. Once anchored, the checkpoint is public and the tenant cannot retroactively alter any prior record without the tampered state being detectable against the anchored checkpoint.

**Verified accurate (2026-07-28):** confirmed against `service-fs/anchor-emitter` (580
lines, a real Sigstore Rekor v2 `hashedRekordRequestV002` submission client) and its
systemd timer `infrastructure/local-fs-anchoring/local-fs-anchor.timer`, which fires
monthly on the 1st at 02:30 UTC. This part of the article matches the live
implementation; only the tile-format paragraph above needed correcting.

## Applications

The cryptographic ledger applies across all customer-facing data in the platform:
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 →