Diff: architecture/architecture.es
From 7cd8e3e to 7cd8e3e
+0 / −0 lines
| Before | After |
|---|---|
| --- | --- |
| schema: foundry-doc-v1 | schema: foundry-doc-v1 |
| title: "Platform architecture overview" | title: "Platform architecture overview" |
| slug: architecture | slug: architecture |
| short_description: "The platform is designed around distributed cryptographic consistency and sovereign bootability, with the capability to collapse a federated archive into a self-contained bootable image transferable across environments." | short_description: "The platform is designed around distributed cryptographic consistency and sovereign bootability, with the capability to collapse a federated archive into a self-contained bootable image transferable across environments." |
| category: architecture | category: architecture |
| type: topic | type: topic |
| quality: complete | quality: complete |
| status: active | status: active |
| bcsc_class: public-disclosure-safe | bcsc_class: public-disclosure-safe |
| last_edited: 2026-05-09 | last_edited: 2026-05-09 |
| editor: pointsav-engineering | editor: pointsav-engineering |
| paired_with: architecture.es.md | paired_with: architecture.es.md |
| --- | --- |
| The PointSav platform is designed around two structural properties: distributed cryptographic consistency and sovereign bootability. Both properties are preserved across cloud and offline-vault environments simultaneously. | The PointSav platform is designed around two structural properties: distributed cryptographic consistency and sovereign bootability. Both properties are preserved across cloud and offline-vault environments simultaneously. |
| ## Distributed cryptographic state | ## Distributed cryptographic state |
| A single archive can exist across multiple physical environments — an active cloud node and an offline vault — while maintaining a single, unified cryptographic state. The two environments share an identical root Merkle hash at all times. | A single archive can exist across multiple physical environments — an active cloud node and an offline vault — while maintaining a single, unified cryptographic state. The two environments share an identical root Merkle hash at all times. |
| - **Active cloud node** — the live, networked copy of the archive. | - **Active cloud node** — the live, networked copy of the archive. |
| - **Offline vault** — a physically isolated copy that mirrors the cloud node's Merkle root without a persistent network connection. | - **Offline vault** — a physically isolated copy that mirrors the cloud node's Merkle root without a persistent network connection. |
| This shared-root property means an auditor can verify the integrity of either copy against the same hash without needing both to be online simultaneously. | This shared-root property means an auditor can verify the integrity of either copy against the same hash without needing both to be online simultaneously. |
| ## Archive collapse and portability | ## Archive collapse and portability |
| When an operator issues the collapse command, the platform compresses the federated cloud index and the offline physical copy into a single transferable entity. The result is a self-executing bootable image (`.ISO` or `.IMG` format). | When an operator issues the collapse command, the platform compresses the federated cloud index and the offline physical copy into a single transferable entity. The result is a self-executing bootable image (`.ISO` or `.IMG` format). |
| The collapse operation is explicit and operator-initiated. It is not automatic and does not run on a schedule. | The collapse operation is explicit and operator-initiated. It is not automatic and does not run on a schedule. |
| ## Sovereign bootable image | ## Sovereign bootable image |
| The resulting image is a self-contained operating environment. It can be deployed on bare-metal hardware or imported into a commercial cloud environment. The image carries the full archive state, making it possible to reconstitute the system on new hardware without reconstructing data from a remote source. | The resulting image is a self-contained operating environment. It can be deployed on bare-metal hardware or imported into a commercial cloud environment. The image carries the full archive state, making it possible to reconstitute the system on new hardware without reconstructing data from a remote source. |
| This property is intended to guarantee operational continuity when a primary deployment environment becomes unavailable. | This property is intended to guarantee operational continuity when a primary deployment environment becomes unavailable. |
| ## See also | ## See also |
| - [[worm-ledger-architecture]] — WORM ledger design that underpins archive integrity | - [[worm-ledger-architecture]] — WORM ledger design that underpins archive integrity |
| - [[compounding-substrate]] — how structural properties compound across deployments | - [[compounding-substrate]] — how structural properties compound across deployments |
| - [[customer-hostability]] — the design properties that allow a customer to host the full stack | - [[customer-hostability]] — the design properties that allow a customer to host the full stack |