client-content-sourcing-pulselisted

# /client-content-sourcing-pulse — Weekly Content Sourcing Audit > **Purpose.** Measure whether the client is providing enough raw input (voice notes, story prompts, case-study moments, opinion-takes) for the ghostwriter to produce non-templated posts. Output is a 1-page sourcing-health brief + 3-5 specific prompts for the AM to send to the client this week. > > **Bar.** A ghostwriter without raw client input reverts to runtime defaults — and runtime defaults churn. Sourcing pulse runs weekly so the AM never asks the client "send me content ideas" generically — they ask specific prompts that backfill the next week's calendar gaps. ## When to invoke - **Cron — every Wednesday 10:00 (weekly per active client).** Per `paperclip.manifest.yaml`. Wednesday timing gives the AM 2 days to source before the next week's calendar build. - After any pillar runs out of raw material (surfaces from `/build-posting-calendar` Step 3 hook-library check) - Before monthly client report (sourcing-cadence trend is a report indicator) - Manually when client engagement drops (sourcing volume often leads disengagement signal) ## Required inputs 1. `client_slug` declared 2. Last 7 days of client-provided raw input across all channels: voice notes (Loom/Voxer/Slack), text drops (Slack/email), screenshots, transcripts, peer-conversation summaries 3. Next 7 days of calendar slots from `/build-posting-calendar` (so we know what raw material is needed) 4. Client's content_strategy subprofile — pillar m