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

Trajectory substrate

← All revisions

7123c638 · PointSav Digital Systems ·

editorial(substrate): resolve trajectory-substrate's standing 2026-07-18 capture-mechanics flag (Track-B) — confirmed only capture-edit.sh exists (matches the prior finding), and its real mechanism is materially different from the 5-script JSONL-file table: it's a git post-commit hook that POSTs the commit diff (64 KiB truncated, not 1,000 lines) to the Doorman's /v1/shadow endpoint as an apprenticeship brief's actual_diff field, no-op without a pending brief — same live shadow-capture mechanism already verified in apprenticeship-substrate.md's Track-B rewrite. No redaction/sanitize step found in the script, consistent with the already-established finding that sanitize-outbound is fabricated elsewhere in this wiki; the 4 other named capture points remain genuinely unbuilt, stated as such rather than resolving the naming ambiguity unilaterally. Fixed the composition-formula base model name to OLMo-3-7B-Instruct per the live-verified finding on tier-zero-customer-side-sovereign-specialist.md. ES pair already clean, no change needed. Register-clean EN

View the full record as of this revision →

@@ -69,44 +69,19 @@ Tenant adapters do not leave the customer's deployment unless that customer expl

### Capture mechanics

**Correction (2026-07-18):** of the five scripts below, only one exists in the live
monorepo — `capture-edit.sh` (`service-slm/scripts/`), and even that has the wrong
extension here (this article says `capture-edit.py`; the real file is a `.sh`). A
repo-wide search finds no `capture-trajectory.sh`, `capture-doctrine.sh`,
`capture-feedback.sh`, or `capture-tenant-runtime.sh` anywhere. This is consistent with
(not contradicted by) the Configuration section below, which states only L1
("edit-corpus capture") is live and L2–L4 are planned/intended — but this table presents
all five scripts in the present tense with no such hedge, which reads as already-built.
**Flagged, not silently rewritten** — the L2–L4 script names may be provisional/aspirational
naming for not-yet-built capture points rather than a factual claim of existing files;
needs project-totebox confirmation of intended vs. actual naming before this table is
corrected.

Five scripts handle capture:

| Script | Trigger | Writes |
|---|---|---|
| `capture-edit.py` | `git post-commit` hook on cluster branches and the main branch | `engineering/<cluster>/<sha>.jsonl` |
| `capture-trajectory.sh` | Session end | `engineering/sessions/<id>.jsonl` |
| `capture-doctrine.sh` | Per platform MINOR bump | `doctrine/<version>/<tuple>.jsonl` |
| `capture-feedback.sh` | Inbox-archive of rejected or redo messages | `engineering/feedback/<record>.jsonl` |
| `capture-tenant-runtime.sh` | Scheduled inside deployment instance | `<instance>/training-corpus/<tenant>/<shard>.jsonl` |

Sanitize-outbound discipline applies at every capture point: private keys, PII, and customer-identifying details are redacted before write. Redaction runs at the capture script, not at the downstream consumer. Diff output is truncated at 1,000 lines.

Every JSONL record carries a provenance header with fields `tuple_type`, `doctrine_version`, `tenant`, `moduleId`, `cluster`, `role`, `scope`, `redaction_class`, `evidence_class`, `source_commit`, `session_id`, and `created`. The training pipeline filters on `(tenant, redaction_class, evidence_class)` to assemble each corpus. Any adapter version is re-derivable from its source records; any record can answer which adapter versions it trained.
One capture script is live today: `capture-edit.sh` (`service-slm/scripts/`), installed as a `git post-commit` hook. It does not write a JSONL file directly — it posts the commit's diff (stat header plus unified 3-line context, truncated at 64 KiB) and commit message to the Doorman's shadow-brief endpoint (`POST /v1/shadow`), where it becomes the `actual_diff` field of the pending brief. It is a no-op when no brief is pending for that repository. It carries no redaction or PII-scrubbing step of its own — matching the already-established finding that outbound sanitization elsewhere in the platform covers only the apprenticeship-corpus write path this script feeds, not a separate, general-purpose redaction layer.

The remaining four capture points this article names — session-end trajectory capture, doctrine capture on MINOR bumps, rejected-feedback capture, and tenant-runtime capture — describe intended future capture points, not scripts that exist in the monorepo today under any name found by a repo-wide search. Whether their eventual names match what's written here is not yet confirmed against any implementation plan.

Every JSONL record the live capture path produces carries a provenance header with fields including `tuple_type`, `doctrine_version`, `tenant`, `moduleId`, `cluster`, `role`, `scope`, `source_commit`, `session_id`, and `created`. The training pipeline is intended to filter on these fields to assemble each corpus once the pipeline itself is built; any adapter version is intended to be re-derivable from its source records.

### Adapter composition at request time

At inference time the [[compounding-doorman|Doorman]] (`service-slm`) composes adapters per request:

(Same base-model naming note as [[adapter-composition]] and [[pointsav-llm]] — the exact
Tier A model name is inconsistent across this wiki and the underlying engineering docs;
not re-litigated here.)

```
composed_weights =
  base_model[OLMo-3-1125-7B-Q4]
  base_model[OLMo-3-7B-Instruct]
  ⊕ constitutional[doctrine_v0.0.x] ← always
  ⊕ engineering[pointsav_vN]? ← if request is platform-build context
  ⊕ tenant[<tenant>_vK]? ← if request is tenant-data context
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 →