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

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

How to configure a tenant namespace

A tenant namespace is the isolated partition within the platform that holds a single customer's resources — fleet nodes, sessions, audit records, and capability tokens. Configuring a tenant namespace means registering the tenant with the service layer, defining quota limits, and verifying that isolation is enforced. This guide covers initial namespace configuration for a single tenant.

For the service that enforces tenant isolation, see service-vm-tenant — the PPN VM tenant proxy. For the fleet architecture that namespaces span, see Private Platform Network: pooled compute from hardware you already own.

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)
  • A tenant ID: a stable, lowercase ASCII string that identifies the customer (e.g., acme-corp)
  • Quota values agreed with the tenant: maximum concurrent VMs, storage quota, API request rate

Step 1: Register the tenant

Create the tenant record by posting to the tenant service:

curl -X POST http://127.0.0.1:9221/v1/tenants \
  -H "Authorization: Bearer <admin-token>" \
  -H "Content-Type: application/json" \
  -d '{
    "tenant_id": "acme-corp",
    "display_name": "Acme Corporation",
    "max_vms": 10,
    "storage_quota_gb": 100,
    "api_rate_limit_rpm": 600
  }'

A successful response returns the tenant record with a created_at timestamp. The tenant ID is immutable after creation — choose it carefully. The WORM ledger records the creation event automatically.

Step 2: Issue the tenant's root capability token

After the namespace exists, issue a root capability token for the tenant's first administrator session. This token uses scope service:tenant-admin and is scoped to the new tenant_id:

curl -X POST http://127.0.0.1:9221/v1/tenants/acme-corp/tokens \
  -H "Authorization: Bearer <admin-token>" \
  -H "Content-Type: application/json" \
  -d '{
    "subject_pubkey": "<tenant-admin-pubkey>",
    "scope": "service:tenant-admin",
    "expires_in_seconds": 86400
  }'

Deliver this token to the tenant's designated administrator. They use it to issue sub-tokens and enroll their own devices.

Step 3: Verify namespace isolation

Confirm the tenant namespace is isolated from other tenants by querying the fleet under the new tenant's credentials:

curl -s "http://127.0.0.1:9221/v1/vms" \
  -H "Authorization: Bearer <tenant-admin-token>"

The response must contain only VMs belonging to acme-corp. If VMs from other tenants appear, namespace enforcement has a defect — do not proceed; review the service-vm-tenant configuration.

Step 4: Verify quota enforcement

Submit a request that would exceed the configured quota to confirm enforcement is active. For example, if max_vms is 10, attempt to register an 11th VM. The service must return a 429 Too Many Requests response with a quota-exceeded error body.

Quota enforcement failure is a billing and fairness defect — resolve it before the tenant begins production use.

Step 5: Confirm the WORM ledger entry

The tenant creation event is permanently recorded. Verify the entry exists:

service-fs read --filter tenant-id=acme-corp --event-type TENANT_CREATED --limit 1

The entry confirms when the namespace was created and under which administrator token. This record cannot be altered.

Key takeaways

  • Tenant IDs are immutable after creation — choose descriptive, stable identifiers
  • Every tenant namespace has independent quota limits; configure them before the tenant starts enrolling nodes
  • Namespace isolation must be verified before handing off credentials to the tenant
  • A WORM ledger entry is created for every namespace lifecycle event (creation, quota change, deletion)

See also

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 →