# LinkedIn Send Actions — Worker Execution Wiring

## Purpose
Define the worker-side execution paths for approved LinkedIn send actions.

## Action Types
1. `send_connection_note`
   - Preconditions:
     - Record strategy = `Connect First`
     - Braden approval captured in Telegram relay / record payload
     - Draft asset exists and is approved
   - Execution target:
     - LinkedIn connection request note send path
   - Verification:
     - connection request sent successfully
     - record status updated to `Outreach Sent`

2. `send_recruiter_reply`
   - Preconditions:
     - Record strategy = `Recruiter Response`
     - Braden approval captured
     - Approved reply draft exists
   - Execution target:
     - email/InMail reply path depending on source
   - Verification:
     - reply sent successfully
     - record status updated to `Outreach Sent`

## Approval Gate
No send action executes without explicit approval captured in Telegram/record context.

## Record Update Contract
On successful send:
- Status -> `Outreach Sent`
- Last Updated -> send date
- Research Payload / Draft Assets append send metadata
- Follow-up timer becomes eligible