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

Revision as of · 2ffa9bf0

Historical revision — this record as it stood on 6 August 2026, not the current version. View the current record →

Self-host a deployment

Prerequisites

  • A host that can run QEMU for aarch64 (the appliance images target this architecture regardless of your host's own CPU)
  • The published os-totebox-loader.img and, optionally, app-orchestration-slm-loader.img from software.pointsav.com
  • A persistent disk image, created once and kept — an ext4-formatted raw file the guest mounts at /data
  • If you need non-default configuration (a specific orchestration endpoint, a Tier B license): the source repo, the Microkit SDK, and an aarch64 cross-compilation toolchain — the published images alone don't let you change configuration after the fact (see Step 3)

Purpose

Self-hosting a deployment means booting one or both of two independent, self-contained seL4/Microkit appliance images on operator-controlled infrastructure: os-totebox (the Sovereign WORM Data Vault — local DataGraph, corpus ingestion, Tier A operations) and app-orchestration-slm (the Yo-Yo broker chassis — health, fleet, and discovery endpoints; Tier B brokering requires a license). Each runs standalone by default; neither needs the other present to start.

Procedure

  1. Create your persistent disk, once:

    qemu-img create -f raw persistent.raw 2G

    This is where DataGraph state, adapter weights, and cached identity survive across restarts. Losing this file means losing everything the appliance has accumulated — it is not regenerated from the image.

  2. Boot the image via QEMU's -device loader mechanism (this is Microkit's own loader path, not the -kernel/-append path a general-purpose Linux VM would use):

    qemu-system-aarch64 \
  -machine virt,virtualization=on,secure=off -cpu cortex-a53 \
  -device loader,file=os-totebox-loader.img,addr=0x70000000,cpu-num=0 \
  -m size=2G -nographic -global virtio-mmio.force-legacy=false \
  -drive file=persistent.raw,format=raw,if=none,id=hd \
  -device virtio-blk-device,drive=hd,bus=virtio-mmio-bus.1 \
  -device virtio-net-device,netdev=netdev0,bus=virtio-mmio-bus.0 \
  -netdev user,id=netdev0,hostfwd=tcp::<host-port>-:<guest-port>

  3. If the published, generic image's default configuration is sufficient, skip to Step 4. Otherwise, understand this before you try to change anything: runtime configuration is baked into the image at build time, in the device tree's bootargs. There is no post-boot config file and no -append equivalent on this boot path. Changing configuration means rebuilding the image yourself, with your own foundry.* bootarg values, and replacing the published one — see the relevant keys below and the full rebuild procedure in the internal dogfood development guide (GUIDE-live-flow-doorman-orchestration-yoyo.draft.md, project-totebox).

    Key Appliance Purpose
    foundry.orchestration_endpoint os-totebox Chassis URL for Tier B brokering
    foundry.tier_b_subscribed os-totebox true to claim a paid subscription at registration
    foundry.yoyo_default_endpoint app-orchestration-slm Default Yo-Yo compute backend URL
    foundry.license_token / foundry.license_pubkey_hex app-orchestration-slm Ed25519-signed Tier B license

  4. Repeat Step 2 for app-orchestration-slm-loader.img if you want the Yo-Yo broker chassis too — it's an independent image with its own boot invocation, not a component started from inside os-totebox.

Expected outcome

os-totebox reaches a healthy, standalone state within seconds of boot, with or without app-orchestration-slm present — this degrade-not-refuse behavior is the intended design, not a sign of misconfiguration. app-orchestration-slm, if booted, answers health/fleet/discovery requests standalone; Tier B brokering itself stays disabled until a valid license is baked into a rebuilt image.

Verification

curl http://<host>:<totebox-port>/healthz       # os-totebox
curl http://<host>:<orchestration-port>/healthz  # app-orchestration-slm
curl http://<host>:<orchestration-port>/readyz   # license / fleet / circuit status

Rollback

Stop the QEMU process. The persistent disk (persistent.raw) is untouched by stopping the guest — restarting the same boot command resumes from the same accumulated state. To discard accumulated state entirely, discard the persistent disk file itself and create a fresh one (Step 1); there is no partial-reset mechanism short of that.

Next steps

Known limitations, as shipped (2026-08-03)

  • No automated update mechanism — a configuration change means a rebuild and a full image replacement, not a live edit.
  • The published images have not been through a customer-scale security review; treat as an early release.
  • Real GPU-scale training requires your own Yo-Yo compute backend — the images themselves don't include one.

See also

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 →