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

Legal and IP structure

← All revisions

028e1891 · PointSav Digital Systems ·

editorial(governance): fix legal-and-ip-structure license table to the real ratified per-directory scheme (Track-B) — de-narrated the stale 2026-08-02 correction, verified directly against root LICENSE v1.2: os-totebox is FSL not AGPL (os-console/os-workplace are AGPL, contradicting the article's uniform-tier grouping), os-orchestration is a distinct PointSav-ARR proprietary tier not generic Proprietary, confirmed zero Sovereign Addendum concept anywhere in the license text, confirmed service-pointsav-link does not exist as a crate; ES pair had never been corrected at all (still silently presented the stale table as fact) — fixed to match; register-clean EN+ES

View the full record as of this revision →

@@ -12,7 +12,7 @@ status: active
audience: vendor-public
bcsc_class: public-disclosure-safe
language_protocol: PROSE-TOPIC
last_edited: 2026-05-15
last_edited: 2026-08-22
editor: pointsav-engineering
paired_with: legal-and-ip-structure.es.md
cites:
@@ -77,19 +77,20 @@ Canadian regulatory practice distinguishes between roles with fiduciary authorit

Strategic and fiduciary decisions are escalated outside the routine contributor tier; the system administrator is the only identity with cross-org write access to canonical repositories.

## License strategy (intended)
## License strategy

The intended licensing pattern follows an open-core model. All licensing targets are planned and subject to the [[bcsc-disclosure-posture|BCSC continuous-disclosure posture]] [ni-51-102] [osc-sn-51-721]:
Licensing follows an open-core model, ratified and assigned at the directory level (root `LICENSE`, "MULTI-LICENSE NOTICE" v1.2, effective 2026-08-02):

**Correction (2026-08-02):** this table is now stale, not fabricated — it predates (last-edited 2026-05-15) the real licensing policy that was ratified and propagated repo-wide on 2026-05-24 (root `LICENSE`, "MULTI-LICENSE NOTICE" v1.1). The "planned" outcome landed differently than predicted: `os-totebox`, `os-console`, and `os-workplace` are already **AGPL-3.0-or-later**, not "Apache 2.0 + Sovereign Addendum" — there is no separate "Sovereign Addendum" concept anywhere in the real license text. `os-orchestration`'s real license (per its own `Cargo.toml` on canonical) is `FSL-1.1-ALv2`, inherited from its `os-interface` rename-predecessor, not a standalone "Proprietary" tier. `service-pointsav-link` is confirmed absent from the codebase — checked on canonical too, not just this archive's local checkout. **Flagged, not resolved** — needs updating to the real, already-ratified per-directory scheme rather than a still-future "planned" framing.
| Tier | Coverage | Represents |
|---|---|---|
| AGPL-3.0-or-later | The platform default — `os-console`, `os-workplace`, all `service-*`/`system-*`/`tool-*` (except `tool-wallet`), most `moonshot-*` directories, `app-console-*`, `app-workplace-*`, and workspace tooling | The open core |
| FSL-1.1-ALv2 | `os-totebox`, `os-infrastructure`, `os-privategit`, `os-mediakit`, `os-network-admin`, their `app-*` extensions, and 5 named `moonshot-*` overrides | A source-available tier that converts to Apache-2.0 on a future date |
| Apache-2.0 | `tool-wallet` only | A deliberate override — no revenue role, seeds the open-source binary shelf |
| PointSav-ARR (proprietary) | `os-orchestration` (the `os-interface` rename target) and `app-orchestration-*` | The commercial moat — not distributed under either open tier |

| Component | Planned licence |
|---|---|
| `os-totebox`, `os-console`, `os-workplace` (open core) | Apache 2.0 + Sovereign Addendum (planned) |
| `os-orchestration` (commercial aggregator) | Proprietary (planned) |
| `service-pointsav-link` (the [[diode-standard|Diode]] adapter) | Proprietary, sold as an enterprise add-on (planned) |
`os-totebox` is FSL-licensed; `os-console` and `os-workplace` are AGPL — the three components carry two different licenses, not one uniform "open core" tier. No "Sovereign Addendum" license extension exists anywhere in the real license text — the running-instance-portability property described below is a design goal, not a distinct license grant. `service-pointsav-link`, the [[diode-standard|Diode]] enforcement adapter, does not exist as a crate in the codebase, so it carries no license assignment.

The Sovereign Addendum is the planned licence extension intended to guarantee that the running instance — not just the source code — remains the user's property and is freely transferable between hardware substrates. The pattern follows the open-core model: open core attracts adoption; proprietary services produce revenue.
The pattern follows the open-core model: the AGPL/FSL tiers attract adoption; the PointSav-ARR tier produces revenue.

## Patent strategy (intended)
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 →