Skip to content
PointSav Digital Systems

PointSav Documentation

PointSav builds operating systems and services for regulated businesses that need to own their data, their AI, and their record-keeping outright. The platform runs on customer hardware, produces continuous-disclosure-grade records by structure, and operates fully without AI for buyers that require an air-gap.

This wiki is the engineering library for that platform, maintained against an internal editorial standard. It documents the architecture, the services, the operating systems, the governance commitments, and the design rationale that binds future development. It is written for institutional readers — auditors, technical due-diligence reviewers, and procurement evaluators — and for the engineers who build on or extend the platform. Where the engineering monorepo holds the code, this wiki holds the reasoning.

Forward-looking statements in this wiki carry planned, intended, or target language per the internal editorial standard.

280 articles in the registry

Browse by area

How It's Built29 articlesBuilding Blocks39 articlesDesign Patterns12 articlesSecurity and Trust13 articlesHow AI Is Used and Contained10 articlesOperating Systems25 articlesPlatform Services28 articlesApplications14 articlesWhere It Runs22 articlesDesign and Brand11 articlesGovernance and Standards22 articlesHow You Run It28 articlesGlossary and Reference23 articlesResearch1 article

How-to guides

All 28 guides →

Step-by-step operational runbooks — how to install, configure, and run the platform.

  • How to add a node to a running fleet

    Adds a node to a running PPN fleet without restarting existing nodes, covering controller health checks, choosing a non-conflicting node ID, and starting its heartbeat agent.

  • How to authenticate binary downloads

    Verifies an Ed25519-signed release from the PointSav distribution endpoint using a licence token, the detached signature, and the pinned publisher key before the binary runs.

  • How to build a co-location map

    Renders tier-coloured co-location cluster markers on a MapLibre GL map by authenticating against the GIS API and fetching the cluster GeoJSON layer.

  • How to configure a tenant namespace

    Configures an isolated tenant namespace: registers the tenant, sets quota limits, issues the root capability token, and verifies isolation and quota enforcement.

  • How to configure the Doorman gateway

    Configures a single-instance Doorman gateway — tier upstream addresses, circuit-breaker thresholds, and verifying tier state through the health endpoint and console F9 dashboard.

  • How to connect to the OSM data pipeline

    Ingesting a new retail or service chain from OpenStreetMap: write the ingest YAML, run the Overpass query, register the chain in the taxonomy, and rebuild the cluster layer.

  • How to deploy a knowledge instance

    Deploys an instance of the app-mediakit-knowledge wiki server from a local content path: build the binary, write knowledge.toml, start the service, and verify it serves pages.

  • How to enroll a PPN node

    Enrolls a machine into a PPN compute fleet by verifying the controller, starting the heartbeat agent, and confirming the node in the fleet inventory and WORM ledger.

Important Information

Important Information

Corporate structure. PointSav Digital Systems ("PointSav") is a trade name of Woodfine Capital Projects Inc. ("Woodfine"). 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. See TRADEMARK.md in this repository for the full trademark notice.

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 →