Purpose
Facade over filesystem, network, storage, identity, crypto, and model crates. This page follows the real source shape for Weave Core and explains the workflow a developer is likely to use first.Network contract
Document peer identity, topic selection, message framing, session lifetime, retry behavior, metrics, and what must be stable between releases. Any change here can strand peers, so examples should be exercised with at least two real processes.Primary types to know
AgentFs— libs/weave-core/src/filesystem/agentfs.rsAgentFsConfig— libs/weave-core/src/filesystem/agentfs.rsAgentFsEntry— libs/weave-core/src/filesystem/agentfs.rsContentAnnouncement— libs/weave-core/src/network/dht.rsDht— libs/weave-core/src/network/dht.rsDhtBehaviour— libs/weave-core/src/network/dht.rsDhtConfig— libs/weave-core/src/network/dht.rsDhtStats— libs/weave-core/src/network/dht.rsDid— libs/weave-core/src/identity/mod.rsDiff— libs/weave-core/src/filesystem/diff.rsDiffEntry— libs/weave-core/src/filesystem/diff.rsDiffSummary— libs/weave-core/src/filesystem/diff.rs
Example shape
Release-quality documentation checklist
- Every public type on the API Surface page has at least one sentence of behavior documentation.
- Every fallible operation lists errors and recovery guidance.
- Every networked example names the peer/session/topic lifecycle.
- Every storage example names durability, repair, and deletion semantics.