build-attribution-tracelisted

# /build-attribution-trace — Lead-to-Revenue Attribution Trace > **Purpose.** Build the cleanest attribution trace possible from available LinkedIn + CRM signals. Multi-touch, dark-social-aware, confidence-scored. Used in monthly client reports, used in `/pipeline-pulse` to identify channel weight, used to defend the engagement against "what's actually working" pushback. > > **Bar.** LinkedIn attribution is structurally messy (multi-touch, dark social, content-influenced-but-not-clicked). The trace must be honest about uncertainty — confidence-scored, not bulldozed into a single number that overstates clarity. ## When to invoke - Monthly per active client (called by `/build-client-report`) - Quarterly for the agency itself (called by `/pipeline-pulse` Layer 2 channel attribution) - Ad-hoc when operator or client asks "where did this lead come from" - Before renewal conversations (3-month rolling trace) ## Required inputs 1. `scope` declared (single-client OR agency-self) 2. Source data inventory — at minimum: - LinkedIn analytics (post impressions, engagements, profile clicks, follower growth) - CRM data (every contact in the funnel for the period — source field, touchpoint history) - Calendar data (booked calls + held calls + outcomes) - DM thread metadata (per `/classify-dm-intent` outputs) 3. Optional: Shield/Taplio analytics export, UTM-tagged link tracking, CMS dark-social signals 4. Period (default: previous calendar month; quarterly for renewal/pipelin