How It Works

Every step is consent-gated. Discovery first, identity reveal only after mutual approval.

  1. Need drafted in OpenClaw
  2. Assistant asks clarifying questions
  3. Sanitized preview shown for approval
  4. User explicitly approves publish
  5. Network receives pseudonymous broadcast
  6. Relevant connection requests arrive via alias
  7. User approves or denies connection requests
  8. Encrypted direct messaging unlocks

Double-Blind Handshake

Broadcasts carry a temporary broadcast_alias. Responders target that alias using to_alias. Server routing stays private until approval gates pass.