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

Favicon matrix and tab identity

← All revisions

9426a185 · PointSav Digital Systems ·

docs(documentation): move security-overview to security/ and favicon-matrix to design-system/ — two category-fit corrections in governance/

View the full record as of this revision →

@@ -0,0 +1,48 @@
---
schema: foundry-doc-v1
title: "Favicon matrix and tab identity"
slug: favicon-matrix
category: design-system
type: topic
content_type: topic
quality: complete
index_group: wiki-surface-design
short_description: "The wiki serves a single static SVG favicon — a navy document-page glyph, linked from a static file, the same mark on every tab regardless of tenant."
status: active
audience: vendor-public
bcsc_class: no-disclosure-implication
language_protocol: PROSE-TOPIC
last_edited: 2026-09-06
editor: pointsav-engineering
paired_with: favicon-matrix.es.md
---

The wiki serves one favicon: a navy (`#1a4480`) document-page glyph on a rounded square, defined as a static SVG file and linked from the page `<head>` with a standard `<link rel="icon">` element. Every tenant's tabs carry the same mark — there is no per-tenant colour or shape variant, and no inline data-URI encoding.

This article describes the mechanism as built.

## Key Takeaways

- The favicon is a static file (`static/favicon.svg`), served over HTTP and referenced by a normal `<link rel="icon">` tag — not an inline SVG data URI.
- `/favicon.ico`, the path browsers request by convention regardless of what `<head>` declares, redirects to the same static SVG file.
- One mark serves every tenant. There is no vendor/customer, square/circle, or steel-blue/Woodfine-blue distinction in the current build.

## The mechanism

`app-mediakit-knowledge`'s page layout links the icon in `<head>`:

```html
<link rel="icon" type="image/svg+xml" href="/static/favicon.svg">
```

The server also registers a `/favicon.ico` route that redirects to the same file, so browsers and crawlers that request that exact path by convention (independent of the `<head>` declaration) still resolve to the real icon rather than a 404.

## The mark

The icon is a single, un-parameterised SVG: a navy (`#1a4480`) rounded-square base with a white document-page glyph. It does not vary by tenant, deployment, or wiki — `documentation.pointsav.com`, `projects.woodfinegroup.com`, and `corporate.woodfinegroup.com` all serve the identical file.

## See also

- [[design-system-substrate]] — the design system substrate that defines the visual language these marks belong to
- [[anti-homogenization-discipline]] — the editorial discipline that preserves distinct brand voices alongside this visual identity
- [[disclosure-substrate]] — the outbound communications architecture served under the customer mark
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 →