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

Workspace services slice — cgroup partitioning for multi-developer environments

← All revisions

b2b42d6c · PointSav Digital Systems ·

correct(architecture): flag CPUWeight/OOMScoreAdjust claims not found in live foundry-services.slice (foundry-services-slice-model)

View the full record as of this revision →

@@ -9,7 +9,7 @@ type: topic
content_type: topic
status: active
bcsc_class: public-disclosure-safe
last_edited: 2026-05-25
last_edited: 2026-07-18
editor: pointsav-engineering
cites: []
paired_with: foundry-services-slice-model.es.md
@@ -32,12 +32,33 @@ The [[pointsav-overview|PointSav]] development environment runs production servi

An initial hardening pass introduced `foundry-services.slice` — a systemd cgroup partition with `CPUWeight=200` and `MemoryHigh=11G` that holds every `local-*.service`. Default systemd user slices (`user-1001.slice`, `user-1002.slice`) sit at `CPUWeight=100`, so under CPU contention the service group receives 2× the scheduler weight relative to a single interactive shell. Memory ceilings prevent any one service from pinning more than approximately 11 GiB on a 16 GiB VM; with `OOMScoreAdjust` ordering (sshd −1000, local-fs −500, local-doorman −300, local-slm +500), the kernel's last-resort kill prefers cheap-to-restart services over the WORM ledger writer or the operator's SSH connection.

**Correction (2026-07-18):** the live `foundry-services.slice` in the monorepo
(`infrastructure/systemd/foundry-services.slice`) does not match this description. It sets
`MemoryMin=12G` (a memory-reservation guarantee against eviction under host pressure, sized
against a 31G host, not an 11G ceiling on a 16G VM) — no `CPUWeight` setting appears anywhere
in the slice file, and a repo-wide search finds `CPUWeight` nowhere in the monorepo at all.
The mechanism described in the file's own comments is different in kind: per-service
`MemoryMin` budgeting (local-content/LadybugDB gets a 2G guarantee; local-slm and
local-doorman have none set) rather than a CPU-weight/OOMScoreAdjust scheme. The only
`OOMScoreAdjust` setting found anywhere in the monorepo is on `local-content` (`-200`,
"moderately protected") — not the four-service sshd/local-fs/local-doorman/local-slm
ordering this article describes. **Flagged, not silently rewritten** — this reads as an
earlier design superseded by a simpler memory-reservation-only mechanism, but needs
project-totebox confirmation before the CPU-weight and OOM-ordering claims are corrected
or removed.

## 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.

Where this lives on disk: `/etc/systemd/system/services.slice`, plus `Slice=` drop-ins under `/etc/systemd/system/local-*.service.d/slice.conf`. The version-controlled source mirrors live under the monorepo's `infrastructure/` directory.

**Correction (2026-07-18):** the version-controlled source names do not match those paths.
The slice file is `infrastructure/systemd/foundry-services.slice` (not `services.slice`),
and the only matching drop-ins found are `local-content-memory.conf` and
`local-content-oom.conf` (not a generic `slice.conf` per service). Flagged alongside the
CPU-weight/OOM-ordering correction above — same underlying staleness.

## See also

- [[multi-engine-session-coordination]] — how concurrent AI-coding sessions coordinate access to the same workspace to prevent index corruption
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 →