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

Pairing as permission

← 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: sovereignty-and-infrastructure-patterns
short_description: "PairingAsPermission is the Object Capability access-control model in Totebox Orchestration: a cryptographic pairing is the permission; its absence means no pathway."
status: active
bcsc_class: no-disclosure-implication
@@ -29,7 +30,7 @@ PairingAsPermission is the access-control model used in [[totebox-orchestration|

This article describes the principle, the topology in Totebox Orchestration, the engineering risks, and the production reference implementations.

**Correction (2026-08-02):** the "Command"/"os-orchestration hub" topology described throughout this article (below, and at the `SYS-CONTRACTS-01` claim further down) is not a built PointSav product — no `os-orchestration` or `app-orchestration-command` crate exists anywhere in the monorepo, matching the finding on [[app-orchestration-command-branch-model]]. `pairings.yaml` is real, but it's `/srv/foundry/pairings.yaml`, the Foundry *workspace's own* cluster-manifest index maintained by the Command Session — not a PointSav customer-deployment mechanism. The general Object Capability / cryptographic-pairing principle this article argues for is a real, legitimate design pattern (well-cited, accurately describing Fuchsia/seL4/WireGuard precedent), but its "production reference implementation" claims for PointSav's own topology describe tooling that doesn't exist yet. **Flagged, not resolved.**
**Correction (2026-08-02, updated 2026-08-06):** `pairings.yaml` is real, but it's `/srv/foundry/pairings.yaml`, the Foundry *workspace's own* cluster-manifest index maintained by the Command Session — not a PointSav customer-deployment mechanism. `app-orchestration-command` is real and substantial on canonical (invite/pairing, fleet visibility, personnel/permission tiers, GPU brokering — see [[personnel-permissions]]), but does not implement the specific "Command"/"os-orchestration hub" topology described throughout this article, including the `SYS-CONTRACTS-01` claim further down. The general Object Capability / cryptographic-pairing principle this article argues for is a real, legitimate design pattern (well-cited, accurately describing Fuchsia/seL4/WireGuard precedent), but its "production reference implementation" claims for PointSav's own topology describe tooling that doesn't exist yet. **Flagged, not resolved.**

## The core principle

@@ -96,7 +97,7 @@ Defence: capability attenuation via separate module identifiers. The Command hol

The current implementation uses `system-mba-shim` — a transitional layer behind which conventional OAuth2 authentication sits. The `system-mba-shim` interface is the clean boundary: when the full PairingAsPermission cryptographic model (certificate-based peer-to-peer key exchange) replaces the OAuth2 layer, no calling code changes. The interface stays constant; the implementation behind it is upgraded in place.

The Six Orchestration Contracts include `pairing_attestation` as `SYS-CONTRACTS-01`, hardcoded into the operating-system kernel. It is not configurable. (Correction, 2026-08-02: this is not physically possible today — `os-totebox` is a plain Rust/tokio binary with zero seL4 dependency, confirmed via this repo's own `cleanup-log.md`; there is no kernel to hardcode a contract into. `SYS-CONTRACTS-01` appears in the real codebase only inside a planning artifact, `service-content/artifacts/FOUNDRY_MASTER_CONTEXT.md`, as a documentation-topic reference, not kernel code. Separately (**retracted, 2026-08-02**): this correction previously said `os-orchestration`/`app-orchestration-command` "is not a built crate at all" — that was checked against a stale local branch; both are real on canonical (`origin/main`), `app-orchestration-command` substantially so. See the updated finding on [[app-orchestration-command-branch-model]]. The seL4-kernel and `SYS-CONTRACTS-01` findings above are unaffected by this retraction. Flagged, not resolved.)
The Six Orchestration Contracts include `pairing_attestation` as `SYS-CONTRACTS-01`, hardcoded into the operating-system kernel. It is not configurable. (Correction, 2026-08-02: this is not physically possible today — `os-totebox` is a plain Rust/tokio binary with zero seL4 dependency, confirmed via this repo's own `cleanup-log.md`; there is no kernel to hardcode a contract into. `SYS-CONTRACTS-01` appears in the real codebase only inside a planning artifact, `service-content/artifacts/FOUNDRY_MASTER_CONTEXT.md`, as a documentation-topic reference, not kernel code. Separately (**retracted, 2026-08-02**): this correction previously said `os-orchestration`/`app-orchestration-command` "is not a built crate at all" — that was checked against a stale local branch; both are real on canonical (`origin/main`), `app-orchestration-command` substantially so (see [[personnel-permissions]] for its real function). The seL4-kernel and `SYS-CONTRACTS-01` findings above are unaffected by this retraction. Flagged, not resolved.)

## The Trustworthy System
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 →