← All structural findings
Network Closure SIGNIFICANT REPLICATED today

Closed loop: US Department of Defense (Pentagon) → Leidos → Dale W. Strong → US Department of Defense (Pentagon)

US Department of Defense (Pentagon) funds Leidos; Leidos has authority over Dale W. Strong; Dale W. Strong benefits US Department of Defense (Pentagon). Three documented edges form a closed conflict-of-interest circuit.
Computed value: 1 closed loop (raw: 1)

Inference logic

1. Edge A→B: US Department of Defense (Pentagon) → Leidos (relationship: funding-type, "Leidos Inc contributed $28,800 ($18,800 individual + $10,000 PAC)").
2. Edge B→C: Leidos → Dale W. Strong (relationship: authority-type, "Strong serves on the House Armed Services Committee, with jurisdiction over the Department of Defense").
3. Edge C→A: Dale W. Strong → US Department of Defense (Pentagon) (relationship: benefit-type, "Leidos is documented as a major defense contractor with $15B+ annual revenue and top-5 contractor status, though direct USASpending contracts were not found in the queried databases.").
Each edge is independently documented in the connections table (IDs 13296, 13308, 17038). Together they form a directed cycle: money flows from A, authority flows through B, benefit returns to A. This is the structural definition of a closed conflict-of-interest loop.

Source edges (3)

  • Dale W. Strong ↔ Leidos — donor (Leidos Inc contributed $28,800 ($18,800 individual + $10,000 PAC))
  • Dale W. Strong ↔ US Department of Defense (Pentagon) — committee jurisdiction (Strong serves on the House Armed Services Committee, with jurisdiction over the Department of Defense)
  • Leidos ↔ US Department of Defense (Pentagon) — contractor (Leidos is documented as a major defense contractor with $15B+ annual revenue and top-5 contractor status, though direct USASpending contracts were not found in the queried databases.)

Comparative baseline

A randomly chosen triple of entities in the graph closes a funding→authority→benefit loop in well under 1% of cases. Each documented closure is therefore unusual on its own.

Steelman — strongest benign interpretation

The three relationships may be unrelated in time or substance. US Department of Defense (Pentagon)'s support of Leidos could predate Leidos's authority over Dale W. Strong by years; Dale W. Strong's benefit to US Department of Defense (Pentagon) could be an arms-length commercial transaction that would have happened regardless of the other two edges. Closure is a necessary but not sufficient condition for a corrupt circuit.

Sensitivity

Edges with vague or generic relationship types (e.g. 'professional association') will produce false positives. Detector pattern matching is conservative but not exhaustive — narrowing or broadening the relationship buckets changes which loops surface.

Replication query (SQL)

Anyone can re-execute this query to verify the published value. If the result diverges, the finding auto-flags as stale.

SELECT (
      EXISTS (SELECT 1 FROM connections WHERE ((entity_a_id=107 AND entity_b_id=10964) OR (entity_a_id=10964 AND entity_b_id=107)) AND (relationship_type ILIKE '%investor%' OR relationship_type ILIKE '%donor%' OR relationship_type ILIKE '%donation%' OR relationship_type ILIKE '%contributor%' OR relationship_type ILIKE '%contribution%' OR relationship_type ILIKE '%funder%' OR relationship_type ILIKE '%founder%' OR relationship_type ILIKE '%co-founder%' OR relationship_type ILIKE '%shareholder%'))
      AND EXISTS (SELECT 1 FROM connections WHERE ((entity_a_id=10964 AND entity_b_id=94) OR (entity_a_id=94 AND entity_b_id=10964)) AND (relationship_type ILIKE '%oversight%' OR relationship_type ILIKE '%regulatory_oversight%' OR relationship_type ILIKE '%regulatory%' OR relationship_type ILIKE '%regulator%' OR relationship_type ILIKE '%committee_membership%' OR relationship_type ILIKE '%committee%' OR relationship_type ILIKE '%chair%' OR relationship_type ILIKE '%appointed_by%' OR relationship_type ILIKE '%appointment%' OR relationship_type ILIKE '%supervisor%'))
      AND EXISTS (SELECT 1 FROM connections WHERE ((entity_a_id=94 AND entity_b_id=107) OR (entity_a_id=107 AND entity_b_id=94)) AND (relationship_type ILIKE '%contractor%' OR relationship_type ILIKE '%contractor_relationship%' OR relationship_type ILIKE '%client%' OR relationship_type ILIKE '%supplier%' OR relationship_type ILIKE '%vendor%' OR relationship_type ILIKE '%grant_recipient%' OR relationship_type ILIKE '%employment%' OR relationship_type ILIKE '%employee%' OR relationship_type ILIKE '%former_employee%' OR relationship_type ILIKE '%consultant%'))
    )::int AS value
Last run: 19 Oct 2026, 01:29 · Last result: 1

Questions this raises

Each question can be commissioned at the matching investigation tier.

  • SEED — $5 What is the timeline of these three relationships — does US Department of Defense (Pentagon)'s support of Leidos predate Leidos's authority over Dale W. Strong?
  • SKETCH — $20 What is the dollar value flowing on each edge over the past five years?
  • SKETCH — $20 Are there public records of Leidos recusing from any decision involving Dale W. Strong?
  • DOSSIER — $75 Map every contract, grant, or appointment between the three entities since the loop closed.
Detector: triangular_loops v1.0 · Created —