TruaceTracing the truth around AIMonday, July 20, 2026
TRV-2026-0300Certified recordJournalism

Israeli command system identified 850,000 targets in Gaza and Lebanon wars, says supplier

Israel identified about 1,000 potential targets a day during the first two years of the wars in Gaza and Lebanon with its command and control system, according to a presentation by the country’s largest arms supplier, Elbit Systems. A total of 850,000 targets were detected in real time by the Israeli Tzayad digital army programme across all the military’s theatres of war between 7 October and the end of 2025, the company said at a military conference in London. It describes the number of people, vehicles and oth…

Other · The Trace — both readings · certified 2026-07-20 · v1 · article view · machine-readable

Current reading — gain

Tzayad digital army program using AI to support tactical decision-making increased speed of fire support and enabled detection of 850,000 real-time intel targets across Gaza and Lebanon theaters.

Current reading — problem

At 1,000 real-time targets per day flagged by the AI-assisted Tzayad system, soldiers could not thoroughly assess collateral damage and civilian risk, coinciding with 71,269 Palestinians killed in Gaza.

What this doesn’t fix

Elbit disputes the interpretation of the 850,000 figure and the source notes uncertainty about what counts as a target versus system activity, and the casualty figures are attributed to external agencies.

Evidence

Reader signal

How should this claim be treated?

Cite this record

Truvace Impact Record TRV-2026-0300, v1: “Israeli command system identified 850,000 targets in Gaza and Lebanon wars, says supplier.” Truvace, 2026-07-20. /record/TRV-2026-0300 (accessed at citation time). sha256 2e8de76bc5f351e6

Calibration history

Every change to this record since certification, in the open. None yet — the reading has held since it entered the record.

  1. Certifiedv12e8de76bc5f3

    Certified into the record

Verify this record
How to verify without trusting this page

Fetch the canonical text of any version from /api/record/TRV-2026-0300 and hash it yourself — for example shasum -a 256 on the saved canonical field. The result must equal content_hash, and each version’s text ends with prev:followed by the prior version’s hash (version 1 chains to 64 zeros). If a single character of any version had been altered since certification, the chain would not reproduce.