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

Applications

← All revisions

a5fa68b7 · PointSav Digital Systems ·

docs(2g): rebuild 6 category _index.md landings — complete MOC rewrites

View the full record as of this revision →

@@ -1,35 +1,40 @@
---
schema: foundry-doc-v1
title: "Applications — Category Landing"
title: "Applications"
slug: _index
category: applications
type: topic
quality: complete
short_description: "User-facing and internal applications built on the PointSav platform substrate — the wiki engine, marketing surface, GIS analytics engine, and the structured-input gate through which external files enter a Totebox."
status: active
bcsc_class: public-disclosure-safe
last_edited: 2026-04-29
last_edited: 2026-05-15
editor: pointsav-engineering
paired_with: _index.es.md
---

## Applications
Applications sit above the three-ring service layer. They consume deterministic data and optional AI output from the rings and present it through a defined interface. An application holds no canonical data — it is a view over the service layer, and can be re-provisioned without data loss by pointing a fresh instance at the immutable data underneath.

This category covers user-facing and internal applications built on the PointSav platform substrate. Applications sit above the three-ring service layer; they consume the deterministic data and optional AI services that the rings produce and present that output to users through a defined interface.
## Knowledge and editorial

Applications in this category include the wiki engine that renders this site, workplace productivity tooling, and the presentation surface for data extracted by the platform's Ring 2 services. Each article describes one application: its purpose, the substrate services it depends on, the audience it serves, and the architectural decisions that shaped it. Articles are written for engineers building or extending an application, and for designers working with the application's interface substrate.
- [[app-mediakit-knowledge]] — The single-binary Rust wiki engine that renders PointSav's engineering documentation; a view over a Markdown tree where the git commits are canonical and every running binary is throwaway derived state.
- [[app-mediakit-marketing]] — Multi-tenant marketing landing pages from a single statically-compiled Rust binary; WordPress.org muscle memory at the operator-facing URL, sovereign infrastructure underneath.

## Articles in this category
## GIS and location intelligence

- [[app-mediakit-knowledge]] — The Rust wiki engine that renders this documentation site; Markdown pipeline, wikilink resolver, full-text search, and browser editor.
- [[app-orchestration-gis]] — The stateless spatial analytics engine for linear-geometry calculations and co-location ranking; a pure function that holds no canonical data and can be re-provisioned by pointing a fresh instance at the data layer.
- [[location-intelligence-platform]] — The full location intelligence platform: app-orchestration-gis (analytics) and pointsav-gis-engine (rendering), with every dataset, algorithm, and rendering decision under customer control.

<!-- ENGINE: this list is editorial in iteration-1; iteration-2+
generates it from category-directory file listing once PL.7
chunked-migration moves articles into category subdirectories. -->
## Input and ingest

## See also
- [[app-console-input]] — The F12 surface in os-console: the structured input gate through which raw external files enter a Totebox before being sealed into the verified ledger.

## Domain applications

- [Wiki home](/)
- [Services](/services/)
- [Architecture](/architecture/)
- [[bim-and-real-property-surfaces]] — How PointSav treats Building Information Modelling as a first-class operational domain, with dedicated design-system tooling and ISO 19650 record-keeping discipline.

## See also

<!-- EDITORIAL NOTE: PL.7 chunked normalization sweep will migrate
 root-prefixed TOPICs into this category subdirectory. Until
 migration lands, the existing root TOPICs render at their current
 URLs (topic-<slug>.md); this landing references them by current slug. -->
- [Services](/services/) — the service layer that applications build on
- [Systems](/systems/) — the operating systems that host applications
- [Architecture](/architecture/) — the three-ring model and the customer-ownership principles
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 →