attribution-architecturelisted

# Attribution Architecture Define the claim types once, apply them everywhere, and pick the window before you see the results. ## When to use - Marketing and sales report different numbers for the same quarter - Channel budget decisions need a defensible basis - Before a campaign, to set the measurement - Board reporting is coming and the numbers need to survive questions ## Inputs - Reads: `workspace/data/object-model.md`, `workspace/reports/metrics-dictionary.csv` - Needs from user: the current reporting setup, the source fields and how they get populated, and the two conflicting reports if they exist ## Workflow ### 1. Define the three claim types, and only these three **Sourced.** The first identifiable interaction that created the record, or the first for an account with no prior activity. One owner. No splitting, no percentages. **Influenced.** Any meaningful interaction with any buying-committee member inside the opportunity window. Multiple owners allowed by design. **Accelerated.** Stage velocity above the segment baseline where a specific program touched the account. The hardest to claim and the most credible when you can. ### 2. Enforce the four rules that keep it honest **Never sum sourced and influenced against the same target.** Influenced revenue double counts by design, everyone knows it, and reporting a combined total destroys the credibility of every other number on the slide. **Pick the window before the campaign.** A window chosen after seeing r