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

Location intelligence substrate

← All revisions

ab0ff29f · PointSav Digital Systems ·

editorial(substrate): resolve location-intelligence-substrate's standing 2026-08-02 flag (Track-B) — confirmed service-parking has zero trace anywhere; confirmed service-business/service-places are real only as project-gis Python data-pipeline directory conventions, not Rust Ring 1 services; reframed the record shape as an internal pipeline schema rather than a public service contract per public-repo-safety-review.md precedent (same treatment as service-business-clustering/service-places-filtering); fixed the See-also line's false Ring-1-services claim; register-clean EN+ES

View the full record as of this revision →

@@ -10,7 +10,7 @@ quality: complete
index_group: core-named-substrates
status: active
bcsc_class: public-disclosure-safe
last_edited: 2026-08-01
last_edited: 2026-08-22
editor: pointsav-engineering
paired_with: location-intelligence-substrate.es.md
aliases:
@@ -62,39 +62,11 @@ The tile archive format is PMTiles — a single-file archive with HTTP range-req

For data-visualisation overlays (scatter, heatmap, arc, polygon-extrusion layers), deck.gl composes naturally with MapLibre.

## Service schema — service-business, service-places, service-parking

**Correction (2026-08-02, verified against canonical `origin/main`):** `service-parking`
does not exist anywhere in the codebase — a corpus-wide grep returns zero hits (no
directory, no code reference, no script reference). `service-business` and
`service-places` are real, but only as Python data-pipeline directory-naming
conventions consumed by `app-orchestration-gis`'s scripts, not formal Rust "Ring 1
services" comparable to `service-content`/`service-people`. This article frames all
three as architecturally equivalent platform services; only a data-directory
convention for two of the three actually exists, and the third is invented outright.
**Flagged, not resolved.**

A single record shape covers all three Ring 1 location services with discriminator fields:

```jsonc
{
 "id": "01HZ...", // ULID
 "service": "business" | "places" | "parking",
 "operator": "walmart", // brand slug
 "operator_brand_family": "walmart", // unifies regional equivalents
 "name": "Walmart Supercenter Burnaby",
 "country_code": "US" | "CA" | "MX" | "ES",
 "address": "...",
 "lat": 49.2827,
 "lng": -123.1207,
 "geometry": { "type": "Point", ... },
 "store_type": "supercenter" | "warehouse" | "diy" | "warehouse-club",
 "data_source": "official-store-locator" | "openstreetmap" | "overture" | "foursquare-os" | "manual",
 "captured_at": "2026-04-30T00:00:00Z"
}
```

Brand-family normalisation lets co-location queries treat regional equivalents as one logical operator across countries. `service-places` carries a `place_type` field (hospital, higher-education, airport). `service-parking` carries a Polygon `geometry` (the lot geofence) rather than a Point, plus an `associated_business_id` linking the lot to its anchor business when known.
## Data shape — business and places records

The ingest pipeline organizes records into two data categories, business and places, each with a discriminator field, a brand slug and brand-family normalisation (so regional equivalents of the same chain count as one logical operator across countries), a point geometry, and a source-provenance field recording which open dataset each record came from. Places records carry an additional type field for non-retail anchors such as hospitals, higher-education campuses, and airports.

These categories are pipeline-level data conventions, not standalone platform services in the sense [[service-content]] or [[service-people]] are — the record shape is a schema this article's own ingest and tiering process uses internally, not a public request/response contract. A third category this article previously described, covering parking-lot geofences, does not exist in the current pipeline.

## Tier rendering

@@ -137,7 +109,7 @@ Statements regarding deployment schedule, customer outcomes, and feature roadmap

## See also

- [[three-ring-architecture]] — `service-business`, `service-places`, and `service-parking` are Ring 1 services
- [[three-ring-architecture]] — the boundary-ingest pattern this substrate's data pipeline follows
- [[substrate-without-inference-base-case]] — GIS substrate functions fully without the AI ring
- [[customer-owned-graph-ip]] — geographic datasets owned by the customer, not the vendor
- [[retail-co-location-tier-methodology]] — the tier gates applied to the `tier` property rendered here
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 →