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

Customer-owned graph IP

← All revisions

30d21bd9 · PointSav Digital Systems ·

editorial(substrate): hedge customer-owned-graph-ip export claim to planned (Track-B) — confirmed export_bundle is an unimplemented Phase-3d planning-doc line item, zero code anywhere in the monorepo; rehedged from routine-current-fact to planned/near-term capability per the commercially-consequential nature of the claim; register-clean EN+ES

View the full record as of this revision →

@@ -24,19 +24,9 @@ Every node, edge, mutation, and [[worm-ledger-architecture|audit-ledger entry]] 

Ownership carries four operational properties:

**Export at any time.** The operator may run a single export command to produce a complete bundle: the graph, the audit ledger, the per-tenant adapters, and the seed taxonomy. This is a routine operation, not a legal or contractual event requiring vendor involvement.
**Export at any time.** The design commits to a single export command producing a complete bundle: the graph, the audit ledger, the per-tenant adapters, and the seed taxonomy — a routine operation, not a legal or contractual event requiring vendor involvement. The export command itself is not yet built; it's a planned near-term capability, not an optional one.

**Correction (2026-08-02, verified against canonical `origin/main`):** this
export mechanism does not exist yet. `export_bundle` appears only as an
unimplemented Phase-3d line item in `service-content/ARCHITECTURE.md`'s
planning table — a corpus-wide grep for `export_bundle`/`fn export` returns
zero implementation hits anywhere in the monorepo. This is a real,
commercially consequential customer-trust claim presented as routine current
fact when it is a planned capability. **Flagged, not resolved — this is the
kind of claim that warrants hedging to planned/intended language, not a
line-level fix.**

**No format lock-in.** The export bundle uses open formats: a Cypher dump for the graph, JSONL for the audit ledger, and standard tensor formats for the adapter weights. The bundle is importable into any compatible system.
**No format lock-in.** The export bundle is designed around open formats: a Cypher dump for the graph, JSONL for the audit ledger, and standard tensor formats for the adapter weights, importable into any compatible system.

**No aggregate license.** The platform does not retain rights to use the customer's data to train cross-tenant models without explicit per-tenant consent.

@@ -46,7 +36,7 @@ line-level fix.**

Most enterprise software platforms shape customer data to the vendor's ontology. When a customer attempts to leave, the data must be re-shaped to fit whatever system they are moving to — a migration project that typically requires vendor cooperation and specialist staff.

The platform's approach inverts this. The customer's data is shaped by their own seed taxonomy (see [[seed-taxonomy-as-smb-bootstrap]]). Export is a single-command operation producing an open-format bundle. The customer's access to their data does not depend on the platform's servers remaining operational — a core property of [[customer-hostability]].
The platform's approach inverts this. The customer's data is shaped by their own seed taxonomy (see [[seed-taxonomy-as-smb-bootstrap]]), designed for single-command export to an open-format bundle. The customer's access to their data does not depend on the platform's servers remaining operational — a core property of [[customer-hostability]].

The economic complement is the transaction-fee pricing model (see [[direct-payment-settlement]]): the customer pays a platform fee only when they earn from their data, not a recurring subscription for access to their own records.
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 →