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

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

Totebox Archives as the asset

A Totebox Archive is designed to be the asset, not a record describing the asset. A person, a corporate entity, and a real property each get their own self-contained archive. It can be merged, split, or handed to a different operator the way a physical file box changes hands — not a row in a database that only exists inside the system that created it. This article covers the design principle; for the storage mechanics underneath it, see Source-of-truth inversion.

What this replaces

Moving data between systems is normally a migration project: export from the old platform, transform the format, import into the new one, reconcile what didn't survive the round trip. The problem is structural, not a tooling gap — the data was designed to live inside one system's schema, so leaving that system means leaving the schema behind too.

A Totebox Archive is designed against that problem from the start. Each archive — a person's, a corporate entity's, a property's — is a self-contained unit that does not depend on any one platform to remain legible. The first deployment wave scopes this to three archive types: Personnel, Corporate, and Real Property, entered directly by operating staff rather than migrated wholesale from legacy records, so the earliest archives are accurate by construction instead of inherited and unverified.

Why it matters to a reader who never opens the codebase

An operator who adopts this pattern is not choosing a vendor with better export tools. They are choosing a data shape that does not have a migration problem to solve later, because the archive was never coupled to the platform that first created it.

A real precedent for this shape

This is not a novel idea. Tim Berners-Lee's Solid project applies the same principle to personal data on the web: an individual's data lives in a pod the individual controls, and applications request permission to read or write it rather than owning a copy inside their own database. A Totebox Archive follows the same logic at the level of an organisation's operating records — the archive is controlled and portable; the application requesting access to it is the visitor, not the owner.

The economic model this shape requires

A platform whose customers depend on data staying inside its own systems has a structural incentive to make leaving expensive. Two structural critiques of that pattern — Yanis Varoufakis's account of platform-owner rent extraction ("technofeudalism") and Shoshana Zuboff's account of behavioural data capture ("surveillance capitalism") — describe the same underlying mechanism: value accrues to whoever controls where the data lives, not to whoever produced it.

Totebox Orchestration is designed to remove that mechanism rather than regulate it. Two of the platform's components — Totebox OS and Console OS — are intended to ship as free and open-source software; the commercial layer sits one level up, in an aggregation component (Interface OS) that operates on top of archives the customer already controls. Giving away the layer that owns the customer's data is the point, not a loss-leader: it is what makes the archive genuinely the customer's to keep, move, or walk away with.

What this is not

It is not a backup feature. A backup is a copy kept in case the original is lost; a Totebox Archive is designed so there is no single original the customer does not already hold.

It is not a data-export feature. Export implies the data's native home is inside the platform and a copy is prepared on request. A Totebox Archive's native home is the archive itself — export has nothing to convert, because the format never changed.

See also

  • Source-of-truth inversion — the storage layering that makes an archive's canonical form independent of any one rendering system
  • Customer hostability — the parallel commitment that the systems operating on an archive run on the customer's own infrastructure
  • Compounding substrate — the broader set of structural properties this pattern contributes to
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 →