Connect authorized nodes and place workspace copies with chosen providers.
A workspace can be served and stored across participating nodes. Its owner chooses the relevant hosts and custody arrangements. Separate the authority to process knowledge from the responsibility to retain encrypted copies.
A network connection does not grant workspace membership.
Replication maintains selected copies of workspace state across locations. Placement policy determines where copies belong and the redundancy required.
Policy-driven replication separates query-serving Host replicas from encrypted block copies held by custodians.
For example, a company can use its own host and retain encrypted copies with independent storage providers. Inspect the actual replica state rather than assuming that a requested copy already exists.
After disruption, peers reconcile the state they are authorized to exchange. Which operations remain available during disconnection depends on the deployment and its policies.
Use native Story calls to invoke executable actions over the QUIC network. Workspace-aware routing resolves serving peers and explains direct, NAT-traversed and encrypted relay paths.
High availability explains continuity through failures. Backup and restore addresses recovery from a preserved archive. A live replica and a backup serve different purposes.
Developer reference
Nodes communicate over authenticated QUIC (RFC 9000) with TLS 1.3 security. Cryptographic peer identity, discovery results and workspace authorization remain separate inputs.
Hosts execute queries; custodians retain encrypted blocks. Replication transfers authorized committed state and required content. A placement requirement is desired state; observed holdings establish which blocks a peer actually has. One cached block does not certify a complete replica.
Reconcile branch state and missing content under explicit authority and failure policy. Transport recovery cannot resolve semantic conflicts between concurrent writes. Partition behavior, disconnected execution and failover guarantees belong to the deployment contract.