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

Revision as of · 38f28cf1

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

How to use declarative knowledge mounts

Knowledge mounts allow a single wiki instance to serve content from multiple source repositories under a unified URL space. A mount is declared in knowledge.toml — the instance reads the source path at startup and makes its articles available at the configured category prefix. This guide covers adding a secondary content mount to an existing instance.

For the federation architecture that mounts enable, see Federate archives via content mounts. For deploying the wiki server in the first place, see Deploy a knowledge instance.

Prerequisites

  • A running knowledge instance with a knowledge.toml configuration (see Deploy a knowledge instance)
  • A second media-knowledge-* content repository cloned on the same host
  • Terminal access to restart the knowledge service

Step 1: Identify the secondary content path

The secondary content repository must be a media-knowledge-* clone on the same filesystem as the running instance. Note its absolute path:

ls /path/to/media-knowledge-projects/

Confirm it has a valid index.md and category subdirectories before adding the mount — the wiki server will warn at startup if the mount path is empty or malformed.

Step 2: Add the mount to knowledge.toml

Open knowledge.toml and add a [[mounts]] section after the [content] block:

[content]
primary_path = "/path/to/media-knowledge-documentation"
instance_name = "documentation"

[[mounts]]
path = "/path/to/media-knowledge-projects"
prefix = "projects"
label = "Projects"

path is the absolute filesystem path to the secondary repository. prefix is the URL prefix under which the mounted content will appear (e.g., mounted articles are served at /projects/<slug>). label appears in the navigation header to identify the mounted section.

Multiple mounts are supported — add additional [[mounts]] sections for each secondary repository.

Step 3: Restart the knowledge instance

The mount configuration is read at startup. Restart the service for the new mount to take effect:

sudo systemctl restart app-mediakit-knowledge

Or if running directly:

# stop the running process, then:
app-mediakit-knowledge --config knowledge.toml

Step 4: Verify the mount is serving

Fetch an article from the mounted category:

curl -s http://127.0.0.1:9090/projects/<slug-from-media-knowledge-projects>/

A successful response returns the rendered article HTML. If the response is 404, check:

  1. The prefix in knowledge.toml matches the URL path segment you used
  2. The path points to a directory with a _index.md in at least one subdirectory
  3. The service restarted cleanly (check journalctl -u app-mediakit-knowledge)

Step 5: Confirm wikilink isolation

Wikilinks inside mounted content resolve against the mounted repository's own slug namespace. A [[slug]] in a projects article will NOT resolve against a documentation article's slug — each mount is isolated. Cross-mount links must use full URLs.

This isolation is by design: the three live instances (documentation, projects, corporate) serve distinct editorial domains; mixing their slug namespaces would cause resolution conflicts.

Key takeaways

  • Mounts extend a running instance with content from a second repository, served under a URL prefix
  • Mount configuration lives in knowledge.toml under [[mounts]]; restart is required after changes
  • Wikilink resolution is per-mount — [[slug]] in a mounted section resolves against that section's slugs only
  • Multiple mounts are supported; add one [[mounts]] block per additional repository

See also

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 →