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

Compounding Doorman

← All revisions

ed8c0aaf · PointSav Digital Systems · 2 August 2026

correct(substrate): flag wrong audit ledger path vs real SLM_AUDIT_DIR (compounding-doorman)

View the full record as of this revision →

@@ -9,7 +9,7 @@ quality: complete
short_description: "The operational pattern at the heart of sovereign AI substrates: a single service mediating every external compute call, logging events, accumulating training signal."
status: active
bcsc_class: public-disclosure-safe
last_edited: 2026-04-30
last_edited: 2026-07-18
editor: pointsav-engineering
cites: []
paired_with: compounding-doorman.es.md
@@ -70,6 +70,16 @@ This is what allows a deployment to operate Ring 3 at any trust level — from f

The Doorman (`service-slm`) is operational on the workspace VM. It binds at `127.0.0.1:9080`, routes Tier A to the local model service, and enforces sanitise-outbound and rehydrate-inbound discipline on every call. The audit ledger writes to `data/audit-ledger/<tenant>/<YYYY-MM>.jsonl`.

**Correction (2026-07-18):** the bind address checks out (`127.0.0.1:9080`, confirmed
against `SLM_BIND_ADDR` in the live deploy config), but the audit ledger path does not.
The real env var is `SLM_AUDIT_DIR` (`slm-doorman-server/src/main.rs`), with the
workspace dogfood deployment explicitly setting it to `/var/lib/local-doorman/audit/`
(default when unset: `$HOME/.service-slm/audit/`) — not `data/audit-ledger/<tenant>/
<YYYY-MM>.jsonl` as this article states. Whether the per-tenant/per-month filename
structure inside that directory matches this article's `<tenant>/<YYYY-MM>.jsonl` shape
was not independently re-verified here. **Flagged, not silently rewritten** — needs
project-totebox confirmation of the real internal layout before this line is corrected.

Tier B integration (Yo-Yo GPU burst) is in progress. Tier C external API routing is available for narrow precision tasks where the operator has explicitly configured an allowlist.

LoRA adapter training — the mechanism that makes the Doorman compound — depends on the [[brief-queue-substrate]] for corpus capture and the [[apprenticeship-substrate]] for the training pipeline. Both are operational or in active development.

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 →