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

Configure a tenant namespace

← All revisions

ae5ea23b · PointSav Digital Systems · 2 August 2026

correct(how-to): flag non-existent /v1/tenants API, real TENANT_IDS config mechanism (configure-tenant-namespace)

View the full record as of this revision →

@@ -7,7 +7,7 @@ category: how-to
content_type: how-to
type: how-to
status: active
last_edited: 2026-06-14
last_edited: 2026-07-18
editor: pointsav-engineering
paired_with: configure-tenant-namespace.es.md
---
@@ -16,6 +16,23 @@ A tenant namespace is the isolated partition within the platform that holds a si

For the service that enforces tenant isolation, see [[service-vm-tenant]]. For the fleet architecture that namespaces span, see [[ppn-small-business-compute]].

**Major correction (2026-07-18):** the API surface this guide describes does not exist in
the live `service-vm-tenant` source. Direct verification of the route table
(`service-vm-tenant/src/main.rs`) finds exactly four routes: `GET /healthz`, `POST /v1/vms`
(create), `GET /v1/vms` (list), `DELETE /v1/vms/:vm_id`, and `GET /v1/status` — **no
`/v1/tenants` endpoint of any kind.** Steps 1 and 2 below (`POST /v1/tenants` to register a
tenant, `POST /v1/tenants/acme-corp/tokens` to issue a root capability token) describe
routes that are not in the service. Tenant registration is not an API call at all in the
live source — it is **config-driven at service startup** via a `TENANT_IDS` environment
variable (the service logs "`TENANT_IDS not set — no tenants registered; all requests will
401`" when it is absent), not a runtime "register a tenant" operation an administrator
performs after the service is already up. Step 3's `GET /v1/vms` isolation check and Step
4's quota-exceeded check are plausible against the real `/v1/vms` route, but have not been
individually re-verified here. **Flagged, not silently rewritten** — this reads as either
an early design that was replaced by simpler env-var-driven tenant provisioning, or a
guide written ahead of the service it describes; needs project-totebox confirmation of the
actual tenant-provisioning mechanism before Steps 1–2 are corrected or removed.

## Prerequisites

- Administrator access to `service-vm-tenant` (the tenant proxy service, port 9221)

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 →