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-LLM

← All revisions

e6a5ba5f · PointSav Digital Systems ·

correct(ai): fix Tier A/Yo-Yo table mislabel, flag Tier A model-name drift (pointsav-llm)

View the full record as of this revision →

@@ -9,7 +9,7 @@ quality: complete
short_description: "The planned vendor-tier specialist AI model for substrate-sovereign SMBs — Tier 3 of the Four-Tier SLM Substrate Ladder, built by continued pretraining of OLMo 3 32B."
status: active
bcsc_class: public-disclosure-safe
last_edited: 2026-04-30
last_edited: 2026-07-18
editor: pointsav-engineering
cites:
 - ni-51-102
@@ -49,6 +49,17 @@ The planned access path routes entirely through each customer's local [[doorman-

1. Customer application sends a query to the local [[doorman-protocol|Doorman]] (127.0.0.1:9080 by default).
2. Doorman classifies query complexity using the current Tier A local model (OLMo 3 7B Q4).

**Correction (2026-07-18):** the exact Tier A model name is inconsistent across this
wiki's own sibling articles and across the engineering source itself. This article says
"OLMo 3 7B Q4" (here and in the Four-Tier table below); [[learning-datagraph-architecture]]
says "the local SLM (OLMo-2 7B Q4)" for the same Tier A role, matching one internal
engineering doc (`service-slm/NEXT.md`: "OLMo-2-7B Q4_K_M; Tier A primary"); a third
internal doc describes Tier A as "OLMo 2 1B." These do not read as three names for one
model — they look like an unresolved version-drift in the underlying engineering docs
themselves, not just a wiki staleness issue. **Flagged, not resolved** — needs
project-totebox confirmation of the actual current Tier A model before either name is
corrected here.
3. For queries classified as simple or routine, the Doorman routes to Tier A and returns a local response — no external call.
4. For queries classified as requiring specialist depth (domain-specific platform conventions, [[totebox-archive|Totebox Archive]] operations, multi-tenant editorial structure), the Doorman is intended to route to the PointSav-LLM Tier C endpoint, authenticating via the customer's provisioned API key.
5. The response returns through the Doorman. An audit row is written simultaneously at the customer's local Doorman and at the PointSav-LLM gateway — two-ledger, per-call audit trail.
@@ -133,7 +144,7 @@ PointSav-LLM occupies Tier 3 of the planned Four-Tier SLM Substrate Ladder. The 
| Tier | Name | Base | Status |
|------|------|------|--------|
| 0 | Deterministic core | Rules, regex, structured lookup | Operational |
| A | Local small model | OLMo 3 7B Q4 (CPU) | Operational (Yo-Yo substrate) |
| A | Local small model | OLMo 3 7B Q4 (CPU) | Operational (local llama-server) |
| B | Burst compute | OLMo 3.1 32B Think (GPU via Yo-Yo) | Operational |
| C | Vendor specialist | PointSav-LLM (planned CPT of OLMo 3 32B) | Planned — Q1 2027 |

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 →