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

Browser developer workbench

← All revisions

983f6fe3 · PointSav Digital Systems ·

editorial(applications): re-verify app-privategit-workbench (Track-B) — confirmed os-privategit/src/main.rs is an unrelated 31-line license-check gate with no workbench dependency; confirmed real sibling crates are app-privategit-design/-source/-marketplace/-bim, neither app-privategit-design-system nor service-privategit exist; dropped a retracted-license correction note and rewrote the Relationship section per register-documentation.yaml

View the full record as of this revision →

@@ -9,7 +9,7 @@ quality: pre-build
index_group: input-and-developer-surfaces
status: active
bcsc_class: no-disclosure-implication
last_edited: 2026-05-29
last_edited: 2026-08-22
editor: project-editorial
short_description: "Browser-based file editor in os-privategit presenting a three-column file tree, viewer, and editor for working across the cluster archive tree without a terminal."
paired_with: app-privategit-workbench.es.md
@@ -33,15 +33,9 @@ for history and promotion.
## Architecture

The workbench is a single Rust crate (`app-privategit-workbench`,
AGPL-3.0-or-later — **Correction retracted, 2026-08-02**: an earlier pass in this
session flagged this as wrong, based on this archive's local `LICENSE`/`Cargo.toml`
files, which are stale relative to canonical (`origin/main`). The real, ratified
per-directory license policy (root `LICENSE`, "MULTI-LICENSE NOTICE" v1.1, effective
2026-05-24, propagating `factory-release-engineering/mapping/repo-license-map.yaml`)
places every `app-privategit-*/` directory under **AGPL-3.0-or-later** — this
article's original claim was correct. See the `systems/app-orchestration-command-
branch-model.md` correction for the broader local-checkout-staleness finding this
session made.) in the `pointsav-monorepo`. It has two components:
AGPL-3.0-or-later, per the ratified per-directory license policy that places every
`app-privategit-*/` directory under that license) in the `pointsav-monorepo`. It has
two components:

**Write-service (Rust/axum):** An HTTP server that handles file reads
and writes. It binds to a loopback address and is never exposed
@@ -148,13 +142,15 @@ service file update causes silent write failures at the filesystem layer.

## Relationship to os-privategit

**Correction (2026-08-02):** this relationship doesn't match real code. The real `os-privategit/src/main.rs` is a 31-line license-check placeholder with an empty `Cargo.toml` dependency list — it has no dependency on the workbench crate at all. Neither `app-privategit-design-system` nor `service-privategit` exist anywhere in the monorepo (the closest real name is `app-privategit-design`, no "-system" suffix). **Flagged, not resolved.**

`app-privategit-workbench` is included in the [[os-privategit|`os-privategit`]] host
operating system alongside `app-privategit-design-system` and
`service-privategit`. It is the authoring surface for operators who
use the privategit tier — a locally-hosted, network-isolated development
environment for [[totebox-orchestration|Totebox Orchestration]] instances. Access to writable roots is governed by the [[machine-based-auth|machine-based authorization]] model.
`app-privategit-workbench` ships on the [[os-privategit|`os-privategit`]] host image
alongside its other `app-privategit-*` crates — `app-privategit-design`,
`app-privategit-source`, `app-privategit-marketplace`, and `app-privategit-bim`
among them. The host image's own entry point is a small, separate license-check
gate that starts before any of these applications run; it has no dependency on the
workbench or any other bundled crate. The workbench is the authoring surface for
operators who use the privategit tier — a locally-hosted, network-isolated
development environment for [[totebox-orchestration|Totebox Orchestration]]
instances. Access to writable roots is governed by the [[machine-based-auth|machine-based authorization]] model.

The crate is licensed under AGPL-3.0-or-later and intended
for downstream deployment in customer-tier instances of `os-privategit`.
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 →