Every part
has a job.

Identity creation/import, personas, credentials, family relationships, signing permissions and identity backup. Its documented interfaces include NIP-46 remote signing and Android NIP-55. The app can hold identity keys in software.

The protocol library, distinct from the My Signet application. Its local manifest declares range-proof, ring-sig, shamir-words, nostr-attestations, nsec-tree and spoken-token.

Authentication and signer-access SDK. The inspected SDK checkout declares signet-verify. A dependency declaration does not prove that every login option is enabled by the consuming app.

Verification and cross-device sign-in; credential publishing and validation. signet-verify is declared by the inspected signet-login checkout and is a development dependency in My Signet. Direct use of signet-credentials by the inspected Vennel clients was not established.

Purpose-separated identity derivation and verifiable succession. My Signet and the succession library declare nsec-tree. Complete client identity migration is a separate unfinished integration.

Holds identity keys on hardware and enforces signing policy. An alternative to software-held keys; it is not a mandatory second signer for every My Signet user.

Bark exposes NIP-07 to browser apps and forwards over NIP-46. Cambium exposes NIP-55 on Android and forwards to Heartwood. Neither holds the user's identity key itself.

Manages Heartwood identities, policies and recovery. Its current README calls the complete new recovery-word hardware ceremony untested alpha. Management tools do not establish a proven hardware restore.

Conversations, contacts and lane labels. The web manifest declares signet-login, nostr-contact-card, nostr-deaddrop and spoken-token. Android build configuration requires the native Link bridge.

Signed contact-card information and spoken verification tokens. Both are declared by KithMoot; spoken-token is also declared by My Signet, Signet and kenspeckle.

Quiet-message counters, padding and scheduling primitives. Dependency presence does not close box-owned cadence activation or physical-device acceptance.

Circle infrastructure for keeper storage, scoped admission and delivery. Its Rust workspace declares shelter-kit and Link components.

Bothy declares link-core, link-endpoint and link-blossom. Android packages Link's native bridge. The workspace's link-relay crate is documented development-only; it does not establish that every box runs a Link relay.

Signed encrypted context collections and supporting cache, CLI and MCP tooling. Additional product dependencies beyond the core Vennel messaging rules, not another network carrier.

Carrier technologies used by the design. They are not ForgeSworn libraries. Connection probes, box scheduling and completed message delivery have separate evidence.

Bonds, invitations and relationship tiers. Its manifest declares tessera-kit, nostr-attestations and spoken-token.

Presence and membership-filter machinery. Directly declared by My Signet and kenspeckle; this does not prove every proposed Vennel discovery journey.

Signed attestation event handling, declared by Signet and kenspeckle. Supports bond and verification mechanisms.

Parent-held policy and authority for the intended family mode. Complete Vennel kin-mode integration remains open.

Value-in-range proofs, declared by Signet. Age-range proof is a family-mode mechanism; the proposed mint-solvency use is separate work.

Anonymous corroboration and ring signatures. nostr-veil, nostr-anon-vote, Signet and epoch-seal declare ring-sig. Proposed anonymous trust and flood controls are not blanket anonymity guarantees.

Composes dominion-protocol, nostr-anon-vote and ring-sig for sealed history and witnessed recovery. Signer-backed Bothy integration remains open.

Encrypted access and recovery-share machinery. Its manifest declares shamir-core. Dominion is the project; dominion-protocol is the package name.

Threshold splitting and reconstruction, with human-readable shares in shamir-words. My Signet and Signet declare shamir-words; shamir-words and Dominion declare shamir-core.

Anonymous ballots for recovery refusal, using ring-sig. This does not make the surrounding recovery process invisible.

Duress and verification components. Its manifest declares shamir-words, nsec-tree and spoken-token. Complete signer/box duress integration remains open.

Encrypted content-addressed file delivery. Wildbloom Node's manifest uses the shelter-kit package under the local name wildbloom-core.

Shared storage and serving machinery for box/file infrastructure. This is a Rust crate, not an omitted npm dependency.

Vennel's bounded outer-envelope codec has Rust hostile-input tests and Android/WebAssembly build evidence. It has no cryptographic dependency, manages no MLS groups and is not consumed by KithMoot or Bothy yet.

MLS is the intended sheltered-lane message-key protection. OpenMLS 0.9.0 is a compile-proven candidate, not an adopted dependency. Group state, KeyPackages, Welcome delivery, replay handling and client integration remain open.

Encrypted archive export/restore, bounded private history import, encrypted local search and box-first deletion with recorded outcomes. These are product implementation paths, not extra standalone ForgeSworn libraries. Release and fresh-box/two-phone acceptance remain separate.

Bothy and Android implement bounded authenticated ID comparison, with Link-only Android transport and strict limits. The primitives do not fetch or retain messages and do not establish automatic replication. Browser Link transport and physical acceptance remain open.

Bearer-note machinery across language implementations. Notes remain claims on a mint, including when the circle operates it.

Mint and wallet roles in the wider stack. Their inclusion in the toolbox does not establish an integrated private payment journey inside Vennel.

Hold-invoice escrow for circle trades and proposed range proofs for mint solvency. BOLT12 offers in wraps and threshold circle mints remain unfinished integrations.

Meeting-point and location tooling for in-person introductions. rendezvous-kit declares geohash-kit; adoption in the Vennel client journey was not established.

Proposed relay classification and publishing support. The manifest confirms the project/package alias. It is not shown as an active Vennel routing requirement.

A possible peer-assisted path. The toolbox explicitly reserves swarm work; it is not drawn as an implemented carrier.

The portfolio identifies a Rust remote-signer client. Direct use by the inspected Vennel client or box manifests was not established in this reconciliation.

Helps maintain the workshop inventory. It does not sit in the message path, hold user keys or provide a service required by Vennel.

Stash, Gopherkind, Toll/402, games and other portfolio products are not included as Vennel runtime dependencies without evidence of a consumer.