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

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

Brand-family swatch

The brand-family swatch is a taxonomy-agnostic visual classification component: a color-coded dot paired with a semantic label, so that category membership is legible at a glance without relying on color alone. Family identifiers resolve through a runtime configuration rather than a code change, so each deployment supplies its own family list and colors — the three families shown throughout this article (Department, Hardware, Warehouse Club) are the component's baseline defaults, not a fixed taxonomy. The platform's GIS surface, part of the location intelligence platform, is one reference deployment: it supplies its own real anchor-family taxonomy through this same runtime mechanism to drive the retail co-location tier methodology's tier visualization, rather than using the baseline defaults shown here.

Visual representation

The brand-family swatch standardizes how anchor categories appear across map markers, tabular filters, and detail drawers. A color-coded identifier paired with a semantic label ensures accessible data density. The component decouples presentation from the underlying taxonomy, resolving family identifiers through a runtime JSON configuration — the GIS surface reference deployment supplies its own taxonomy this way, rather than the component shipping one taxonomy for every deployment.

Usage guidelines

Deployment scenarios

  • Map Markers: Functions as the visual foundation for anchor markers, using color-coded dots to signal family affiliation.
  • Data Filtering: Serves as the interactive primitive within filter rows (typically paired with a checkbox).
  • Detail Overlays: Provides high-level categorization within side drawers and header chips.
  • Cluster Analysis: Employs a concentric ring variant to represent family distribution within aggregate map clusters.

Constraints

The component is reserved for taxonomic classification. It must not be used for binary state indicators, transient system feedback, or non-taxonomic tagging, which are serviced by the Tag and Status Indicator components.

Technical specifications

Anatomy and composition

  • Indicator: A 12px (default) or 24px (marker) circular dot using family-specific color tokens.
  • Label: A taxonomy-resolved display name (e.g., "Warehouse Club").
  • Accessibility Layer: An aria-label that combines the dot and label semantics, ensuring the visual indicator is hidden from screen readers to prevent redundant announcements.

Interaction model

The swatch is natively static. Interactivity is inherited from its parent container (e.g., a filter button or map feature). On map surfaces, the component supports a reveal-by-zoom behavior: cluster-centroid rings are intended to render at low zoom levels, transitioning to individual swatches at higher magnifications.

Accessibility and compliance

The component is engineered to meet WCAG 2.2 AA standards:

  • Redundant Signaling: Color is never the sole channel for information; labels provide primary semantic meaning.
  • High-Contrast Support: In Windows High Contrast Mode or forced-colors environments, the dot reverts to system link colors while the label maintains text integrity.
  • Luminance Contrast: Family color tokens are validated for a minimum 3:1 contrast ratio against both light and dark map basemaps.

Design tokens (DTCG)

The dot is inline CSS, not a sized token — .ps-swatch__dot is hardcoded to 10px by default and 24px for the map-marker variant. The component references four shared tokens ({semantic.ink-primary}, {semantic.ink-secondary}, {primitive.space.05}, {primitive.radius.sm}) plus brand-family colors, which are deployment-specific and set at runtime rather than shipped in the primitive token bundle. The three baseline defaults ship as CSS fallbacks for a deployment that hasn't supplied its own taxonomy:

Value Description
#0B5FFF Department — azure blue (baseline default)
#FF6B00 Hardware — construction orange (baseline default)
#00875A Warehouse Club — warehouse green (baseline default)

These are defaults, not a closed set — a deployment extends or replaces the family list through its own runtime taxonomy file rather than by editing the component.

Planned extensions

Future iterations are intended to include:

  • Pattern Infills: Planned support for geometric patterns within the dot to enhance distinguishability for users with advanced color vision deficiencies.
  • Dynamic Pie Charts: Research is underway to transition the cluster-centroid ring into a dynamic donut chart once cluster density crosses a configured threshold.

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 →