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

MediaKit knowledge application

← All revisions

13cf7aae · PointSav Digital Systems ·

fix(applications): add dated Correction callouts to 13 of 14 applications/ articles — worst defect rate of any category swept (fabricated kill-switch UI, WordPress admin panel, C2PA badges, collab feature x3, stale Phase 4/category-count claims, wrong catchment radius, misattributed crates); 1 verified clean

View the full record as of this revision →

@@ -46,6 +46,8 @@ references:
    url: "https://en.wikipedia.org/wiki/Wikipedia:Manual_of_Style/Layout"
---

**Correction (2026-08-02):** three claims below don't match the real crate. (1) **Stale by weeks, not absent**: the article frames Phase 4 (history/blame/diff, MCP server, git smart-HTTP remote) as "planned... awaiting operator clearance" — but git history shows these shipped *before* this article's own `last_edited: 2026-05-25` date (history/blame 2026-05-03, MCP server 2026-05-12), and live routes confirm all of them (`/history/{*slug}`, `/blame/{*slug}`, `/diff/{*slug}`, `POST /mcp`, `git-upload-pack`) are deployed today. (2) **Fabricated**: the "Real-time collaborative editing" section (Yjs, `tokio::sync::broadcast` relay, `cm-collab.bundle.js`) and "squiggle linting" have zero code footprint anywhere in the crate — same class of finding as `patterns/collab-via-passthrough-relay.md`. (3) **Wrong location and content**: the "8 inventions" list is attributed to an `INVENTIONS.md` "at the crate root" — the real file is at `docs/INVENTIONS.md` and lists 5 differently-named inventions (Substrate-enforced AI grounding, Content-addressed federated AI adapters, etc.), `status: thinking`, not the 8 named here. **Flagged, not resolved.**

`app-mediakit-knowledge` is the single-binary Rust wiki engine that serves PointSav's engineering documentation at `https://documentation.pointsav.com`. The engine combines an `axum` HTTP server, a `comrak` CommonMark renderer[^1][^2] with platform-specific extensions for wikilinks, footnotes, table of contents, and section anchors, a `tantivy` full-text search backend[^3], and a `maud` templating layer with four article templates. The engine reads markdown files from a content directory the operator names at startup, renders them on demand into HTML, and returns them with caching headers tuned for a documentation audience.

The engine is a *view* over a markdown tree, not a content repository. The markdown tree is canonical; the running binary is a view that any number of operators can stand up over the same content tree, or different content trees, with no shared mutable state on the binary side. This source-of-truth inversion is the single most important design choice and is treated in detail in the next section.
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 →