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

MCP and AI-agent-consumable design systems

← All revisions

6aede942 · PointSav Digital Systems ·

editorial(design-system): de-narrate mcp-ai-agent-consumable-design-systems' retraction note (Track-B) — confirmed the article's claims still hold against current app-privategit-design source (MCP module, 5 tools incl. the previously-unmentioned list_token_families, AGPL-3.0-or-later license); stated facts directly instead of narrating the prior session's correction-of-a-correction, dropped the internal cross-reference wikilink used as evidence, per register-documentation.yaml; fixed the same 4-vs-5-tool gap in the ES pair, which had never been corrected at all; register-clean EN+ES

View the full record as of this revision →

@@ -82,25 +82,25 @@ the site's pages are rendered from.

## The machine surface, concretely

**Correction retracted, 2026-08-02:** an earlier pass in this session flagged the `/mcp` endpoint and license claims below as fabricated, based on this archive's local `app-privategit-design` checkout, which is stale relative to canonical (`origin/main`). Re-checked directly against `origin/main`: the MCP module is real (`src/mcp/{mod,protocol,tools}.rs`), wired at `POST /mcp` → `crate::mcp::mcp_handler` (`src/routes/mod.rs`), and `src/mcp/tools.rs` implements all 4 named tools (`get_component_recipe`, `list_components`, `get_token`, `search_design_system`) almost verbatim to this article's description — plus a 5th tool, `list_token_families`, not mentioned here. `GET /bundles/:name/download` is also a real route, alongside `GET /elements/:slug/download`. The AGPL-3.0-or-later license claim is also correct — every `app-privategit-*/` directory falls under AGPL per the real, ratified root `LICENSE` ("MULTI-LICENSE NOTICE" v1.1, effective 2026-05-24). This article's claims hold up well against canonical; the earlier correction should not have been applied. See [[app-orchestration-command-branch-model]] for the broader local-checkout-staleness finding this session made.

The design-system server exposes three machine entry points.

- **`POST /mcp`** — the MCP endpoint. It speaks JSON-RPC 2.0 per the
  specification and exposes four tools: `list_components` (every component
  specification and exposes five tools: `list_components` (every component
  the registry knows, filterable by origin), `get_component_recipe` (the
  HTML, CSS, ARIA guidance, consumed tokens, and variants for one named
  component — the same recipe the site renders live previews from),
  `get_token` (resolve a single design token by its CSS custom property name
  or its DTCG path), and `search_design_system` (full-text search across
  components, tokens, and research notes, for an agent that does not yet know
  the exact name of what it needs).
  or its DTCG path), `list_token_families` (enumerate the token groups
  available before drilling into one), and `search_design_system` (full-text
  search across components, tokens, and research notes, for an agent that
  does not yet know the exact name of what it needs).
- **`GET /tokens/search`** — the same token index as a plain HTTP query, for
  tooling that would rather make an ordinary request than speak MCP.
- **`GET /bundles/:name/download`** — versioned file bundles, including the
  full token export in Design Tokens Community Group (DTCG) format. An agent
  or build pipeline that only needs token values can pull this file directly
  and never touch the MCP endpoint at all.
- **`GET /bundles/:name/download`** and **`GET /elements/:slug/download`** —
  versioned file bundles, including the full token export in Design Tokens
  Community Group (DTCG) format. An agent or build pipeline that only needs
  token values can pull a bundle directly and never touch the MCP endpoint
  at all.

The design principle tying the three together is single-sourcing. Token
counts on the documentation pages, live component previews, MCP tool
@@ -136,8 +136,8 @@ text carries CC BY attribution terms.

## Scope and limits

Stated plainly: the endpoint set described above — `/mcp` with its four
tools, `/tokens/search`, and the bundle download route — is implemented in
Stated plainly: the endpoint set described above — `/mcp` with its five
tools, `/tokens/search`, and the bundle download routes — is implemented in
the design-system server's source and is the surface a self-hosted instance
exposes. The v3 public documentation of that surface, including the Agents
page that presents it to human readers, is under operator review at the time
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 →