Skip to content
PointSav Digital Systems

Totebox session

← All revisions

61ed7fe2 · PointSav Digital Systems ·

content(quality-pass): institution POV elevation — 97 articles updated, 32 new from drafts-outbound

View the full record as of this revision →

@@ -8,7 +8,7 @@ quality: complete
short_description: "A Totebox Session is an AI-assisted contributor session opened within a single Totebox Archive — scoped to the archive's declared repositories, unable to write outside them, and the standard entry point for all development work in Totebox Orchestration."
status: active
bcsc_class: forward-looking
last_edited: 2026-05-08
last_edited: 2026-05-25
editor: pointsav-engineering
paired_with: totebox-session.es.md
---
@@ -19,7 +19,7 @@ This article describes how a session is opened, what it can and cannot do, the f

## How to open a session

The intended entry point is `bin/open-archive.sh <archive-name>`, planned for invocation from the Command Session. When invoked, it is intended to:
The intended entry point is the `open-archive` console command, planned for invocation from the hub session. When invoked, it is intended to:

1. Read the archive manifest at `clones/<archive>/.agent/manifest.md`
2. Print the archive name, tetrad status, AI gateway endpoint, and count of pending inbox messages
@@ -36,14 +36,14 @@ A Totebox Session:
- Writes to any repository declared in the archive's manifest
- Commits to the archive's staging branch (never directly to the canonical `main`)
- Routes inference through the shared `service-slm` access-control gateway using the archive's module identifier
- Sends cross-archive requests as messages to the Command Session (never writes to other archives)
- Sends cross-archive requests as messages to the hub session (never writes to other archives)
- Stages wiki drafts in `.agent/drafts-outbound/` for the editorial pipeline

A Totebox Session does not:

- Write workspace files (`CLAUDE.md`, `AGENT.md`, `bin/`, `pairings.yaml`)
- Write workspace-level configuration or tool files
- Write to the identity store
- Access the canonical `vendor/` or `customer/` trees directly (those receive content by promotion, not direct write)
- Access the canonical source trees directly (those receive content by promotion, not direct write)
- Open connections to sibling archive sessions

## The Project Tetrad
@@ -57,7 +57,7 @@ Every Totebox Archive declares four legs of the Project Tetrad. A session's work
| deployment | Provisioning the running instance in the deployment directory |
| wiki | TOPIC draft files staged in `.agent/drafts-outbound/` |

The Command Session ratifies tetrad completeness when all four legs are present.
The hub session ratifies tetrad completeness when all four legs are present.

## The AI session coordination protocol

@@ -65,8 +65,8 @@ Sessions communicate through the inbox-and-outbox file protocol:

- Each archive holds `.agent/inbox.md` and `.agent/outbox.md` files
- A Totebox Session reads its inbox at session start and archives actioned messages
- Outbound requests to other archives or to the Command Session are prepended to `.agent/outbox.md` (newest on top)
- The Command Session sweeps cluster outboxes during workspace review and routes messages
- Outbound requests to other archives or to the hub session are prepended to `.agent/outbox.md` (newest on top)
- The hub session sweeps archive outboxes during workspace review and routes messages

In the planned next phase, `app-orchestration-command` (CommandCentre) is intended to broker all cross-archive messages by HTTP, with each message transiting the access-control gateway and the immutable ledger automatically. The file-based protocol is intended to remain as the fallback and the development-mode mechanism.

@@ -85,7 +85,7 @@ Tiers are enforced by pairings, not string comparisons. A P3 contributor's `os-c

## Relationship to os-console

`os-console` is the customer-facing entry point for opening a Totebox Archive. In the workspace, `bin/open-archive.sh` is the equivalent. Both are intended to perform the same function: read the archive manifest, validate the contributor's permission scope, set the session context, and open a working session inside the archive. The development environment uses the same pattern the customer is intended to use.
`os-console` is the customer-facing entry point for opening a Totebox Archive. In the development workspace, the `open-archive` command is the equivalent. Both are intended to perform the same function: read the archive manifest, validate the contributor's permission scope, set the session context, and open a working session inside the archive. The development environment uses the same pattern the customer is intended to use.

## See also
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 →