Skip to content

Diff: systems/totebox-archive

From 61ed7fe to 61ed7fe

+13 / −14 lines
BeforeAfter
--- ---
schema: foundry-doc-v1 schema: foundry-doc-v1
title: "Totebox archive" title: "Totebox archive"
slug: totebox-archive slug: totebox-archive
category: systems category: systems
type: topic type: topic
quality: complete quality: complete
short_description: "A Totebox Archive is a self-contained, freely transferable micro-virtual machine that persists institutional data as immutable flat files." short_description: "A Totebox Archive is a self-contained, freely transferable micro-virtual machine that persists institutional data as immutable flat files."
status: active status: active
bcsc_class: public-disclosure-safe bcsc_class: public-disclosure-safe
last_edited: 2026-05-04 last_edited: 2026-05-25
editor: pointsav-engineering editor: pointsav-engineering
cites: [] cites: []
--- ---
A Totebox Archive is the fundamental unit of data storage and sovereignty within the PointSav platform — a self-contained micro-virtual machine that persists institutional records as immutable flat files and can be physically transferred between cloud providers, private servers, or bare-metal hardware without losing its cryptographic integrity. Each archive is cryptographically anchored to a Write-Once-Read-Many (WORM) ledger, creating a permanent and verifiable audit trail for every transaction and state change.
A **Totebox Archive** is the fundamental unit of data storage and sovereignty within the PointSav platform. It operates as a **Micro Virtual Machine** that provides self-contained services for specific institutional assets. ## Immutable data layer
## Immutable Data Layer Unlike traditional databases that require active processes to access data, a Totebox Archive persists information as immutable flat files — JSONL, GeoParquet, and Markdown — so the data remains accessible and readable even if the original software engine is no longer running. No proprietary runtime is required to read the records decades later.
Unlike traditional databases that require active processes to access data, a Totebox Archive persists information as **immutable flat files** (JSONL, GeoParquet, Markdown). This decoupling ensures that the data remains accessible and readable even if the original software engine is no longer running. ## Freely transferable design
Each archive is cryptographically anchored to a WORM ledger, creating a permanent, verifiable Audit trail for all transactions and state changes.
## Freely Transferable System
A key architectural requirement of the PointSav system is that data must be an asset, not a liability. A Totebox Archive is designed to be **Freely Transferable**. It is packaged as a **Bootable Disk Image** that can be moved between physical servers, private clouds, or bare metal resources without losing its integrity or historical context. A Totebox Archive is packaged as a bootable disk image that can be moved between physical servers, private clouds, or bare-metal hardware without losing integrity or historical context. The operator picks up the image and moves it; there is no host operating system underneath that holds the keys.
## Asset Specialization ## Asset specialization
Totebox Archives are typically deployed as specialized containers for distinct institutional domains. Common archive types include: Totebox Archives are typically deployed as domain-specific containers for distinct institutional assets. Common archive types include:
* **Totebox Archive - Personnel:** Encrypted records and identification. | Archive type | Contents |
* **Totebox Archive - Corporate:** Tax identification, formation documents, and minutes. |---|---|
* **Totebox Archive - Property:** Land titles, zoning records, and construction ledgers. | Personnel | Encrypted records and identification |
| Corporate | Tax identification, formation documents, and minutes |
| Property | Land titles, zoning records, and construction ledgers |
## See also ## See also
- [[totebox-os]] - [[totebox-os]]
- [[totebox-orchestration]] - [[totebox-orchestration]]
- [[infrastructure-os]] - [[infrastructure-os]]
- site-ledger-integration - site-ledger-integration