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

Apprenticeship substrate

← All revisions

1eee203b · PointSav Digital Systems ·

editorial(substrate): fix apprenticeship-substrate capture-pipeline claims (Track-B) — re-verified directly against slm-doorman/src/verdict.rs: tenant is a field inside the JSONL record, not a directory segment (resolves conflicting prior claims); routing confirmed live via real shadow-capture data (14 tuples on record), but zero senior-signed verdicts exist yet — no task type has left its starting promotion stage; register-clean EN+ES

View the full record as of this revision →

@@ -77,18 +77,12 @@ Production routing eliminates senior tokens on graduated types. Shadow routing g
The apprenticeship corpus is a fourth corpus alongside the constitutional, engineering, and tenant-runtime corpora. Per-tenant partitioning lives at the directory level (see [[totebox-archive|Totebox]] storage layout):

```
data/training-corpus/apprenticeship/<task-type>/<tenant>/<ulid>.jsonl
data/training-corpus/apprenticeship/<task-type>/<ulid>.jsonl
```

**Correction (2026-08-02, verified against canonical `origin/main`):** the real path
(`service-slm/ARCHITECTURE.md` / `slm-doorman/src/verdict.rs`) has no `<tenant>` segment —
`data/training-corpus/apprenticeship/<task-type>/<ulid>.jsonl`. Separately, this
article's "the routing structure is operational today" claim above is also
stale — `service-slm/NEXT.md` lists re-enabling apprenticeship routing
(`SLM_APPRENTICESHIP_ENABLED=true`) as an open TODO, not a live default.
**Flagged, not resolved.**
One file holds one (brief, attempt, verdict) triple; the tenant is a field inside the record itself, not a directory segment. Tenant-private records never leave the tenant's infrastructure. A `refine` or `reject` verdict additionally produces a Direct Preference Optimisation triple — rejected attempt, corrected diff, constraint-violation tag — which feeds adapter training on the apprentice's policy.

One file holds one (brief, attempt, verdict) triple. Tenant-private records never leave the tenant's infrastructure. A `refine` or `reject` verdict additionally produces a Direct Preference Optimisation triple — rejected attempt, corrected diff, constraint-violation tag — which feeds adapter training on the apprentice's policy.
Routing is live and shadow capture is real: every code-shaped commit fires a brief and records a (brief, attempt, actual-diff) triple with no verdict attached. What hasn't happened yet is the senior-signed side — no task type has a scored verdict on record, so the promotion ledger has not moved any task type off its starting stage. The mechanism is switched on; the verdict loop that graduates it is still ahead.

## Configuration
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 →