peat-protocol 0.9.0-rc.6

Peat Coordination Protocol — hierarchical capability composition over CRDTs for heterogeneous mesh networks
docs.rs failed to build peat-protocol-0.9.0-rc.6
Please check the build logs for more information.
See Builds for ideas on how to fix a failed build, or Metadata for how to configure docs.rs builds.
If you believe this is docs.rs' fault, open an issue.
Visit the last successful build: peat-protocol-0.9.0-rc.1

peat-protocol

crates.io docs.rs License: Apache-2.0

The SDK entry point for the Peat coordination protocol — hierarchical capability composition over CRDTs for heterogeneous mesh networks (phones, servers, sensors, embedded devices, AI models).

Facade

peat-protocol is the single public crate. It re-exports peat-mesh (P2P topology, QUIC/Iroh transport, Automerge CRDT sync) and peat-schema (Protobuf wire types), so downstream consumers depend on peat-protocol alone:

use peat_protocol::{peat_mesh, peat_schema};

Add the dep

[dependencies]
# During the rc window, use the exact-version pin — Cargo does not
# select pre-release versions by default with the caret form.
peat-protocol = "=0.9.0-rc.1"

# Once 0.9.0 stable is published, the normal selector works:
# peat-protocol = "0.9"

Features

Feature Default Purpose
automerge-backend yes Automerge CRDT over Iroh QUIC — the standard backend
lite-transport no UDP-based peat-lite bridge for microcontrollers
bluetooth no peat-btle BLE mesh transport
relay-n0-hosted no Opt-in to n0's hosted iroh relay pool (*.iroh.network, *.iroh-canary.iroh.link) and DNS pkarr discovery. Off by default — tactical and edge builds must not phone home through third-party infrastructure. Enable only when n0-hosted NAT traversal and global discovery are explicitly wanted. See issue #833.

How it works

Peat organizes diverse systems through three phases:

  1. Discovery — nodes find each other via mDNS, BLE advertisements, static config, or geographic clustering.
  2. Cell formation — discovered nodes compose capabilities into cells (additive, emergent, redundant, or constraint-based).
  3. Hierarchical operations — cells self-organize into zones for efficient state sharing across the mesh.

State is CRDT-based (Automerge), so the protocol operates through network partitions without a central server.

Documentation

License

Apache-2.0