Skip to content
PointSav Digital Systems

Capability Geometry: seL4 Capability Authorization in Totebox Orchestration

← All revisions

eed765ab · PointSav Digital Systems ·

Linking heal (documentation): first-mention wikilinks on 48 under-linked articles (171 links, index-validated, no red links); EN only, ES pairs follow-up

View the full record as of this revision →

@@ -48,7 +48,7 @@ surface's logical structure.

## The seL4 Capability Model: Authorization as a Formal DAG

The seL4 microkernel implements a different model. Access to any resource — a memory
The [[sel4-microkernel-substrate|seL4 microkernel]] implements a different model. Access to any resource — a memory
region, a network endpoint, a storage device — requires holding an unforgeable capability
token for that resource. Not a credential. Not a session token. A mathematical object
issued by the kernel itself.
@@ -98,7 +98,7 @@ a policy enforced by software that can be subverted.

## PointSav Implementation: system-core and system-ledger

The capability substrate in Totebox Orchestration is implemented in two Rust crates:
The capability substrate in [[totebox-orchestration|Totebox Orchestration]] is implemented in two Rust crates:

**system-core v1.0.0** defines the capability type system:

@@ -113,7 +113,7 @@ pub struct Capability {
```

A `Capability` is not a session token. It is a typed, rights-bounded, optionally time-limited
object anchored to the WORM audit ledger.
object anchored to the [[worm-ledger-architecture|WORM audit ledger]].

**system-ledger v1.0.0** provides the verdict function:

@@ -127,14 +127,14 @@ pub enum Verdict {

`consult_capability()` on `InMemoryLedger` evaluates a capability invocation against the
current ledger state and returns a `Verdict`. The ledger is append-only (WORM) and anchored
via RFC 9162 Merkle proof chains. The audit trail for F12 (SYS-ADR-10) routes through
via RFC 9162 [[merkle-proofs-as-substrate-primitive|Merkle proof]] chains. The audit trail for F12 (SYS-ADR-10) routes through
this verdict function.

---

## Machine Pairing as Capability Minting

F11 machine pairing in os-console is the intended capability minting ceremony for Totebox
[[pairing-as-permission|F11 machine pairing]] in os-console is the intended capability minting ceremony for Totebox
access (planned; Phase H3 of the os-console substrate roadmap):

1. The Totebox pairing authority holds a `CapabilityType::CNode` — the root of its
@@ -169,10 +169,10 @@ machine-level identity anchor for Totebox Orchestration.
## Leapfrog 2030 Alignment

Capability Geometry is the Totebox security model intended to be in place by the
Leapfrog 2030 milestone. The seL4 Microkit substrate (Doctrine claim #34, Two-Bottoms
[[leapfrog-2030-architecture|Leapfrog 2030]] milestone. The seL4 Microkit substrate (Doctrine claim #34, Two-Bottoms
Sovereign Substrate) provides the kernel layer. system-core and system-ledger provide
the Rust-language capability substrate above it. The three-binary architecture
(os-console, os-totebox, os-orchestration) implements Capability Geometry at each
the Rust-language capability substrate above it. The [[topic-three-binary-architecture|three-binary architecture]]
(os-console, [[os-totebox]], [[os-orchestration]]) implements Capability Geometry at each
layer: per-cartridge PD on os-console, per-service PD on os-totebox, and a
capability-broker PD on os-orchestration that holds cross-Totebox endpoint capabilities.
Important Information

Important Information

Corporate structure. PointSav Digital Systems ("PointSav") is a trade name of Woodfine Capital Projects Inc. ("Woodfine"). 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. See TRADEMARK.md in this repository for the full trademark notice.

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 →