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

SLM Rust stack architecture

← All revisions

6a430753 · PointSav Digital Systems ·

fix(ai): add dated Correction callouts to 7 of 10 ai/ articles — decode-time constraints, SLM stack deps, sovereign-ai-routing PII claim (compliance-relevant), draft-generate endpoint underclaim, plus 3 minor factual slips; 3 articles verified clean

View the full record as of this revision →

@@ -15,6 +15,8 @@ cites: []
paired_with: slm-stack-architecture.es.md
---

**Correction (2026-08-02):** most of the specific stack described below does not match the real `service-slm` codebase. **Inference**: the real runtime is **llama-server (llama.cpp)** at Tier A and **vLLM** at Tier B — both external, non-Rust binaries called over HTTP (`service-slm/ARCHITECTURE.md:225-233`); `mistral.rs` and `candle` are not deployed anywhere (candle is listed only as a hypothetical future path). **Storage**: the real crate uses `rusqlite`, not `sqlx` (zero `sqlx` hits in `Cargo.lock`). **Document processing / orchestration / observability**: `oxidize-pdf`, `docx-rust`, `calamine`, `pulldown-cmark`, `apalis`, `object_store`, `opentelemetry-rust`, `sigstore-rs`, and `mupdf-rs` — none appear anywhere in the workspace's 286-crate `Cargo.lock`. **Binary/crate layout**: the "Flat binary architecture" section below invents `slm-ledger`, `slm-compute`, `slm-memory-kv`, `slm-memory-adapters`, `slm-inference-local`, `slm-inference-remote`, `slm-api`, `slm-cli` as a single-binary design; the real workspace has five crates (`slm-core`, `slm-doorman`, `slm-doorman-server`, `adapter-hub`, `slm-mcp-server`) with two actual `[[bin]]` targets, not one. What's confirmed accurate: the axum/tower/tokio/reqwest/tracing base, the `cargo-deny`/`deny.toml` license-policy mechanism, and LadybugDB as the knowledge-graph store. **Flagged, not resolved** — this needs a rewrite of the "canonical stack" and "flat binary architecture" sections against the real dependency graph, not a wording fix.

[[service-slm|`service-slm`]] is built as a single, statically-linked Rust binary. Every direct dependency in the stack is either pure Rust or Rust bindings to a permissively licensed native library. No copyleft licenses appear anywhere in the dependency graph, which means [[pointsav-overview|PointSav]] holds an unrestricted right to fork, modify, and redistribute the entire codebase. This property is called the "We Own It" criterion.

The choice of Rust is not a language preference. It is an engineering constraint imposed by the intended deployment target — [[totebox-os|ToteboxOS]] appliance hardware, where a CPython interpreter plus a large ML framework does not fit in the available memory envelope, and where cold-start predictability and the absence of a garbage collector are operational requirements rather than optional improvements.
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 →