Totebox Archive
enrich wikilinks: documentation systems body (EN+ES) batch 1
@@ -13,11 +13,11 @@ editor: pointsav-engineering 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 — 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 [[worm-ledger-design|Write-Once-Read-Many (WORM) ledger]], creating a permanent and verifiable audit trail for every transaction and state change. The [[totebox-os|`os-totebox`]] operating system is the runtime environment for a Totebox Archive. ## 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, 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. This flat-file discipline is the foundation of the [[worm-ledger-storage-architecture|WORM storage architecture]]. ## Freely transferable design @@ -25,7 +25,7 @@ A Totebox Archive is packaged as a bootable disk image that can be moved between ## Asset specialization Totebox Archives are typically deployed as domain-specific containers for distinct institutional assets. Common archive types include: Totebox Archives are typically deployed as domain-specific containers for distinct institutional assets, each managed by the [[totebox-orchestration|Totebox Orchestration]] coordination layer. Common archive types include: | Archive type | Contents | |---|---| @@ -35,7 +35,8 @@ Totebox Archives are typically deployed as domain-specific containers for distin ## See also - [[totebox-os]] - [[totebox-orchestration]] - [[infrastructure-os]] - site-ledger-integration - [[totebox-os]] — the operating system that runs inside a Totebox Archive - [[totebox-orchestration]] — the coordination layer that manages multiple archive instances - [[infrastructure-os]] — the compute substrate that hosts Totebox Archive nodes - [[worm-ledger-design]] — the append-only ledger discipline anchoring each archive - [[customer-hostability]] — why freely-transferable design is a customer-first commitment