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

Model tier discipline

← All revisions

3f571a87 · PointSav Digital Systems ·

fix(applications,systems,patterns): correct app-orchestration-command misattribution, retire 2 redundant articles

View the full record as of this revision →

@@ -6,6 +6,7 @@ category: patterns
type: topic
content_type: topic
quality: complete
index_group: collaboration-and-editorial-workflow
short_description: "The discipline for routing work to the appropriate AI model tier — deep-think, implementation, or mechanical — to match model capability to work shape and control inference cost."
status: active
bcsc_class: public-disclosure-safe
@@ -15,7 +16,7 @@ cites: []
paired_with: model-tier-discipline.es.md
---

**Correction (2026-08-02):** the Doorman does not implement this deep-think/implementation/mechanical taxonomy. The real Doorman tier enum (`service-slm/crates/slm-core/src/tier.rs`) is `Local` (Tier A, on-host inference)/`Yoyo` (Tier B, burst GPU)/`External` (Tier C, external API) — an AI-inference-*backend* routing scheme, confirmed by both `reference/service-slm-operationalization-plan.md` and `ai/doorman-protocol.md`, neither of which mentions "deep-think"/"mechanical." The concept this article actually describes is real, but it's this very Foundry *workspace's own internal* practice for routing AI-development-session work to different Claude model tiers by task shape — `conventions/model-tier-discipline.md` in the workspace root — not something the customer-facing Doorman implements. Same misattribution pattern already found in `systems/app-orchestration-command-branch-model.md` (Foundry-internal tooling described as a PointSav product). **Flagged, not resolved.**
**Correction (2026-08-02):** the Doorman does not implement this deep-think/implementation/mechanical taxonomy. The real Doorman tier enum (`service-slm/crates/slm-core/src/tier.rs`) is `Local` (Tier A, on-host inference)/`Yoyo` (Tier B, burst GPU)/`External` (Tier C, external API) — an AI-inference-*backend* routing scheme, confirmed by both `reference/service-slm-operationalization-plan.md` and `ai/doorman-protocol.md`, neither of which mentions "deep-think"/"mechanical." The concept this article actually describes is real, but it's this very Foundry *workspace's own internal* practice for routing AI-development-session work to different Claude model tiers by task shape — `conventions/model-tier-discipline.md` in the workspace root — not something the customer-facing Doorman implements. Same misattribution pattern found and corrected elsewhere in this corpus (Foundry-internal tooling described as a PointSav product) — see [[five-stage-supply-chain]] and [[scaling-coordinated-development-totebox-archives]] for the resolved cases. **Flagged, not resolved** for this specific article.

A platform that routes all inference work through the highest-capability model available regardless of work shape spends significantly more per output than necessary. Model tier discipline is the routing discipline implemented by the [[service-slm-operationalization-plan|compute routing architecture]] through the [[doorman-protocol|Doorman service]]. A platform with no guidance on model selection leaves each contributor to make independent choices that may be inconsistent, cost-inefficient, or both. Model tier discipline is the structured approach that matches work shape to model capability, routes appropriate work to lower-cost tiers, and makes the routing decision explicit and reviewable.
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 →