Infrastructure

Infrastructure articles sit at the boundary between the abstract platform architecture and the concrete machines, services, and network paths that constitute a live deployment. This category covers storage substrate design, fleet topology, edge deployment patterns, key management operations, and the telemetry and mesh network that connect a fleet.

Storage substrate

The foundational persistence layer — the WORM ledger and the audit surface it provides.

• WORM ledger design — The four-layer Write-Once-Read-Many ledger: tile-based, hash-chained, cryptographically signed; satisfies SEC 17a-4(f), eIDAS, and SOC 2 by structure rather than policy.
• WORM ledger substrate: four-layer architecture and two boot envelopes — Architectural layout of the WORM ledger across Ring 1 services.
• WORM ledger storage architecture — Physical storage organisation for WORM ledger deployments.
• Immutable storage and secure backup — Storage topology and block-device configuration for PointSav deployments.
• Data vault bookkeeping substrate — An SMB bookkeeping architecture built on an immutable source vault and append-only journal, with structural separation between the bookkeeping record and any accounting tool.

Fleet and edge deployment

How a deployment is provisioned, updated, and maintained across on-premises and cloud hardware.

• Edge deployment and boundary ingest — Edge deployment patterns for PointSav instances operating at the network edge or in low-connectivity environments.
• Tier C key wiring — The operational procedure for managing external API keys in the Doorman service: where keys live, how they rotate, and how a breach is contained.

Network and telemetry

How fleet nodes communicate and how observability signals are collected without centralising identifiable data.

• Sovereign mesh — The WireGuard-based peer-to-peer mesh network that connects PointSav fleet nodes without a central routing authority.
• Zero-state telemetry architecture — Zero-state telemetry: the V4 Intent Beacon collects behavioural and hardware signals from edge clients without cookies, session identifiers, or third-party analytics.
• Telemetry architecture — Architecture of the telemetry pipeline across PointSav deployments.

See also

• Architecture — cross-cutting platform architecture and the three-ring model
• Systems — the operating systems that run on this infrastructure
• Services — the services that depend on the storage and network substrate