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 · 9b9339a2

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

Retail co-location tier methodology

A retail co-location cluster earns a tier by passing a fixed set of gates, not by accumulating points toward a score. The [[location-intelligence-platform|Location Intelligence]] platform assigns every cluster one of four tiers — Regional, District, Local, or Fringe — by testing composition, catchment population rank, civic support, and overlap with stronger neighbors against country-specific thresholds. A cluster either clears every gate for a tier or it does not; there is no partial credit and no composite number a customer would need to interpret.

Why gates instead of a score

An earlier version of this methodology combined proximity distances into a single continuous score. That approach was retired: a composite number invites the reading that the platform is forecasting financial outcomes, when what it actually measures is spatial proximity and brand diversity. The gate-based system makes that boundary explicit in the mechanism itself — the tier is a classification, not a projection of revenue, foot traffic, market share, or a recommendation to acquire, develop, or lease any site.

Tier definitions

Tier Name What it represents
1 Regional A major trade-area anchor — top decile nationally by primary catchment population
2 District A significant multi-format node — top quartile nationally by primary catchment
3 Local A hardware or wholesale hub with civic support
4 Fringe Any cluster that does not clear a Tier 1–3 gate

Tier names follow the shopping-center industry's own Regional → District → Local hierarchy, so the labels mean the same thing here that they mean in a leasing broker's vocabulary.

What a cluster must clear

Every tier requires all of its gates to pass — composition, catchment rank, civic support, and non-overlap:

  • Composition — which categories of capital-intensive anchor must co-occur. Regional requires a warehouse-club or lifestyle anchor alongside a hypermarket; District requires a hypermarket alongside hardware or warehouse; Local requires a hardware or warehouse anchor on its own.
  • Catchment population rank — each cluster's primary catchment population is ranked against every other cluster within its own country, not globally, so a Tier 1 cluster in a smaller market is compared to its own market's distribution rather than penalized for that market's overall size. Regional requires the top 10% nationally; District the top 25%; Local the top 50%.
  • Civic support — a minimum count of regionally or locally classified hospitals within the cluster's outer catchment ring. Regional requires a regional-grade hospital; District accepts a regional or district hospital; Local accepts any classified hospital.
  • Non-overlap — a cluster that sits mostly inside a stronger neighboring cluster's own catchment does not additionally qualify at a lower tier for the same geography. This is measured as the overlap between the two clusters' catchment areas; Regional clusters must be almost entirely non-overlapping with any stronger peer, District clusters allow more overlap.

Threshold precision is intentionally coarse — the goal is separating nationally significant clusters from local ones, not producing a precise numeric ranking. Threshold refinement is an active area of ongoing work.

What is deliberately excluded

Neighborhood grocery formats (operating in the thousands of small-footprint locations per country) are not ingested as anchors. Their density would produce a large number of low-value clusters below any threshold useful for site selection — a deliberate scope decision, not a data-coverage gap.

Relationship to the platform

The tier assignment is what the map interface renders directly — the Conclusion-First design shows a cluster's tier, not the gate values behind it, so a user comparing markets sees the conclusion first and drills into the underlying anchors only when a cluster has earned that attention. GIS orchestration application computes tier assignment from the cleansed cluster data; the result renders through [[location-intelligence-substrate|the platform's rendering stack]] as the tiered map layer.

Forward-looking information

Statements regarding threshold refinement and future methodology changes are intended targets subject to change. Actual timelines depend on operator review, data coverage, and development velocity. [ni-51-102] [osc-sn-51-721]

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 →