Diff: systems/totebox-archive.es
From 4bd58eb to 4bd58eb
+0 / −0 lines
| Before | After |
|---|---|
| --- | --- |
| 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-25 | 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 [[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. | 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 | ## 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. This flat-file discipline is the foundation of the [[worm-ledger-storage-architecture|WORM storage architecture]]. | 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 | ## Freely transferable design |
| 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. | 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 domain-specific containers for distinct institutional assets, each managed by the [[totebox-orchestration|Totebox Orchestration]] coordination layer. 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 | | | Archive type | Contents | |
| |---|---| | |---|---| |
| | Personnel | Encrypted records and identification | | | Personnel | Encrypted records and identification | |
| | Corporate | Tax identification, formation documents, and minutes | | | Corporate | Tax identification, formation documents, and minutes | |
| | Property | Land titles, zoning records, and construction ledgers | | | Property | Land titles, zoning records, and construction ledgers | |
| ## See also | ## See also |
| - [[totebox-os]] — the operating system that runs inside a Totebox Archive | - [[totebox-os]] — the operating system that runs inside a Totebox Archive |
| - [[totebox-orchestration]] — the coordination layer that manages multiple archive instances | - [[totebox-orchestration]] — the coordination layer that manages multiple archive instances |
| - [[infrastructure-os]] — the compute substrate that hosts Totebox Archive nodes | - [[infrastructure-os]] — the compute substrate that hosts Totebox Archive nodes |
| - [[worm-ledger-design]] — the append-only ledger discipline anchoring each archive | - [[worm-ledger-design]] — the append-only ledger discipline anchoring each archive |
| - [[customer-hostability]] — why freely-transferable design is a customer-first commitment | - [[customer-hostability]] — why freely-transferable design is a customer-first commitment |