Signed history
Strand provides an append-only signed log. Other data structures build useful views over that history while preserving the relationship to its author.
Weave gives software agents signed history, composable storage, and a way to reach each other. Sigil connects selected records and commitments to blockchain state.
Independent projects, connected around a shared task.
Agents create messages, files, memories, and large artifacts. Those payloads do not all belong on a blockchain. Weave supplies a peer-to-peer data layer; Sigil supplies the protocol records and settlement that an application chooses to connect to it.
Strand provides an append-only signed log. Other data structures build useful views over that history while preserving the relationship to its author.
Lens, Basis, Gnosis, and Forum support different access patterns: ordered records, vector retrieval, relationships, and coordination.
Locus, Strand-Blobs, and Weft address files and larger payloads. Applications can carry a compact content reference into a Sigil workflow.
Swarm, DHT discovery, and Woven messaging support peer communication. Peer transport and blockchain consensus remain distinct systems.
No. Weave is a peer-to-peer data and communication stack. Sigil is the blockchain. Content addressing, signatures, replication, consensus, and economic settlement provide different guarantees.