Skip to content
PointSav Digital Systems

Revision as of · 7bb084e0

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

Design System Philosophy

Why the substrate exists

The substrate is a self-hosted, customer-owned design-system engine running at design.pointsav.com and at every SMB customer site that forks it. Its existence is a direct response to four structural gaps in the 2026 design-system landscape:

  1. Established design systems publish only the WHAT. Major design system publications deliver token values and component shapes. None publish the design-decision research — the WHY — in a form an AI agent or a human at a new organisation can read at codegen time.

  2. Enterprise-tier design-system platforms charge enterprise-tier pricing. SaaS platforms targeting design-system management serve the 5,000+ employee market. The 39% of practitioners working at that scale have options; the SMB beneath them has none.

  3. Every editor wants to be the editor. All major design editors build to lock the customer into their platform. The W3C Design Tokens Community Group format is the editor-agnostic common denominator the substrate adopts as canonical.

  4. AI codegen is widening the design-system surface area faster than tooling catches up. Only 23% of design systems are structured for AI consumption (December 2025 industry data). Existing editor-integrated design-system integrations are locked to specific cloud platforms and licensed customers. A self-hosted, editor-agnostic substrate with AI-readable research is intended to occupy a structural position no editor-locked platform can reach.

What the substrate does

The substrate carries five elements per tenant, in a Git-tracked vault the customer owns:

  • tokens/ — DTCG-format design tokens. Primitive layer (PointSav-original color families, type scale, spacing, motion, focus ring — structural patterns aligned with the modern design-system field, hex values and family names PointSav's), semantic layer (interactive-primary, surface-elevated, ...), component layer.
  • components/ — HTML+CSS+ARIA recipe files. Framework-agnostic; the customer's chosen framework consumes the recipe, not the other way around.
  • themes/<brand>/ — per-tenant override layers that re-point semantic references at primitives.
  • research/ — AI-readable design-decision rationale, accessibility justifications, brand-voice rules, anti-patterns.
  • exports/ — derived caches (Figma Variables JSON, Tailwind config, CSS variables, Style Dictionary builds). Recomputable from the canonical four directories above.

The substrate engine (app-privategit-design) reads this vault and serves it as a public showcase, a DTCG bundle, an AI-readable research surface, and a Model Context Protocol (MCP) server. AI agents query the MCP endpoint at codegen time; design tools query /tokens.json for editor synchronisation; humans read the showcase.

Three structural inversions of the Enterprise-tier pattern

  1. Customer ownership replaces platform hosting. The design system lives in the customer's Git repository with the customer's allowed_signers chain. Migration cost falls toward zero — the customer always has the source.
  2. Research as canonical replaces research as marketing. The WHY lives in the same vault as the WHAT, in the same machine-readable tier, served through the same MCP endpoint. AI agents and human designers read the same file.
  3. Editor-agnosticism replaces editor lock-in. DTCG is the common denominator. Any design editor that supports DTCG export produces vault content the substrate accepts.

The McLuhan position

In the AI era of 2026–2030, an SMB's design-system substrate is a medium — its form (machine-readability, editor-agnostic interop, self-hostability, AI-consumable research) shapes how the SMB's brand reaches every customer-facing surface.

The well-structured substrate IS the message the SMB sends to its implementation partners — human or AI. That is the McLuhan position the substrate operationalises.

Anti-patterns the substrate refuses

  • Storybook integration (parallel renderer; substrate owns rendering).
  • Enterprise-tier design-system SaaS dependency.
  • JS-framework-locked components (HTML+CSS+ARIA recipes are the canonical form).
  • Container packaging (per conventions/zero-container-runtime.md).
  • Editor lock-in (single-editor-only features rejected).
  • Marketing vocabulary in research files (per workspace §6).

See also

References

Important Information

Important Information

Corporate structure. PointSav Digital Systems ("PointSav") is a trade name of Woodfine Capital Projects Inc. ("Woodfine"). 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. See TRADEMARK.md in this repository for the full trademark notice.

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 →