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

Registry-driven releases: one source of truth for tokens, components, and counts

← All revisions

1a7443a7 · PointSav Digital Systems ·

editorial(design-system): fix registry-driven-releases' standing 2026-08-02 flag (Track-B) — confirmed against app-privategit-design/src/tokens_gallery.rs's own source comments: the flag's 'served exclusively from primitive.json+pointsav-brand.json, never tokens.full.json' claim was itself backwards — those files are compiled INPUTS to tokens.full.json, which IS the served/compiled export, matching this article's original mechanism claim; only the leaf count was genuinely stale, now described as current-count-not-fixed rather than re-asserting a specific number that will drift again; de-narrated per register-documentation.yaml; same fix applied to the ES pair; register-clean EN+ES

View the full record as of this revision →

@@ -95,18 +95,15 @@ no longer maintained.

Two details make this example useful. First, neither copy actually fed the
site: the tokens design.pointsav.com serves resolve through one pipeline —
the vault's source files compiled into a single resolved export
(`dtcg-vault/exports/tokens.full.json`, 146 leaf tokens) — so the divergence
was invisible in production while remaining a live hazard for any tool that
picked the wrong file. (Correction, 2026-08-02: the pipeline claim is backwards
— the real commit's own message states design.pointsav.com's served tokens
come exclusively from `primitive.json` + `pointsav-brand.json`, never from
either `dtcg-bundle.json` copy nor the vault export named here. The 146-token
count is also stale by this article's own `last_edited` date — the real file
has grown to ~385 leaves since, after two more pillars (`paper`, `writing`)
were folded in. The "107 shared paths, 5 new colors" resolution numbers
earlier in this section are independently confirmed accurate. Flagged, not
resolved.) Second, the resolution was registry-shaped: declare
the vault's source files (`primitive.json`, `pointsav-brand.json`, plus the
`paper` and `writing` pillars) compiled into a single resolved export,
`dtcg-vault/exports/tokens.full.json` — so the divergence was invisible in
production while remaining a live hazard for any tool that picked the wrong
file. That export has grown well past the two-pillar shape this section
first measured; the current published bundle spans four pillars and several
hundred leaves total, and the file itself is the current count, not a
number fixed to this article's writing date. Second, the resolution was
registry-shaped: declare
one copy canonical, fold the five genuinely-new values into it, and replace
the other with a deprecation stub that points at the canonical file. Not a
cleanup of two copies into two better copies — the elimination of the second
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 →