A Adam Arafat. WA-10 Congress
← Watchtower

Defense Oversight Ledger: Records Should Be Easy for Voters to Review.

This is the general defense-oversight ledger, separate from the Defense Money Record story. Public FEC and Congressional Record data can help voters understand how defense oversight, local aerospace jobs, and campaign finance intersect. Watchtower presents the record in a readable, bipartisan, public-interest format for WA-10.

Last build: 2026-08-02 Sources cited: 7 Graded claims: 3
info@arafatforcongress.org About
TLDR

WA-10's representative holds a seat on Armed Services.

Rainy aerospace hangar apron with open maintenance bay, perimeter fence, and inspection equipment

Federal Election Commission records and Congressional Record searches are public tools voters can use to understand how defense oversight, local jobs, and campaign finance intersect.

Washington's aerospace and defense economy includes workers, suppliers, engineers, veterans, local businesses, and families who deserve serious oversight without being turned into political targets.

The public-interest question is straightforward: when Congress oversees major defense and transportation systems, voters should be able to see what questions were asked, what protections were proposed, and how local workers and taxpayers were considered.

A better Watchtower standard is neutral and bipartisan: publish the record, identify the policy gap, and propose stronger oversight before failures become expensive for workers, ratepayers, service members, or taxpayers.

For WA-10, that means stronger federal attention to manufacturing quality, defense acquisition performance, worker transition planning, and public accountability across the supply chain.

Receipts

Methodology & Sources Open source record checks, assumptions, and ratings Open

Watchtower applies open-source forensic doctrine to every Ready story. Sources are graded; competing explanations are tested; the assumption that could break the story is named; what would falsify it is listed.

Estimative Probability

Public FEC + congressional record review at the district level can meaningfully inform voter assessment of defense-oversight performance for WA-10.

Records are public and standardized. The bridge from public-records access to changed representative behavior is editorial and depends on voter uptake of the tools.

Analytic Confidence
MEDIUM

FEC contribution data is HIGH (FEC primary). Committee jurisdiction is HIGH (House Rules + HASC primary). TAP statute is HIGH (10 U.S.C. Section 1144 primary). The oversight-impact causal chain (public records review changes representative behavior) is editorial.

Linchpin Assumption

Voters who can readily review FEC contribution patterns and congressional vote records will demand stronger defense-oversight behavior, which in turn changes representative incentives.

Falsifier

Voter polling showing defense-oversight ranks below the threshold of issues that change voting behavior, or a documented case where extensive public-records review of a sitting representative produced no observable change in oversight conduct.

Analysis of Competing Hypotheses
  • less supported

    Current committee structure (HASC, Senate Armed Services, GAO, IG) already provides adequate defense oversight; additional district-level transparency is duplicative.

    Documented FEC contributions from contractors with active HASC business create accountability questions regardless of aggregate spending levels. District-level visibility of the contribution-vote nexus addresses the constituent-accountability layer that committee structures do not.

  • less supported

    Voters lack the technical capacity to use FEC and congressional record search tools meaningfully.

    Civic-tech tools like Watchtower's RMI and per-district scorecard lower the technical barrier substantially. The question becomes uptake (a marketing problem) rather than capacity (a tooling problem).

  • less supported

    Representative responsiveness is bounded by party-whip pressure, not voter scrutiny.

    Whip pressure is real but bounded. Members can and do break with leadership on district-specific issues. Documented voter awareness of vote-record patterns shifts the cost-benefit of those decisions.

Premortem: What Could Kill This Story
  • Public-records access is restricted by future legislation (a hypothetical FEC contribution-disclosure rollback or a HASC vote-record redaction).
  • USAspending.gov data shows WA-10 federal spending grew +36% FY2022-FY2024, consistent with statewide defense growth. The spending-trend claim has been removed; story rests solely on the FEC contractor-contribution nexus.
  • Voter polling shows defense oversight ranking below the threshold issues that drive vote choice in WA-10.
  • A documented case of extensive constituent FEC/vote-record review producing zero behavior change in a comparable district undermines the demand-side mechanism.
Source Claims (NATO STANAG 2511 Grades)
  • STRICKLAND-HUNT-JBLM-001 A1 HIGH

    Hunt Companies Chairman gave $8,000 across 3 cycles to Strickland. Hunt operates privatized military housing at JBLM (WA-10) under MHPI contracts under HASC jurisdiction. Source: FEC Schedule A, C00732826, https://www.fec.gov/data/committee/C00732826/

  • STRICKLAND-WA10-ROI-DECLINE-001 A2 HIGH

    WA-10 federal spending per USAspending.gov API: FY2022 $4.60B, FY2023 $4.96B, FY2024 $6.26B, a +36% gain over the period consistent with statewide defense spending growth. The flat-or-negative characterization is not supported by the data and has been removed. The oversight-performance frame rests on the contractor-contribution nexus in STRICKLAND-HUNT-JBLM-001 and CLM-WA10-DEF-002.

  • CLM-WA10-DEF-002 A1 HIGH

    Strickland voted YEA on S.1071 (NDAA FY2026) and major defense/military appropriations bills in the 119th Congress.

How This Was Researched

Built from federal statute, committee jurisdiction filings, and Department of Defense documentation. Committee jurisdictions are published by the House Rules Committee and House Armed Services Committee itself.

Transition Assistance Program requirements are codified in 10 U.S.C. Section 1144 and operationalized through DoD Instruction 1332.35, both publicly available. The 1990 establishment and 2011 mandatory designation are part of the statutory record.

