Skip to content
PointSav Digital Systems

Totebox orchestration as the development environment

← All revisions

ea347f81 · PointSav Digital Systems ·

docs(2i-arch): Bloomberg vocab scrub — second architecture batch (EN+ES, 12 articles)

View the full record as of this revision →

@@ -16,7 +16,7 @@ cites:
paired_with: totebox-orchestration-development.es.md
---

PointSav's development environment is deployed as a Totebox Orchestration instance — the same architecture the platform delivers to customers. The Foundry workspace, where the platform is written and shipped, runs as a hub coordinating thirteen Totebox Archives over a single shared `service-slm` access-control gateway. The development workflow is the customer workflow. There is no test environment that diverges from production architecture; the environment that produces the code is the architecture the code describes.
PointSav's development environment is deployed as a Totebox Orchestration instance — the same architecture the platform delivers to customers. The development workspace, where the platform is written and shipped, runs as a hub coordinating thirteen Totebox Archives over a single shared `service-slm` access-control gateway. The development workflow is the customer workflow. There is no test environment that diverges from production architecture; the environment that produces the code is the architecture the code describes.

This article documents how the workspace maps onto Totebox Orchestration, what the Command Session and Totebox Sessions own, and which components are operationally live versus planned.

@@ -24,9 +24,9 @@ This article documents how the workspace maps onto Totebox Orchestration, what t

Totebox Orchestration organises work into Totebox Archives — self-contained units, each holding source code, operational guides, a live deployment, and a wiki contribution. A Command Session acts as the hub: it holds pairings to every archive and coordinates cross-archive work. A Totebox Session opens within a single archive and operates only within that archive's declared scope.

The Foundry workspace maps directly onto this topology:
The development workspace maps directly onto this topology:

| Foundry concept | Totebox Orchestration equivalent |
| Development workspace | Totebox Orchestration equivalent |
|---|---|
| The workspace | Command Session — hub, identity store, cross-archive coordination |
| Each `clones/project-*/` directory | A Totebox Archive |
@@ -69,7 +69,7 @@ Every Totebox Archive declares a Project Tetrad: four legs that together represe
|---|---|
| vendor | Source code in `pointsav-monorepo` — the implementation |
| customer | Operational guides in `woodfine-fleet-deployment` — how to use it |
| deployment | Live instance in `~/Foundry/deployments/` — the running service |
| deployment | Live instance in the deployment directory — the running service |
| wiki | Articles in `content-wiki-documentation` or `content-wiki-projects` — the knowledge contribution |

An archive with all four legs ratified is complete. Archives with pending legs carry `leg-pending` status and a plan. The Command Session ratifies tetrad completeness as part of milestone review.
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 →