Architecture
How packages compose, and where integration and recovery remain explicit.
Choose a contract before a runtime
Weave combines independently versioned packages for records, projections, local files, discovery, transport and application models. The primary Cargo workspace contains 49 packages; Filament contributes a separate eight-crate workspace. Use the library catalog to identify the actual package, feature profile and source version.
The arrows describe integration boundaries. A local constructor, stored event or started listener is not evidence that all downstream behavior is enabled.
Records and projections
Strand supplies signed record and storage interfaces. Blobs handle larger payloads. Lens, Locus, Forum, Gnosis and Basis expose different data models. Their durability, batching and recovery semantics differ: for example, Basis/Forum/Gnosis constructors do not automatically rebuild their derived indexes, and Lens does not provide the documented multi-operation atomic commit once implied by its old guide.
Nexus and WOVEN expose convergence/event contracts with their own transport and policy configuration. Read a model's current guide before designing a multi-writer or restart workflow around it.
SDK and network
WeaveNode configures identity and named local stores, with network and replication controls. Strand creation is local; announcement is explicit. Auto-replication announces the ordinary registered strands and does not imply a full replication/rebuild workflow for every data model.
The messaging manager has a separate plaintext/unverified-receive limitation. Read networking, replication and the threat model.
Applications and tools
The Weave CLI, dCLI and dBrowser have different interfaces. dCLI is a headless browser/research tool; dBrowser uses a desktop/Tauri application boundary. Filament includes partially wired runtime and utility paths. Loom libraries are pre-1.0 components whose presence does not admit a runner or prove a deployed collaboration service.
Verify the composition
Start with one package-level operation, then prove the next boundary with an actual result: a signature verification, durable read, scoped authorization, remote byte transfer or restored query. Failure modes explains why a single successful constructor or build cannot cover the whole application.
