Skip to content
PointSav Digital Systems

Revision as of · 4ab1e8f4

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

Sovereign compliance appliance

os-mediakit is the public-facing operating system in the PointSav family. It hosts a company's marketing website, its internal wiki, and its compliance newsroom — three workloads that typically live on rented third-party platforms and that disappear the moment a subscription ends. The target operator is a Reporting Issuer: a company with statutory disclosure obligations that needs mathematical proof of what it disclosed and exactly when. os-mediakit is built on a hardened FreeBSD base and ships three application surfaces as isolated workloads. This article covers the three surfaces, the FreeBSD licensing rationale, the Compliance Ledger, the Diode adapter, and the two deployment postures.

The three application surfaces

os-mediakit hosts three surfaces on a single appliance. Each workload runs as an isolated instance so that a heavy database query on the wiki cannot induce latency on the landing page:

Surface Engine Role
[app-mediakit-marketing](/wiki/app-mediakit-marketing) Stripped static site engine with a Rust cache layer Public landing pages and investor-relations pages
[app-mediakit-knowledge](/wiki/app-mediakit-knowledge) Markdown wiki engine with content-contract-conforming storage Corporate wiki, project wiki, documentation wiki
app-mediakit-distribution Push-based compliance feed engine Press releases, regulatory filings, executive commentary

Why FreeBSD

The choice of base OS is deliberate. FreeBSD's BSD licence allows PointSav to take the code, modify it, close the modifications, and ship a proprietary distribution without obligation to open-source those modifications. The result is a legally clean path to a proprietary compliance appliance.

The intended roadmap for the substrate is a four-phase metamorphosis:

Phase Form Status
1 Hardened FreeBSD host with the three apps running in jails Initial
2 NanoBSD — a stripped, read-only variant Planned
3 Custom kernel with interpreted-language rendering replaced by Rust Planned
4 Unikernel — OS and application fused into a single binary Planned

The Compliance Ledger

The distinguishing capability is app-mediakit-distribution. Conventional investor-relations platforms pull wire-service data after the fact and serve it as a static page. os-mediakit inverts the flow:

  1. A press release is drafted inside os-totebox and cryptographically signed.
  2. os-totebox pushes the signed payload to os-mediakit-distribution at the moment of release.
  3. os-mediakit archives the signed content, the timestamp, and the cryptographic signature before publishing.
  4. The website updates at the moment of release. The signed record remains in os-mediakit permanently.

The result is mathematical proof of what was disclosed and exactly when. The company does not lose its archive when a subscription ends — the company owns the appliance.

The Diode connection

os-mediakit faces the public internet. os-totebox does not. The two connect only through a unidirectional adapter (service-pointsav-link, planned) that permits commands and content to flow from the internal Totebox to the public MediaKit, but never the reverse. A compromised plugin on the marketing surface cannot reach back into the corporate Totebox, because the code to do so is absent from the adapter.

The adapter is a separately installed package. Operators who do not need fleet management can run os-mediakit with no adapter at all; the OS has no capability to phone home.

Standalone or federated

os-mediakit deploys in two postures:

Posture Use case Interface
Standalone A freelancer or SMB hosting one or two public sites Local TUI accessed by SSH
Federated A commercial operator managing many sites from a central fleet The local TUI becomes a status monitor; control passes to os-orchestration

Both postures use the same os-mediakit binary. The transition is one command: install the adapter package, perform a one-time pairing handshake, and the MediaKit instance joins the fleet mesh.

See also

Important Information

Important Information

Corporate structure. PointSav Digital Systems ("PointSav") is a trade name of Woodfine Capital Projects Inc. ("Woodfine"). 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. See TRADEMARK.md in this repository for the full trademark notice.

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 →