Skip to content
PointSav Digital Systems

Revision as of · 626563df

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

os-orchestration — The Fleet Aggregator

os-orchestration is the commercial-tier operating system that lets a single operator see, query, and command many Totebox archives at once. Where os-console connects to one os-totebox, os-orchestration is the hub between an operator's Console and a fleet of Toteboxes. It is what an executive views when they want the position of every property in a portfolio, every entity in a holding company, or every project in a development pipeline — a single unified answer to "what is the state of the entire estate, right now?" This article covers what os-orchestration does, what it deliberately does not do, how aggregation works, the commercial features it adds, and when to deploy it.

What it does not do

os-orchestration does not store raw records. It is stateless. It pulls metadata from Toteboxes, synthesises a unified view, and presents it through os-console. Raw data never leaves its sovereign Totebox. The aggregator sees only what the Totebox is permitted to expose.

This boundary is structurally important: even if os-orchestration is compromised, the underlying Toteboxes remain sealed. The aggregator holds no keys to the archives.

Where it sits in the product line

Component Role Licence model (planned)
os-console Operator-facing terminal Apache 2.0 (intended to be free)
os-totebox Data archive per entity Apache 2.0 (intended to be free)
os-orchestration Fleet aggregator Proprietary (intended as a commercial product)

The commercial line is drawn at the aggregator. The Console and the Totebox are intended to be free and freely transferable. The Orchestration aggregator is the paid product — an individual operator managing one entity never needs it.

How aggregation works

os-orchestration connects to Toteboxes through the PointSav Protocol (PSP) — a capability-based binary protocol that tunnels through standard TLS at the edge. Inside the tunnel:

  1. The aggregator sends a signed capability object granting permission to read a specific row of a specific Totebox for a fixed time window.
  2. The Totebox verifies the capability, runs the query internally, and emits only the result — never the raw record.
  3. The aggregator combines results from many Toteboxes into a single unified view.

Promise pipelining and zero-copy memory mapping make the experience feel local even when Toteboxes are distributed across multiple regions.

The commercial features

Three capabilities are reserved exclusively to os-orchestration:

Feature What it enables
Aggregation Reading metadata from multiple Toteboxes simultaneously
Multi-tenancy Serving multiple operators against the same underlying fleet
Complex viewports Cross-archive dashboards — portfolio rollups, cross-entity reconciliation, executive summaries

These features are intentionally absent from the open os-console codebase. They live in the os-orchestration codebase and nowhere else.

The Diode discipline

os-orchestration can issue commands downstream to the Toteboxes it manages. The Toteboxes cannot issue commands back up. The aggregator is itself a Diode subject: it receives commands only from os-console, never from a Totebox. This makes lateral movement structurally impossible — a compromised Totebox cannot use the aggregator as a bridge to the operator's Console.

When to deploy

os-orchestration is a commercial product for multi-entity operators. Single-entity operators managing one Totebox do not need it. Multi-entity operators — real-estate portfolios, public companies with subsidiaries, family offices with multiple holdings — deploy it when the cognitive load of running separate Consoles against individual Toteboxes justifies the aggregator.

See also

  • console-os — the Direct vs. Aggregate mode distinction; os-console pairs with os-orchestration in Aggregate mode
  • totebox-os — the archives being aggregated
  • diode-standard — the unidirectional command discipline that governs the aggregator
  • machine-based-auth — how pairings secure aggregator-to-Totebox connections
  • deployment-patterns — how os-orchestration appears in commercial deployment configurations
  • os-family-overview — the eight-OS family and how os-orchestration fits
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 →