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 · 90df496e

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

Design systemIndex

The design-system category covers the PointSav design system as a platform component — its foundational vocabulary, design philosophy, brand surface context, and the foundation-layer token families that the operator-facing surfaces inherit. It addresses the design system as a concept within the platform: why it exists, how it is structured, what brand identity it carries, and where the foundational token vocabulary aligns with field convention. Component implementation guides, accessibility specifications, and the working surface live in the design system repository at design.pointsav.com; this category supplies the architectural framing.

The design system is itself one of the platform's load-bearing substrates — see Design-system substrate for the substrate framing — and inherits the same customer-ownership, machine-readability, and editor-agnostic interoperability disciplines that the rest of the platform applies to its data layers. Every surface the design system renders is designed mobile-first; Inter is the UI and heading typeface, chosen for screen legibility and the absence of corporate ownership.

Start here: Design system philosophy — why the substrate exists, and the three structural inversions of the enterprise-tier pattern that everything else in this category builds on.

Philosophy and primitive vocabulary

The foundational decisions: why the substrate exists, what it preserved from convention, what it replaced.

  • Design system philosophy — Why the substrate exists; three structural inversions of the enterprise-tier pattern; self-hosted, customer-owned, editor-agnostic token publishing.
  • Design system — primitive vocabulary rationale — Vocabulary rationale: numeric colour scales, layered semantic aliasing, productive-versus-expressive type split, and numeric spacing scales aligned with 2018 to 2026 field convention.
  • Design-system substrate — The substrate framing: self-hosted design-system engine storing tokens and components in the customer's own git repository; W3C DTCG token format; machine-readable MCP endpoint.

Token concepts and tooling

Background articles on what tokens are, how they compose into components, how they theme, and how they reach designers, AI agents, and other organizations.

Brand surface

How the brand identity is encoded as colour families and typographic stacks across PointSav and Woodfine product surfaces.

  • Brand-family swatch — Brand colour families assigned to retail and institutional anchor categories in the co-location GIS surface; consistent colour-coded identifiers for map visualisation and tabular data.
  • Brand typography and print standards — The typographic separation between web interface system fonts and institutional print typography; open-licence serif typefaces reserved for PDF generation and formal disclosures.

Wiki surface design

The component vocabulary, typographic system, and dark-mode palette that compose the documentation.pointsav.com reading surface.

  • Wiki component library — Nine reusable interface components that compose a complete wiki article page; Wikipedia layout conventions, current accessibility standards, PointSav token system.
  • Wiki typography system — Inter and Source Serif 4 type stack, heading scale, and spacing tokens for the wiki; broad linguistic coverage for bilingual content.
  • Wiki dark mode — Light and dark colour schemes for the wiki: WCAG-verified palettes and theme persistence via localStorage.

Related foundations

The architectural and substrate articles that frame the design system within the wider platform.

Additional planned articles — design-system tooling for BIM and AEC interface conventions — are not yet written.

Foundation tokens

The four foundation-layer token families: colour, typography, spacing, and motion. Full specifications are maintained in pointsav-design-system and published on the design system's own site — these are external links, not wiki articles.

  • Colour tokens — primitive palette, semantic aliases, and dark-mode pairings in DTCG format.
  • Typography tokens — type scale, font stacks, fluid type variables, and reading rhythm tokens.
  • Spacing tokens — base unit, geometric scale, component gap tokens, and layout margin tokens.
  • Motion tokens — duration scale, easing curves, and reduced-motion variants.

See also

  • Substrate — the design-system substrate framing alongside the other foundational mechanism substrates
  • Patterns — named design patterns that the design system encodes at the interface layer
  • Applications — operator-facing applications that consume the design system through the token and component layers
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 →