Editorial policy & corrections
Last updated: November 12, 2026
Bull & Gavel is a free news publication from ClearVoyant LLC that reports on public financial-disclosure filings. This page
says how we work, what our data does and does not cover, and how to get something corrected or removed.
It supplements the methodology.
What we publish
- Our ledger. The disclosed trades we have ingested from periodic transaction reports posted by the House Clerk, the Senate eFD system and the U.S. Office of Government Ethics. It is a record of what we could read, not a complete list of everyone who must file. Scanned filings we cannot read, amended filings, filings disclosed many days after the trade, and filings we have not yet ingested may be missing.
- Context. Public policy actions (Federal Register, agency feeds), SEC Form 4 and 8-K filings, committee assignments, lobbying and contract records, shown beside the ledger (posts on X may also cite 10-K and 10-Q filings and list committees with an "as of" date). Showing two public facts side by side is not a claim that one caused the other or that anyone acted on non-public information.
- Analysis. Our own measurements (for example returns versus SPY from the disclosure date) and AI-assisted summaries, labelled as such.
How we label things
- Who traded. A filer's report can include accounts held by a spouse, jointly, or by a dependent child. Where the filing says so we show Spouse, Joint, or Dependent child. When it does not specify an owner, we show Not specified. Self appears only when the filing uses an explicit self code. We do not present someone else's account as the filer's own decision.
- How much. Filings give value ranges. We show the range as filed. Single dollar figures, where they appear, are approximations and are labelled.
- Where from. Named rows link to the official filing where we have the link. Market prices come from a third-party source and are not government records.
- AI. Software, not an AI model, parses the filings into ledger rows. Scanned filings are read with OCR, which can misread. AI-written text (briefings, reports, themes) is generated from our own data and checked by automated rules; it can still be wrong, and it is not a statement by any filer. Posts on X that name a person are drafted with AI assistance and checked by a person against the linked filing before publication.
- Neutral wording. We do not allege wrongdoing. Terms such as "committee overlap" and "convergence" describe a coincidence of public records only.
- Not advice. Nothing here is investment advice. We tested copy-trading and did not find a reliable edge (see the methodology).
Before we name a person
Anything we publish that names a person should be checked against the original filing: the filer's identity and role, the owner of the account, the transaction date, side and amount range, and the filing date. We link to the filing so you can check us.
Posts on X that name a person follow the same rules: the filing's own wording ("reported"), the range and owner as filed, the full list of the member's committees with an "as of" date, and no statement about timing, motive or wrongdoing.
Corrections, disputes and removal requests
- Email hello@bullandgavel.com with the page address and what you believe is wrong. We aim to acknowledge reports within two business days. If an X post that names a person is wrong about the person, owner, range, side or ticker, we delete it and post a correction; other errors get a correction reply.
- We verify against the original filing. Verified errors are fixed on the site first and ship with the next daily update; where an error was material we add a dated entry to the log below rather than silently editing history.
- If you are not a public official (for example a spouse, dependent child, staff member or a candidate who never held office) and you believe a page about you should be reviewed or restricted, say so in your email; we will consider requests case by case and respond in writing.
- If the filing itself is wrong, the correction has to be made by the filer with the agency; we will update our records when the agency posts an amendment.
Corrections log
Material corrections are listed here with the date, the page affected, what was wrong, and what changed.
| Date | Page | What was wrong | What changed |
|---|
| November 12, 2026 | Site-wide counts (ticker, member, leaderboard and briefing pages) | House publication was leaving out distinct transactions. The dedup step kept one row when several lines shared a member, ticker, transaction type, amount, filing date and owner, so different trade dates, notification dates and blank-ticker assets were counted once. The parser also skipped rows whose amount was a single dollar figure rather than a range. Pete Sessions' House report 20035563 has 32 transactions on the filing and the site published 30. | The House dedup step now keeps those separate lines, including identical lots listed more than once on one filing, and a single dollar figure is read as that figure. The Senate step also merged separate transactions on different dates in the same asset; 9 Senate rows return to the trade list. Counts are recomputed when this deploys. Before the change the published House set was 2,957 rows. For House stock buys and sells filed Jan 1-Nov 6, 2026 (no options), the published count was 2,586 rows across 76 members, with one member at 840 and the top four at 1,357. |