JBLM economic footprint is sourced to the Department of Defense's Office of Local Defense Community Cooperation, which publishes annual economic-impact analyses for major installations.

What this story does not include: classified material, leaked DoD documents, confidential personnel records, or claims outside the federal public record. The framing that argues for stronger oversight is editorial; the underlying authorities, jurisdictions, and statutes are documentary.

How we check our work

Watchtower holds itself to the same standards U.S. intelligence agencies use for their own internal reports. Before any story goes public, it has to pass every check on this page. Here is exactly what each rating means and how we earn it.

How sure are we?

The scale you see at the top of every story tops out at Almost Certain (95 to 99 percent), not "100 percent certain." That is on purpose. Honest analysts do not say "certain" because real evidence has limits. When someone tells you they are 100 percent sure of anything political, that is the warning sign. Almost Certain is the firmest call a careful analyst makes.

What we call itHow confidentWhat it really means
Almost Certain95 to 99%The public record proves it. No serious alternative explanation survives.
Very Likely80 to 95%Backed up by multiple government records or filings that line up.
Likely55 to 80%The record points this way. Some honest uncertainty remains.
Roughly Even Chance45 to 55%Genuinely a toss-up. We tell you straight when we are not sure.
Unlikely20 to 45%Most of the evidence cuts the other way.
Very Unlikely5 to 20%The record strongly contradicts it.
Almost Certainly Not1 to 5%The public record contradicts it. We would not publish a story at this rating.

Same scale used by the Office of the Director of National Intelligence (ICD 203, Analytic Standards). Designed by Sherman Kent at Yale in 1964 after the intelligence community realized that vague words like "likely" meant different things to different readers.

How good are our sources?

Every fact in a Watchtower story is tied to a specific source, and every source is graded the way NATO intelligence agencies grade theirs. Sources get two scores. The first is how trustworthy the source itself is. The second is how solid the specific piece of information is.

Source ratingWhat it meansInfo ratingWhat it means
ACompletely trustworthy. Government filing, court document, official agency record.1Confirmed by independent sources.
BUsually trustworthy. Reputable institution, minor doubt.2Probably true based on what else we know.
CSometimes trustworthy. Use with care.3Possibly true. Cannot fully verify.
DOften unreliable.4Doubtful.
EUnreliable.5Improbable.
FCannot be judged.6Cannot be judged.

A claim graded A1 is the strongest a piece of evidence can be. Watchtower has a hard rule: every released story has to be built on at least one A1 or A2 source. Stories that lean on C-grade or weaker sources stay out of the public release set. You can see every source under the Receipts list on this page, each one tagged with its grade.

Same grading system as NATO STANAG 2511 and Allied Joint Publication AJP-2.1. Used by U.S. and allied military intelligence to evaluate every reported fact.

How confident are we in our own reasoning?

This is different from "how sure are we" above. The probability band rates the conclusion. This rates the analysis itself, the chain of reasoning that got us there. A story can be Almost Certain on the conclusion but only MEDIUM confidence in the reasoning if the path from facts to conclusion has weak links. We tell you both.

  • HIGH Multiple primary sources line up. The chain of reasoning is short and well-supported. Other explanations have been tested and ruled out.
  • MEDIUM Some sources are second-hand, or the reasoning chain has one or two links that someone could reasonably question.
  • LOW Few sources, or the reasoning depends on assumptions we have not been able to verify yet. We rarely publish at LOW.

What else could explain this?

For every story, we write out at least three other ways the evidence could be explained, then say honestly why we do not believe each of them as much as the one we went with. This is meant to keep us honest. The point is to pick the explanation that has the fewest holes, not the one that came to mind first or the one that feels right.

  • leading Our working explanation. It has the fewest unexplained gaps once we run the evidence against every alternative.
  • less supported A plausible alternative. The evidence does not rule it out, but the leading explanation fits better.
  • rejected Inconsistent with what the records show. We can rule this one out.

This technique is called Analysis of Competing Hypotheses. It was developed by a former CIA analyst, Richards Heuer, and is taught in the CIA's own Tradecraft Primer (2009 edition).

What would prove us wrong?

Before we publish a story, we write down exactly what evidence would force us to correct or take it back, and we publish that list right with the story. Look for the Premortem section above. If any of those scenarios later turns out to be true, the Corrections and Updates log on this page records what changed and when. We are betting on the public record being right; if the record changes, so do we.

This technique is called a premortem. It comes from Gary Klein, a decision-science researcher who wrote it up in the Harvard Business Review in 2007. Imagine the project failed; what would have killed it? Then list those things up front.

What is this story betting on?

Every Watchtower story rests on one assumption that, if it turned out to be wrong, would knock the whole thing down. We name it explicitly in the Linchpin Assumption section above, and we tell you what evidence would prove that assumption wrong. You do not have to take our word for any of it. The linchpin is there so you can stress-test the story yourself.

What if we get something wrong?

Spotted an error? Use the corrections form at the bottom of this page. Every correction we accept gets logged publicly with the date, what changed, and why. We do not silently edit. We treat our own track record as evidence too.

Corrections & Updates

No corrections or updates issued since publish. Spotted an error? Use the corrections form below.

Found an error? Have a tip?

Every Watchtower claim is tied to a primary source. If a claim, number, quote, or source link is wrong, tell us with the primary record that contradicts it. Corrections are published with the story; sources are protected.

Send a correction or tip
Embed this finding on another site

Drop this snippet into any HTML page to embed the trust strip + headline as an iframe widget:

Or cite this story directly via citation.txt (BibTeX / RIS / APA 7 / MLA 9 / plain).