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

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

AI routing and the linguistic air-lock

AI routing, as it exists today, is the mechanism by which service-slm — the Doorman — mediates every request that involves a language model, across three compute tiers. service-slm is the sole boundary that holds external-model credentials and logs every call to the per-tenant audit ledger; no other component in the system holds external AI credentials or makes direct outbound calls to external language models.

This platform does not scrub personally identifiable information or location data from a prompt before an external call. The only sanitization code on the platform today is a credential redactor: it removes secrets — private keys, API tokens, generic bearer/secret/password patterns — and it runs solely on the path that writes training examples into the learning corpus, never on the path to an external model.

This is a compliance-relevant gap, not a cosmetic one, for regulated-industry readers — real estate, financial advisory, clinics, law firms — evaluating the platform's privacy protections. The honest current answer: when Tier C goes live, raw customer text will reach an external model unless a PII-scrubbing mechanism is built first. The credential redactor protects secrets, not customer data.

What's real today

  • Three compute tiers: Tier A (local), Tier B (Yo-Yo burst/GPU), Tier C (external API).
  • Model names: Tier A runs olmo-3-7b-instruct locally; Tier B (Yo-Yo) defaults to Olmo-3-1125-32B-Think.
  • Tier C is not live. The client is wired only against a test mock, and every call is gated behind a fixed, compile-time allowlist.
  • Every proxied call is audit-logged, with cost and response recorded to the audit ledger.
  • Every request carries a mandatory tenant tag.
  • No per-tenant budget cap gates routing decisions yet. Cost tracking and pricing configuration exist, but nothing currently ties a tenant's spend to a routing decision.

What is not built

PII scrubbing, location-identifier stripping, pseudonymous token substitution, and any form of rehydration mechanism are not built.

Applications — what the platform can honestly promise today

  • Editorial workflow: TOPIC and GUIDE drafts that reach Tier C today do so through the fixed allowlist's narrow-precision tasks (see Learning Datagraph — SLM trajectory loop and apprenticeship queue for draft_generate's behavior) — not through any sanitization step, because none exists for this path.
  • Financial advisory / real estate / clinic / law-firm use of Tier C is not yet a safe claim to make. Any of these use cases sending ledger records, client names, or property/owner records through Tier C today would reach the external model with PII unredacted. A real PII-scrubbing mechanism, independently verified, must exist before that changes.

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 →