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 · dcf2dd1c

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

Workspace services slice — cgroup partitioning for multi-developer environments

The PointSav development environment runs production services and interactive engineering sessions on the same Linux host. The workspace services slice pattern ensures that build-session resource bursts do not starve the inference and ledger services that other operators depend on during the same session.

Key Takeaways

  • foundry-services.slice reserves 12G of RAM (MemoryMin=12G, on a 31G host) that the kernel will not reclaim from the platform's services even under severe host memory pressure — a guarantee, not a ceiling.
  • One service, local-content (the entity graph), carries additional protection: a 2G MemoryMin of its own plus OOMScoreAdjust=-200, making it a late candidate for the kernel's last-resort kill. No other service currently carries this protection.
  • This is not Kubernetes. No scheduler, no replica controller, no service mesh, and no CPU-weight scheduling — just a memory reservation plus one service's OOM protection. Appropriate for a single-node deployment of up to roughly 12 services.
  • The cgroup discipline carries forward when scale increases. The per-service Slice= drop-in pattern is compatible with more complex multi-node orchestration.

Resource contention on a shared host

The PointSav development environment runs production services and interactive engineering sessions on the same Linux host. Platform services (the local SLM, Doorman, content graph, ledger writer, and proofreader) share memory with multi-operator build sessions and research/GIS batch processes. Without protection, a memory-heavy process outside the slice can evict a platform service's working set under host pressure — service-content was observed hitting this exactly, going unresponsive when an external Python process exhausted host RAM.

A memory reservation, not a CPU or OOM-ordering scheme

foundry-services.slice sets MemoryMin=12G on a 31G host: a floor the kernel will not reclaim below for any service in the slice, even under severe pressure — sized as the local SLM's ~7G working set, local-content's own 2G reservation, and a 3G buffer for the rest. There is no CPUWeight setting anywhere in this slice or anywhere else in the monorepo; CPU scheduling is not part of this mechanism.

Only local-content carries additional protection beyond the slice-wide floor: its own MemoryMin=2G (plus MemoryHigh=5500M, MemoryMax=6G, and MemorySwapMax=0 — it is never swapped, since a partially-swapped entity graph can't serve real-time queries), and OOMScoreAdjust=-200. That negative score tells the kernel's OOM killer to treat local-content as a late candidate — the graph takes minutes to rebuild if killed. No other platform service (local-doorman, the local SLM) carries its own OOMScoreAdjust setting today; a three-tier hierarchy is described in local-content's own configuration comments as the rationale for its value, but only local-content's own score is actually applied.

Single-node scope without Kubernetes

This is not orchestration in the Kubernetes sense — there is no scheduler, no replica controller, no service mesh. systemd is enough. The pattern scales to roughly a dozen services on a single GCE VM, the compact single-node configuration that characterises a minimal sovereign deployment. Beyond that scale, the architecture changes — but the cgroup discipline carries forward.

Installed as /etc/systemd/system/foundry-services.slice, plus per-service memory and OOM-protection drop-ins under each protected service's own .service.d/ directory.

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 →