guardian-verify-setup

Account verification for trusted message delivery is configured by binding your identity to a chosen channel. You start an outbound verification flow via the assistant CLI to link your Slack or Telegram account for proven identity routing.

Channel binding secures outbound messages by linking a guardian identity to a communication channel like phone, Telegram, or Slack. This ensures outgoing message delivery only occurs to verified recipients with proven identity.

To check verification status or resend a code, use the assistant channel-verification-sessions commands in your CLI. These commands manage the entire outbound verification lifecycle, including starting, resending, and checking ongoing sessions.

You can revoke an existing channel verification and rebind your identity using the assistant channel-verification-sessions commands. This CLI functionality supports rebind flows to securely update your bound phone, Telegram, or Slack channel.

Yes, channel verification requires command-line access to manage identity binding. The skill satisfies command-line control requirements by executing start, status check, and revoke actions entirely through the assistant CLI interface.