How It's Built

• Architecture Overview — PointSav Platform

  A map of the PointSav platform's major architectural surfaces: compute substrate, software distribution, GIS intelligence, and the editorial pipeline.

• Co-location methodology

  A structured approach for ranking hardware co-location candidates across jurisdictional, network, infrastructure, and cost dimensions, constrained first by regulatory requirements before other optimization occurs.

• Crypto Payment and License Issuance Architecture

  The payment and license architecture behind software.pointsav.com — a custodian-free flow from on-chain USDC transfer to Ed25519-signed download token, with no customer accounts and no payment intermediary.

• Customer hostability

  Customer hostability is the architectural commitment that every PointSav artefact can run on the customer's own hardware, against the customer's own keys, with the customer's own audit ledger — making self-hosted deployment the canonical pattern, not a tier.

• DataGraph Federation: From app-orchestration-slm to app-orchestration-graph

  How the PointSav platform federates sovereign per-archive DataGraphs through a single auditable gateway, and the conditions under which that gateway transitions to a dedicated service.

• Direct-payment settlement

  Payment for marketplace transactions is planned to flow directly from buyer to the customer-tenant; PointSav's share is a transaction fee at settlement, not a recurring subscription.

• Economic model — community and SMB customer tiers

  PointSav's two-tier commercial structure: a free Community tier that serves as an adoption funnel, and a paid SMB Customer tier targeting regulated small-to-medium businesses that hyperscale billing models cannot serve economically.

• Editorial draft routing protocol

  Metadata classification layer that routes editorial drafts by their language_protocol declaration — which gateway processes an artifact and which vocabulary rules apply.

• Leapfrog 2030 architecture

  Structural positioning thesis pairing customer-owned hardware, data, and adapter weights with transactional rather than subscription revenue.

• Mailbox atomicity — flock-based prepend and msg-id idempotency

  flock-guarded prepend and msg-id idempotency for flat-file mailboxes — how concurrent sessions serialize writes instead of silently losing messages.

• Multi-engine session coordination — session locks, boot_id, and role guards

  Session-lock protocol for concurrent AI engines on one host — boot_id staleness detection and role locks that keep two sessions off the same .git/index.

• os-infrastructure and os-network-admin: Distribution Model

  Two products are planned/intended for software.pointsav.com: os-infrastructure ($19 USDC, bare metal or cloud VM) and os-network-admin ($1 USDC, mesh control plane including Linux daemon mode). Each ships as three signed artifacts per version.

• Per-user build cache discipline — preventing cross-user Cargo races

  Per-user partitioning of the shared Cargo build cache — why a per-developer CARGO_TARGET_DIR eliminates cross-user lock races and permission errors.

• Platform architecture overview

  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.

• PointSav architecture 2030 — an overview

  A faithful public summary of the PointSav constitutional charter — six pillars, fifty-two structural claims, eight cross-industry inventions, a three-tier compute model, three-ring service architecture, and the economic model that sustains it.

• PointSav platform — architectural overview

  Constitutional charter encoding six foundational commitments and fifty-four numbered structural claims that govern every PointSav engineering decision.

• PointSav Software Distribution Substrate

  A three-component system — release server, storefront, and payment watcher — that delivers compiled binaries against on-chain USDC payments, with no customer accounts and no subscription billing.

• PointSav — company overview and three-organisation structure

  PointSav Digital Systems is a technology vendor that builds sovereign, on-premise-capable operating systems for record-keeping and business administration. It sits within a three-organisation structure established by Woodfine Capital Projects Inc.

• Regional market definition

  Spatial containers on the location intelligence map — how settlements with co-location presence differ from Regional Markets, and why coverage is not market strength.

• Scaling Coordinated Development Across Many Totebox Archives

  The app-orchestration-command topology is designed to grow. This article describes the coordination challenges that appear as the number of Totebox Archives increases, the mechanisms introduced to address them, and the planned trajectory toward per-archive process isolation.

• Six-tier sovereignty matrix

  Six fixed directory prefixes organising the PointSav monorepo by purpose, making the repository self-documenting and enforcing dependency hygiene by convention.

• Three-binary architecture: os-console, os-totebox, os-orchestration

  Totebox Orchestration is delivered through three distinct binary operating environments — os-console, os-totebox, and os-orchestration — each with a distinct role, deployment target, and hosted application set.

• Three-layer architecture

  Strict one-way flow of PointSav deliverables through three layers — vendor monorepo, customer showcase catalogue, and private running instances.

• Three-layer stack

  The Three-Layer Stack is the infrastructure decomposition pattern used across PointSav deployments, separating raw computing capability, isolated platform execution, and secure operator access into three distinct layers.

• Three-ring architecture

  The durable composition pattern for the PointSav platform: three concentric rings with strict one-way dependencies, where the AI ring is structurally optional and the deterministic data pipeline operates fully without it.

• Totebox orchestration as the development environment

  PointSav's development environment is itself deployed as a Totebox Orchestration instance — the workspace that builds the platform runs on the same architecture the platform delivers to customers.

• Totebox session

  A Totebox Session is an AI-assisted contributor session opened within a single Totebox Archive — scoped to the archive's declared repositories, unable to write outside them, and the standard entry point for all development work in Totebox Orchestration.

• Vertical seed packs marketplace

  PointSav intends to distribute curated industry-specific seed packs as starter taxonomies, enabling tenants to contribute refinements back through a planned marketplace.

• Workspace services slice — cgroup partitioning for multi-developer environments

  systemd cgroup partitioning that gives production services twice the CPU weight of interactive build sessions — single-node isolation without Kubernetes.