1Origin claimWho first made the concrete allegation?
2Institution / NGO liftDid it move through UN, NGO, court, media, or activist channels?
3Counter-recordWhat official, legal, military, or methodology evidence tests it?
4ConsequenceDid it become sanctions, lawfare, campus pressure, or media shorthand?
01Weapon or technology claim becomes categorical illegality claim
claim_origin
A weapon, AI system, surveillance tool, or military technology is framed as inherently illegal or designed for civilian harm.
02Tool capability, operational use, and legal review are collapsed
category_collapse
The file should separate what the tool can do, how it was used, the approval chain, target selection, and LOAC constraints.
03Technical/legal records test capability and use
methodology_audit
Official, technical, military-law, and investigative sources should determine whether the allegation proves policy, misuse, or false framing.
9001Hostile allegation chain is visible
bottom_source_proof_audit_origin
The dossier contains NGO/UN/media/activist/conflict-party claim-side material. This records claim transmission, not proof.
9002Primary-like bottom proof missing from visible archive layer
bottom_source_proof_gap
The all-claims audit did not find a primary-like bottom evidence item in the visible evidence set. The original evidence must be traced before the allegation is treated as established.
9003Counter-audit and original record required
bottom_source_counter_audit_required
Resolve by finding the original incident/file/record and testing it against official records, forensic material, military/legal context, and counter-audit sources.
9004Interim read: allegation provenance, not bottom proof
bottom_source_interim_read
Until bottom-source proof is verified, the claim page should frame these sources as allegation provenance and source-chain material.
9301Hostile allegation chain preserved
p1_claim_origin
The public file preserves where the allegation travelled: NGO, UN, media, conflict-party, activist, or legal repetition. That is provenance, not proof.
9302Original bottom source lacks the required proof
p1_bottom_source_gap
The decisive test is whether the bottom source proves the exact claim: command policy, verified attribution, legal trigger, chain-of-custody forensics, binding law, or independent verification.
9303Counter-record and methodology audit travel with the claim
p1_counter_record
Counter-audits, official records, forensic/methodology limits, legal thresholds, and pro-Israel expert records must be weighed against the bottom source rather than discounted as advocacy.
9304The public bottom-source record does not show verified Israeli chemical-weapons use in Gaza.
p1_final_debunk_read
Bottom-source debunk: the recurring chain relies on advocacy claims, State of Palestine submissions, and confusion between white phosphorus/incendiary-law issues and chemical-weapons law. The chemical-weapons bottom layer would require verified chemical-agent sampling, OPCW-type substantiation, chain-of-custody analysis, or official findings under the Chemical Weapons Convention. The current source chain does not provide that. White phosphorus allegations, where separately assessed, belong to incendiary-weapon/precautions analysis, not proof that Israel used chemical weapons.