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 as substrate protocol

← All revisions

5a01a3a9 · PointSav Digital Systems ·

editorial(substrate): resolve mcp-substrate-protocol's standing 2026-08-02 flag (Track-B) — confirmed vector_search/temporal_query unbuilt (service-content's own architecture notes list keyword classification, not vector search); confirmed the file ledger exposes only ledger.append as an MCP tool, no ledger.query/checkpoint tools (a separate read-only Ledger-Entries resource exists, different primitive); fixed a second, previously-uncaught error — the article claimed tool discovery uses an MCP 'describe mechanism', but the real method is tools/list, per the already-established code-for-machines-first.md finding; register-clean EN

View the full record as of this revision →

@@ -10,7 +10,7 @@ index_group: the-compounding-doorman-and-ai-boundary
short_description: "Every Ring 1 and Ring 2 service exposes a Model Context Protocol server interface as its primary external contract, with the Doorman as the MCP gateway."
status: active
bcsc_class: public-disclosure-safe
last_edited: 2026-05-15
last_edited: 2026-08-22
editor: pointsav-engineering
cites: []
references:
@@ -42,19 +42,9 @@ The Doorman is both MCP Client (calling `service-content` for graph grounding) a

## Tool semantics

Each service exposes a small set of named MCP tools. `service-content` exposes graph query, graph mutation, vector search, and temporal query. The file ledger service exposes ledger append, ledger query, and checkpoint. The extraction service exposes entity extraction and classification. The people service exposes person lookup, upsert, and relationship query.
Each service exposes a small set of named MCP tools. `service-content` exposes graph query and graph mutation; vector search and temporal query are not yet implemented — the service's own architecture notes list keyword classification, not vector search, as the current retrieval mechanism. The file ledger service exposes exactly one MCP tool, `ledger.append`; a separate read-only "Ledger Entries" MCP resource exists for reading history, a different primitive from a query tool, and there is no dedicated checkpoint tool. The extraction service exposes entity extraction and classification. The people service exposes person lookup, upsert, and relationship query.

**Correction (2026-08-02, verified against canonical `origin/main`):** `graph_query`/
`graph_mutate` are real (`service-content/src/http.rs`). `vector_search`/
`temporal_query` are not implemented — `service-content/ARCHITECTURE.md` §2 lists
"no vector search — keyword classification only" as a current gap. `service-fs/src/
mcp.rs::handle_tools_list()` exposes exactly one MCP tool, `ledger.append` — there is
no `ledger.query` or `checkpoint` tool (a read-only "Ledger Entries" MCP *resource*
exists, a different primitive). This article correctly hedges its marketplace-tools
section as "planned Phase 5" elsewhere but presents these equally-unbuilt tool names
in unhedged present tense. **Flagged, not resolved.**

The marketplace service (planned Phase 5) is intended to expose listing creation, listing query, and transaction initiation as MCP tools. Customers extending the platform add new MCP servers that expose their own vertical-specific tools. The [[compounding-doorman|Doorman]] discovers new tools at session start via MCP's describe mechanism; no core code changes are required to accommodate a new extension.
The marketplace service (planned Phase 5) is intended to expose listing creation, listing query, and transaction initiation as MCP tools. Customers extending the platform add new MCP servers that expose their own vertical-specific tools. The [[compounding-doorman|Doorman]] discovers new tools at session start via MCP's `tools/list` method; no core code changes are required to accommodate a new extension.

## The Doorman as MCP gateway
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 →