PI-SPACESHELP CORPUS · SPACES.EIBRAIN.ORG · 2026-10-18

Write.
Coordinate. Survive.

The technical product reference and interactive workbench for pi-spaces: from local tuple spaces through RequestRef claims, CompletionProfiles, overlay gate (Layer A/B), and HRW federation to the 6-stage Multiplayer Space-Chat and mobile control.

01

Canonical Model

Locally atomic. Federatedly journaled.

PI-SPACES EXECUTION FLOWSINGLE-HOST VS. FEDERATED CLUSTER
LOCALV1–V3 SINGLE SPACE
  1. 01 Input & ClaimEntry + RequestRefTemplate match, lease & RFC-8785 hash
  2. 02 Atomic CommitTxn + CompletionProfileMutation, claim, rev & budget in 1 commit
  3. 03 Reactive StreamreadPage / changes / MailboxConsistent snapshots & prefix ACK
CLUSTERV4–V6 FEDERATED
  1. 01 Zero-Trust GateLayer A/B + 60s GrantNetBird peer + Ed25519 challenge
  2. 02 Router & ShardingHRW Policy & JournalPartitioned journals & takeWaiting
  3. 03 Operations ControlRunGate & AdminSpacesControl via smartphone & web admin
PiSpaces and RemoteSpace share the exact same SpaceLike contract. Application concepts transfer between local and remote clients; federation needs its own request/routing adapter.
02

Clear Content Model

Nine systems. One canonical order.

01SYSTEM · CANONICAL

Technical system map for tuple spaces, the 6 architecture layers, the data and consistency model, and binding guarantees and boundaries.

02SYSTEM · CANONICAL

Pure state machine, document version 5, global IDs (gid), subtypes, wildcard templates, leases, transactions, CompletionProfiles, and byte budgets.

03SYSTEM · CANONICAL

Idempotent request claims (RequestRef + generation), RFC-8785 argument hashes, byte-bounded snapshot pages (readPage), revision streams (changes), and consumer mailboxes (events/ack).

04SYSTEM · CANONICAL

Local client PiSpaces, named spaces (NamedSpace/Registry), reaper and event delivery (startService), plus the 8 replay-safe LLM agent tools.

05SYSTEM · CANONICAL

Transport-independent SpaceService, role policy, RemoteSpace over Unix socket, TCP, and pi-serverd, plus safe resolution of OutcomeUnknown.

06SYSTEM · CANONICAL

Two-layer security (Layer A NetBird peer, Layer B Ed25519/P-256 challenge), token/QR enrollment, 60s grants, key rotation, boot guard, and restore.

07SYSTEM · CANONICAL

RouterController with journal partitions, signed RouterLease and delegation, FederationPolicy (HRW/expand), FederatedSpace, waiter race, membership, and principal erasure.

08SYSTEM · CANONICAL

RunGate & RunController, WorkerSupervisor, space lifecycle, control via mobile app (pi-termux-mobile) & web admin (AdminSpaces), plus Phase 3 replication.

09REFERENCE · CANONICAL

Hands-on guide from a local zero-setup space (v1) to a federated cluster with mobile/web admin (v6) using the Multiplayer Space-Chat, plus the faceted API & Tool Finder.

03

Source-Owned Corpus

Contract, code, and live evidence united.

DE / EN100% anchor parity & offline index