Careful interpretation
Why association does not establish causation
Public records can document identities, formal roles, sponsorship, and subject overlap. None of those facts alone proves that one actor caused another record, action, decision, or outcome.
Reviewed Sep 5, 2026 · Examples cover Q1–Q2 2026 lobbying records and 119th Congress legislative records
Four records, four different meanings
- Sponsorship: Congress.gov lists Mike Rogers as sponsor of H.R. 3838; it does not explain another entity's conduct.
- Filing-subject overlap: reviewed Boeing filings explicitly reference H.R. 3838 or its subject; that supports bill context, not proof of contact, support, opposition, or effect.
- Committee responsibility: an official House page lists Rogers as Armed Services chairman; responsibility does not show that a specific filer contacted him.
- Award-recipient identity: an official award record can identify Boeing as recipient; it does not show that lobbying or legislation caused the award.
How to read this on a profile
- Name the exact documented relationship before drawing any conclusion.
- Keep lobbying, legislation, political finance, and federal awards in their labeled modules.
- Read the evidence class: documented fact, site calculation, verified relationship, or contextual association.
- Check the time period and identity basis.
- Read the public limitation as part of the record, not a footnote to ignore.
Visitor checklist
- Which official record supports the connection?
- Does it document identity, role, sponsorship, subject overlap, or something else?
- Are the periods actually comparable?
- Is there direct evidence of contact or action?
- What alternative explanations remain?
- Would a causal statement go beyond the record?
When the answer is insufficient evidence
If the reviewed packet does not document the claimed relationship or causal step, the correct result is insufficient evidence. Missing context is not proof of absence, and nearby timing is not a substitute for a source.