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

Full-text search

20 revisions

Maintained by PointSav Digital Systems. Each revision is content-addressed by its commit hash.

5 September 2026Track-B documentation wave: services category — mandatory Test-1 self-contradiction fix (service-fs-data-lake), Test-3 split, structural + mechanical frontmatter fixes across 17 articles89c36c1a
22 August 2026editorial(services): rewrite service-search as designed-not-built (Track-B) — confirmed the directory holds only a README, no Cargo.toml/src, same finding already flagged in reference/glossary-documentation.md; reframed around the recorded design intent without asserting current operation, dropped the Configuration table (nothing to configure); register-clean EN+ES, no repo-path citations as evidence91fcbc8b
6 August 2026fix(index-group): backfill index_group across 11 categories migrated to Index Topic (330 files)9b9339a2
2 August 2026fix(services): add dated Correction callouts to 5 services/ articles from batch 2 — fabricated service-wallet (no folder at all), wrong Anchor-Claim-Socket vs real Anchor-Claim-Source model, plus 3 repeat findings (service-places-filtering, service-pointsav-link, service-search all confirmed nonexistent/unbuilt)2684032a
2 August 2026fix(frontmatter): short_description band-fit to house style (120-180 chars) — services/6407fbe3
30 June 2026fix(frontmatter): correct references: YAML indentation across 72 documentation articles309234de
14 June 2026feat(media-knowledge-documentation): add content_type field to all TOPIC + GUIDE filescebee408
29 May 2026enrich wikilinks: documentation services body (EN+ES) batch 25b143601
17 May 2026editorial: Phase A2+A3 — title normalisation (169 files) + wikilink backslash fix (20 files)642749d1
15 May 2026docs(2g): corpus-wide Doctrine claim vocabulary removal (227 files)3bec4800
15 May 2026docs(2g): corpus-wide mechanical quality passfcaf140a
15 May 2026docs(services): add external references to service-search (2 files, bilingual pair)5ed80078
12 May 2026merge: integrate origin/main (taxonomy ratification + category-balance + schema-scrub commits) before project-knowledge Stage 6 promotef0831a90
8 May 2026Step 5 priority 4b — services batch 1: 6 EN+ES pairs register-corrected2b73e9ce
7 May 2026wikipedia-parity: remove inline copyright, trademark, and Provenance blocks from article bodiesf6245a8f
6 May 2026content-wiki-documentation: body H1 batch remediation (106 files)90b1bc7a
6 May 2026Phase E: bcsc_class + status sweep — services/, systems/, infrastructure/, reference/, design-system/3a0c2765
3 May 2026IP footer sweep — re-apply five-mark trademarks workspace-wide36eaf5c9
3 May 2026Diffuse Leapfrog 2030 Doctrine and Glossary formatting11bbf5a2
3 May 2026PL.7: Batch normalization — remove legacy topic- prefix from all files and links3f656f75

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 →