Warning

Warning: This site contains images and graphic descriptions of extreme violence and/or its effects. It's not as bad as it could be, but is meant to be shocking. Readers should be 18+ or a mature 17 or so. There is also some foul language occasionally, and potential for general upsetting of comforting conventional wisdom. Please view with discretion.
Showing posts with label HRW. Show all posts
Showing posts with label HRW. Show all posts

Thursday, February 13, 2020

On OPCW-Bellingcat "Collaboration"

Adam Larson (aka Caustic Logic)
February 13-16, 2020


Feb. 16 note: This needed split-up into parts in order to get even part of it up ASAP - I've been super-tired lately and sleeping a lot (getting better now). But the pieces seem too small for three blog posts, so I assembled them here over a few days. I suppose this needs to be it, aside from typos, etc. and any possible updates.
19 February: a similar line of inquiry can be seen here by Philip Watson, involving an allegedly informed source who claims Bellingcat's Eliot Higgins was commissioned - if indirectly via former team leader Len Phillips - to inform the FFM Alpha team in Turkey X (that is, perhaps, to submit findings like that grid pattern, rather than just letting them take it from public airings as I had presumed). I'm very skeptical of Watson's works at large and we do not get along. I'm skeptical but undecided about his source and claims. But it's worth considering, and the article raises good points I miss here, like apparent leaks of an acceptable kind to Brian Whitaker (definitely to publicize one of the OPCW's conflicting reasons to dismiss the Henderson/EST engineering report, and possibly even to reveal the name of their former inspectors suspected of involvement in the leaks they don't like)

Part 1: A Simple Error?
It was recently noticed the Bellingcat research collective's "policy plan" document for 2019-2020 bragged (or blagged?) of past or ongoing "collaboration" with the OPCW, which in the last year has been embroiled in ongoing controversy over its handling of the 2018 Douma incident in Syria. Several influential bodies (mostly private but promoted, like Human Rights Watch and "Mayday Rescue in support of the White Helmets") are listed as collaborators of Bellingcat. But this highly partisan group of error-prone pseudo-experts also claimed such work with two important international bodies; the list of specified entities ends with "International Criminal Court, Organization for the Prohibition of Chemical Weapons (OPCW), and many more." The paragraph in question, screen-grab:
A search I did about two days ago shows the document had said this:

I was looking into it after noticing a discussion between Bellingcat founder Eliot Higgins and Norwegian researcher Eirik Rømcke @Vaalandspibaa on February 7- 9. Rømcke had to ask repeatedly to no answer. On the 7th he asked "You have asserted a collaboration with the OPCW on page 7 in your "policy plan" (link for pdf-download below) Wouldn't that be in breach of their independence? Please clarify" Higgins asked "specifically what assertions are you referring to?" He was reminded, but didn't reply. Rather, he deleted that question before I could see it. (screen grab showing what it had said and note he refers to another tweet deletion before that).

By the time I caught the discussion on the 12th and checked to file in question (Bellingcat policy plan 2019-2021), the collaboration list no longer included the OPCW, stopping at "International Criminal Court, and many more."

Such "collaboration" may have a specific legal definition that has to apply here, or not. I don't know.  The collaboration with ICC is still proudly listed, apparently presenting no problems even after the recent review. Their work for the OPCW could be fairly innocent, but apparently it looked bad in a way ICC did not, so it's been changed.

As I saw that: "NOT that there's anything to hide about #Bellingcat's "collaboration" with #OPCW, but they did just hide it." https://twitter.com/CL4Syr/status/1227560932366114816

But Higgins soon offered an explanation: that wasn't an admission hidden, just an error he corrected; OPCW was never meant to be there: "That was on there in error, copy and pasted the list of names from another document and didn't mean to leave it in, then didn't read it since it was uploaded, so I've fixed that now. We've not collaborated with the OPCW, apologies for the confusion, totally my fault."
https://twitter.com/EliotHiggins/status/1227553917829046279

Implicitly, he only noticed it in the course of the discussion cited above, during the pause there. He never did acknowledge the tip with a thanks, or with any reply - aside from deleting yet another line from that discussion. Implicitly, Higgins had edited that document himself, so he could personally vouch for the copy-paste error as soon as he saw it. That seems unlikely, but is possible. And what was the error? Maybe he copied that from a list he had whipped up of groups they've collaborated with or would like to?

More likely they - as a group - were actually bragging about some kind of collaboration with the OPCW - real or invented, exaggerated or maybe just described carelessly That would be back before the leaks and controversy began, not anticipating such deep questions would be raised about the organization's process. I was thinking he/they would argue what "collaborate" means, but the removal suggests that was (or would be) kind of cooperation they aren't supposed to do. (Or perhaps it was alright, and Higgins was just worried that he shouldn't have mentioned it?).

Possibly related: the Bellingcat foundation was in the same days "currently going through a detailed audit" for financial transparency, as Higgins mentioned, as pat of their achieving charity status in the Netherlands. And an update: 15 Feb. he says "We even got charity status in the Netherlands, which involves lengthy external audits with the results published at the end of the process, so I'm obviously very terrible at cover ups." So this is a registered "charity" we're examining.

What kind of collaboration might exist, despite this denial? There are two broad classes where their activities play in, or have at least been suspected. The following two parts explore their possible role in shaping the findings of OPCW investigations, and their curious efforts to promote some aspects of the body's work while launching deceptive attacks on other aspects.

Part 2: Shaping OPCW Findings?
First I'll re-consider a few possible or suspected cases of the Bellingcat network having an undue hand in shaping investigations by the OPCW. Nothing I've found makes for a ground-breaking proof of such, but there are cases to be made. We'll stat with the Douma probe and this recent Higgins tweet: "I just want to nip this silly claim the chemical weapon truthers are spreading in the bud, Bellingcat had nothing to do with the OPCW FFM report on Douma, and we certainly weren't one of the ballistic experts cited in the report. Stop making up stories to impress your followers."

Nobody claimed the Bellingcat TEAM was one of the three individual cited experts. There's been speculation one or more of them might be PART OF Bellingcat, but Higgins will be denying that as well. That still appears sadly possible from my end, but I suspect the FFM would have called on other, more "grown-up" people, probably with formal qualifications.

There was a FFM engineering sub-team whose findings were never called on (whether it was even requested is a matter of dispute). And there was an early-June consultation with toxicologists that was simply ignored. And there was the formula change to core team only in July, excluding all but one of those who'd been to Douma (one of whom was Ian Henderson with his EST report they didn't want). So from July-August 2018 and forward, they'd be pursuing a plan B in both toxicology and engineering-ballistics, and probably keen to avoid the need for any plan C; they'd want extra-sure cooperation. The replacement experts would have some expertise but it needn't impress outsiders, who'd never know such details. Mainly they would need the right combination of political views and suggestibility, and just enough tools to produce a few plausible-seeming supports. I wouldn't be surprised if it was someone we've heard of who works with Bellingcat, like Dan Kaszeta for toxicology and Hamish de Breton-Gordon for engineering (for example). But it would be more logical to use someone we've never heard of, who was suggested by such contacts as someone who could deliver the right answers.

And even aside from the possibility of such direct involvement, it's quite possible Bellingcat had something to do with the FFM report, now that their greasy fingerprints are over so many things. The relevance of that would be hard to say without a bit of review, to which we now turn.

Douma cylinder grid pattern 
The question I've raised recently is whether one of their findings in particular wound up in the FFM's final report when it doesn't belong, being a preposterous notion clearly not based in science. It's hard to imagine - but still possible - that one of their engineering experts proposed this idea on his or her own, but more logically, they took it one way or another from the Bellingcat network. Most logically, it was copied from a widely-seen New York Times video report, citing wok by Forensic Architecture, who credited Bellingcat - and it was a member of their network who first publicly proposed the idea, just one month after the event, inverting an idea first offered by Michael Kobs as vey unlikely.

This fascinating point was worth its own detailed post to explain in full (see The Illogical Douma Airdrop Clue that Might Show How it Was Faked). What follows is a short summary taking advantage of that prior work and skipping the "how it was faked" part to save space.


At right is the sequence required for this observation to mean what's claimed. I've asked everyone involved if they can model or animate the sequence (no one having done so already), or even explain it any better than my illustration does. Higgins seems to have me on universal ignore since about 2014, so it's no surprise he never answered. But Bellingcat at large, Mr. Vandenberg, Forensic Architecture, its founder Eyal Weizman, and NYT's Malachy Browne all ignored the question (queries listed with the above article). Apparently none of them is confident enough to revisit this issue. They're just glad it snuck to the top like that without anyone who matters calling it out. That was the hit, and what follows is the run.

Douma cylinder movements
Much attention has been paid recently to initial cylinder movements at the same site (location 2, the one with 35 fatalities). Higgins was had an exclusive video sent by White Helmets contacts the day after, with a screen-grab he briefly showed and then deleted. In its place he got a likely custom-made video showing the surroundings (allowing a geolocation), the date and time, and no people (just the screen of someone's personal phone). But since the other video, the cylinder has also been rotated some 180 degrees and moved a bit.

Higgins swore then and swears now the first video was removed only for showing a man with his face covered by a paper mask, by which he could be identified and killed. That is possible (he was identified based on what's seen, and on review Bellingcat does tend to exclude people from photos showing weapon remnants). Still it seems unconvincing in context.

On the other hand, I don't see much reason to rotate it; that does leave the side that's mildly  dented lining up against some intact rebar (right, from Swedish TV4). But that didn't convince anyone, and the soot-coated area and runoff pattern down the sides would prove its being rolled even without a prior image. Significance to FFM findings: "the cylinder was moved a number of times prior to the FFM visit," with this being one time.

Higgins offers a guess as to why it was moved: "there's a good chance it was covered by the various metal debris and it was likely cleared out the way to get a good look at the cylinder." I added "You could also narrow down the chances with reference to an image of the pre-movement scene. "

I've considered this point overrated, so I reflexively didn't consider it 'til the last minute. It does belong here, not so much for influencing any OPCW findings as for showing Bellingcat's involvement at the other end, where the evidence and actors on the ground meet; they might work with the evidence managers allied with the perpetrators AND with the official agency that winds up effectively laundering their claims.

As for the significance of this one; I didn't review the one question I'll pose to readers/myself for a possible follow-up - did Higgins possibly have both views in front of him before the deletion of the one? If so, he would seem to be covering for evidence manipulation - though not very well, and not a very significant alteration, as I just explained. But if the next-day video postdates the deleted image, the reason he gave would be as plausible as anything.

Before Douma
Even if the FFM's engineering experts and their submitted findings had nothing to do with Bellingcat or that silly gid notion, that could easily be inserted by, say, FFM team leader Sami Barreck at his own discretion. Other possible reflections could come in the same way, might be in there in finer points or ones I'd noted somewhere, but these two could suffice to illustrate possible shaping of the Douma findings.

"Collaboration" could also go further back to Bellingcat's founding in 2014, and the work of its members might have played in even earlier, like Higgins' 2013 work on the "volcano" rockets linked to the 2013 Ghouta incident. They did a lot of video collation and considering different kinds of chlorine bombs allegedly dropped from helicopters over the years. That's likely to include some incorrect calls that made it into  repots of the FFM and JIM reports. But without more review, there's just one prominent case that comes to mind.

2017 Bomb ID: HRW
Then there was the suspected role of Bellingcat in identifying a certain Soviet-designed sarin bomb as used in the Khan Sheikhoun incident of 4 April, 2017. This idea first appeared (widely) less than a month afterwards, in a 1 May report by Human Rights Watch. As their CEO Ken Roth tweeted May 1: "Remnants of Syria's Apr 4 chemical attack match Soviet-era air-dropped bomb designed to deliver sarin" Of course the Soviet Union was likely to have provided weapons to Syria in the past, perhaps including the weapon they just identified, that might implicate Syria and enable accountability, in the interest of Human Rights.

The report cites how it seemed to be "a factory-made sarin bomb," taking some faint greenish coloration as a painted stripe like on the KhAB-250 (it isn't), and decides "the circular object in these photos appears similar to the cap for the filler hole on the body of a KhAB-250 bomb," if one looks at it inside-out like they did, and takes "similar" as close enough to "match" in this specific a sense.

A source is cited, and it's not Bellingcat by name. "The similarities between the remnants in the crater and the KhAB-250 bomb were first identified by the twitter accounts @elemcee69 and @Mortis_Banned. See e.g., tweet from @elemcee69 on April 14, 2017, https://twitter.com/elemcee69/status/852809433570615296."

But I can't, because "Twitter suspends accounts which violate the Twitter Rules" and this was one of them.  However, Mortis_Banned is alive and not banned - aka "​Children of Soros #NotOurTsar" Researcher at@citeam_en, seems obsessed with demonizing Putin + Assad, eagerly pushed this discovery. April 9, 2017, a Ricardo Peldito seems to be the first with photos of the bomb in a museum. Some possible different models or translations are bounced around in the following days; M-B added "According to that CW disarmament specialist, ОБАС-250-235П is one and only Sov/Rus aviation bomb to spread Sarin. That looks like filler cap" (museum pieces, b/w photo). "I do agree that currently OBAS-250 is a hypothesis at best" he said, in response to Bellingcat's Dan Kaszeta (whose tweet is invisible on my end), in a discussion also including founder Higgins, the named elemcee69, and others including professor Jeffrey Lewis and Military-specializing Dutch journalist Hans de Vreij, who warned "In the absence (so far) of ÁNY evidence of the alleged chemical ordnance used, I'm not going to speculate about 'a 250 kg bomb'"

HRW ran with an ID at least inspired by that discussion, aired in their report at the start of May. It was quickly supported by Mortis_banned and others. The Bellingcat team's Timi Allen snapped out a 3-D model on the 3rd, but that was quickly refuted by Michael Kobs, showing clearly how HRW had taken it inside-out.

The Russian MoD had already alerted us the KhAb-250 was never exported and all active copies were destroyed decades ago, aside from museum pieces like the one used for these false claim. Mortis-banned resisted: 9 May: "If @mod_russia were so kind as to declassify docs on the OBAS-250-235P, we'd know if this looks like an internal part of the bomb."

Bellingcat role in this find: they're directly cited in the HRW report with 4 things: geolocation for sarin crater, and of a video view from the north (both fine), for Dan Kaszeta's article on sarin they published, for another weapon ID (Iranian rockets blamed in chlorine attacks in Ghouta). But they're not cited by name with the KhAB-250 identification. Higgins or someone at Bellincat worked with HRW, while the cited sources probably did not. - they were in that discussion, likely brought it up, but if so maybe asked to not be credited directly, fearing it was the bad lead it was. Soon they were in agreement with that track's undeniable failure and on the lookout for a different bomb, eventually deciding (with decent if questionable basis) it was the little-known Syrian M4000 that had some scraps appear at the site.

2017 bomb ID: UN and OPCW
Regardless, the same point would be included by the UN Human Right's Council's Commission of Inquiry in a September 2017 report; they would note "what appears to have been a Soviet-era chemical bomb" - not any specific model they could name, including KhAB250 but "the parts are consistent with sarin bombs produced by the former Soviet Union in the 250kg-class of bombs." The source for this isn't entirely clear, but it sounds like HRW's findings adjusted for being proven wrong (presuming they were only wrong on the exact model of 250kg Soviet sarin bomb?)
http://reliefweb.int/report/syrian-arab-republic/report-independent-international-commission-inquiry-syrian-arab-3

And the 7th and final report of the UN-OPCW Joint Investigative Mechanism, released in late October/November, would include a different version of the same idea aimed at blaming Damascus: "According to information obtained by the Mechanism, the filler cap, with two closure plugs, is uniquely consistent with Syrian chemical aerial bombs. ... Information was also received that additional metal fragments collected from the crater might correspond to parts of Syrian aerial chemical munitions."
https://undocs.org/S/2017/904

From whom this information was "obtained by the Mechanism" is not specified. The two-hole closure is quite generic - all we've learned is it's not that one Soviet bomb, so it's unclear what further deduction was involved to make it "uniquely" Syrian. And there's clearly no way the other featureless scrap could be linked to some nation's sarin bomb - that was one scrape too many across the bottom of the barrel.

But in between these weak points was an "assessment" they were given that the sarin's manufacture involved hexamine and "very high heat" - clearly to suggest the Syrian state made the stuff, not any jihadists. Those points are dubious, source unclear. The general view I tend to accept is it's the same basic material recovered after Khan al-Assal 19/3/13, Saraqeb 29/4/13, Ghouta 21/8/13, Jobar 24/8/13 (in soldiers' blood, a mortar shell, a weapons workshop, all at about the firing spot for the rockets blamed for 21/8), Daraya 25/8/13, Daraya 15/2/15, etc. Sometimes 40% impure, kitchen-grade sarin with lesser potency, a yellow color, caustic properties, foul and strange odor. If that's what they head, I wouldn't dispute it.

Chances are close to 100% the prior track advocated by Bellingcat and allies at least shaped this unexplained turn. There's a lower possibility the collective's members directly informed the commission on these findings. Again, there is a world of dubious experts out there to help dubious investigations like this fill in their dubious blanks with politicized disinformation to fit the pre-ordained conclusions.

Was this finding of the UN-OPCW JIM based on the eventual M4000 ID in an early phase? Not by what we know. The report was "leaked" in late October, formally released soon after. The Russian MoD first shows an M4000 diagram only in response to that, on the 2nd of November, and was noted prior to this Bellingcat article on the 13th. And no one has given a reason other than seeing that slide to know about the M4000's design. So this earlier decision is mysterious and strangely predictive.

It's as if HRW's claim had driven everyone halfway across a desert towards the oasis of "blaming Syria with a specific bomb ID." That road quickly came to a stop, but they wouldn't turn back. The CoI and the JIM in turn seem to be bumping across the fields 'til they find two road-like flat patches that run a bit further toward the oasis (unknown but uniquely Soviet, unknown but uniquely Syrian). Then quickly outrunning that, the whole convoy was bumping for just a few days before they hit the clear, paved M-4000 highway running straight to that oasis. Damascus admitted it had that bomb, had converted them to hold explosives, and dropped them all over for people to find pieces of. Was that highway paved by impostors unauthorized by reality, who planted some old M4000 scraps at the site? They don't care.

Bellingcat got to take the lead driving here, with ally Greg Koblentz in the cab with Eliot Higgins. And this is where the OPCW's Investigation and Identification Team will pick it up...

But back in 2017, that unexplained finding appearing in a JIM report gave it a stamp of authority, allowing for later comments like this from Higgins: "The March 30th 2017 Al Lataminah Sarin attack is significant because filling caps with the same design and green paint as the one recovered from Khan Sheikhoun was recovered, one the OPCW described as being unique consistent with a Syrian Chemical bomb." As far as we know, he or a close ally is the one who first told them that, based on absolutely nothing.

Part 3: Attack Dogs
or promotion and backup information security
So it seems like the broader Bellingcat network does enjoy an undue role in shaping the OPCW and FFM's findings. But so far that role seems mostly indirect or unproven, and their main uses are on the output end.

Their promotion of findings over the years has been helpful, re-explaining the overt and covert findings in the FFM's reports (eg. filling in the blanks on how falling = helicopters = Assad). They'll gloss over egregious omissions to pose the official science as clear, and sideline any doubts (attacking the reader's skepticism, you could say). They emphasize doubts emanating from Russian-linked sources, and any similarity of those to anyone else's doubts, and use that to dismiss them (both adding to and drawing from that ongoing information war).

In recent months they've taken up what could be called backup information security - they sideline doubts from within the OPCW itself - and leaks that bear them out - by attacking its inspectors who claim to be blowing the whistle on unethical practices. It seems the OPCW's scientific aspect is in partial revolt against its political aspect. Damage to trust has been caused (and/or deepened) by a good hard look, over the last ten months, at the organization's corrupt state of operations. The Bellingcat team comes down squarely with management, using their open-source sleuthing skills with exceptional ineptitude here, trying hard to invent and then combat all kinds of flaws in the leaked information and/or the people leaking it. It works about as well as a pencil eraser on ink - it cannot make it go away, but maybe it can make things vey muddled and a bit more faint.

I'm not claiming Bellingcat as a whole or any members take orders directly from the OPCW, as if they were employees or even formal consultants. It seems possible - if not likely by track record - that they simply follow the truth into their constant agreement with the FFM's findings. They're tasked with this I suppose in a general implied sense by the same people who...
a) provide some of their funds (UN taxpayer-funded NED at least)
b) lead all brute-force financial and military efforts to impose "accountability" for the crimes Bellingcat helps expose in Syria (except those pinned on ISIS - others do more in that area)
c) steer the actions of the OPCW, by threats and oustings if needed (2002) or by more subtle means and working with more allies towards more consensual ends, including illegal wars and aggression against Ba'ath party governments in the Middle East
d) by general dint of running the world, as it were, they also shape what's seen as a wise investment, and what kind of people get wealthy enough off of the current reality to re-subsidize it with a donation to Bellingcat, for example.

I suppose it's similar to how we have a "free" media because it's not state-run, but corporate-run instead. But then of couse it winds up agreeing with the corporate-run state, making it more like a sibling relationship than a parent-child one. It might be similar here, with the OPCW as the adult sibling with a good necktie job and reputation, and Bellingcat a semi-acceptable little sister with punker friends who can get "other" jobs done. With Mom and Dad fully in the loop - actually running the loop - big brother doesn't even need to talk directly to little sis or her friends. Things could just happen fortuitously without you ever seeing her in the room. But then you might see one of her distinctive artifacts left behind from time to time, as we may have in part 2.

Different kinds of leaks: promoting the political ones...
On 26 October, 2017, there was a "leak" at the OPCW and it caused no alarms. The UN-OPCW Joint Investigative Mechanism (JIM) in effect at the time had wrapped up its investigation of the April incident in Khan Sheikhoun and its final report on the incident. An advance draft was released days early (no ID number assigned yet, etc.), uploaded here on Google Drive by Nabil Abi Saab, an Alaraby TV correspondent based at UN headquarters in New York. This allowed some public buzz and commentary to precede and amplify the effect of its formal release as S/2017/904 on 7 November.

So the file was not shared directly with Higgins or Bellingcat, as some of us had wondered. They did eagerly share the "leaked" report, saying it "shows that, despite Russian and Syrian protests, there’s now clear evidence that Syria was responsible for the Khan Sheikhoun Sarin attack, and alternative versions of events presented by Russia and Syria are fabrications." (Of course it did so based partly on dubious points like the "uniquely" Syrian bomb yet to be identified, and partly on the unfortunate fact that the specific theories posited by Syria and Russia were just bad guesses.)

That was clearly an authorized release intended to maximize the political implications of what would the final report of the JIM (it worked so well the Russians refused to extend the mandate of the weaponized mechanism). In fact it was only called a "leak" by Bellingcat and their ilk, perhaps to make it sound edgy and relevant, besides politically useful.

In contrast, the unauthorized releases of 2019 reveal a very fragile process that cannot bear scrutiny by the public. Uninitiated into the special magic involved in getting to that Assad-blame, we might get "confused." And we widely did; to the outsider, it looked as if the OPCW's FFM was suppressing valid findings to protect the politically desired ones. It took some special explaining by Bellingcat and allies like Brian Whitaker to set some people "straight." This awkward episode serves to remind us all why unauthorized release is strictly disallowed, as the OPCW's Director-General Fernando Arias has recently reminded us, and those who break the rules they had agreed to and knew full well should be held to account.

… and neutralizing the legitimate ones.
An example by punishment could deter future instances, but it won't be able to recall the exposed information of past ones. Unstopped leaks that threaten confidence in the organization would need to be neutralized as possible, re-branded in the public mind. And as things turn out, Bellingcat and allied signal amplifiers like Whitaker (who only seems to me outside that network due to his seniority and fading past of journalistic credibility) labor to cast the leaked evidence as something wrong, irrelevant, and helpful to the Russian cause, leaving no legitimate reason to accept or spread it.

A typical comment in recent days is this by Higgins: "the leaked claims aren't credible because they made assumptions which turned out to be wrong, made errors in their work, and lets not forget they're making claims based on the work of the OPCW before months more of investigation by the OPCW." The supposed errors have been discussed elsewhere, but in brief: working with Forensic Architecture again, Bellingcat did make a show of addressing the evidence and they raised a few minor points, but wrongly alleged measuring errors and missed the point(s) about presumed drop altitudes, just for the leading two among a very few points they considered unevenly, yielding results that don't hold up under scrutiny (see for example my review comment at the article claiming to show Hendeson wrong). As for that "many months" of improvements they missed after "Alex" quite the OPCW and Henderson was excluded from active work - this is where the special magic happened, after all but one of the investigators who was in Douma had been excluded, the previous toxicology findings and various other complications were removed, and illogical proposals were weaseled in, one of them at least likely copied from Bellingcat. as part 2 explained. Being kept out of that process sounds like a recommendation to me.

On this faulty basis, Higgins has declared the engineering report's "content is actually inaccurate, so [Henderson]'s a liar who got things wrong, then a bunch of people promoted that to attack the OPCW." Other tweets just from Higgins expand on this: "Alex lied about Ian Henderson's status at the OPCW" and Henderson is "someone who lied repeatedly, so not exactly the most trustworthy source of opinions on the final report." ... "both leakers were involved with deceit, and violated the protocols of the OPCW which they would have both been fully aware of." ... "violating multiple internal protocols, deceiving staff and external organisations and individuals" ... And finally (Henderson's report) "ends up getting leaked to the Syria Propaganda Superfriends and he's pleased about it, despite the multiple violations of his obligations to the OPCW."

The motive behind his disputed actions couldn't be certain, but it's easy to pick a direction and paint some arrows that way. Bellingcat's part 2 article notes "the Russian Federation appears to have had access to [Hendeson's report] well before" its leaking to the WGSPM last May. Basis: "On April 26, 2019, the permanent representative of the Russian Federation to the OPCW sent a critique of the final FFM report to the OPCW, sections of which were remarkably similar to Henderson’s report." Brian Whitaker tried to help them spin this issue with an article at Al-Bab, which can be seen to fail after its best efforts. There is the kind of similar wording you'd expect from people reaching the same conclusions and using proper technical terminology. In one case the original words would be in Russian, and based on their own on-site investigation, with no need to copy anyone. It also fails to note non-copied points like the Russian report (PDF) but not the Henderson one noting primary fragmentation marks to support their decision a mortar shell or similar, not an impacting gas cylinder, caused the associated damage.

Now, if one were intent on seeing Henderson and his report as wrong, its agreement with the presumed Russian lies would seem extremely suspicious. In that light, the Bellingcat side almost seems to underplay this issue as just one among several lines of attack. It's not teased out in deeper detail, perhaps because they can already see the other side of the problem; if Russia's accepted engineers and the OPCW's sidelined ones independently reached such similar conclusions … isn't possible they're both talking truth?

the FFM's disagreement on the fragmentation marks, for example, is to simply deny they exist, or perhaps to link them illogically to the cylinder impact. See at right: they want you to note the damage in the red circle, never try to explain the bullet-like marks radiating out from that spot, unless it was with this: "It can be seen that there was a large impact on the roof and walls above the balcony," causing the cylinder to slow down and fail to punch through fully. But no one has or can propose another plausible explanation but the marks of explosive primary fragments. A Bellingcat-allied weapons expert tried, in a less-than-lucid moment, suggesting "prior or subsequent battle damage" instead of what I proposed. But it clearly couldn't be very "subsequent" so that's basically what I had proposed. Professor Scott Lucas likewise suggested "months of bombardment" had caused the marks, also confusingly posed as disagreement. Neither could say how this would cause such marks other than by explosive fragmentation, both having tried but come up with the same thing. (the best try would be bullets, but that requires a bizarre scenario of someone on the balcony shooting the walls in a circle, and some other strange damage and scorching coincidences on the east and west walls, besides the strange cylinder impact to follow.)
https://libyancivilwar.blogspot.com/2019/05/douma-location-2-explosives-damage.html

If you have to flatly deny the visual record like this without any explanation, in order to make your point, your point might be wrong. Right?

But Bellingcat's open-source analysis came to the rescue to support the FFM's rejection of this clue. How? They cite the open-source FFM report itself on this point, adding nothing futher. Douma leaks part 2: "The final FFM report directly disagrees with these findings. They also considered the possibility that the crater was a result of an explosive device, but concluded that it was “unlikely given the absence of primary and secondary fragmentation characteristic of an explosion.” They did so with NO BASIS - thee is no such "absence." "We also know that the scorching under the crater was likely not from an explosion," Bellingcat adds, citing the FFM. Linking that to the blast was an error on Henderson's part (a hot fire was intentionally lit atop the rubble, reason unclear/disputed. The smoke from this coated the ceiling, the cylinder's underside at the crater, and apparently vented through the damaged vent on the balcony so that smoke is also unrelated).

BUT we also know that there are three more crucial details Henderson and/or the FFM's "engineering sub-team" had cited (the app. SECONDARY fragmentation marks, extreme rebar bend, and widespread spalling visible inside the room below impact). These still support the blast version, and do not have plausible work-arounds. And that's besides the clear primary fragmentation marks he somehow missed (but the Russians duly noted), and other things like the strange variance in rebar damage, and scorching with no other explanation on the upper balcony edge (middle of the west wall), closer to where the detonation fireball would be - just above the balcony, leaving little to no sign.

But on the plus side: management said there was no explosion here, and people trust the management. Bellingcat loves to add to the OPCW's credibility account, but on this point they could only make a withdrawal.

Talking and yet not talking about Putin collusion ...
But they had more besides the supposed errors and their similarity to Russian lies. Higgins infamously mused "appearing on behalf of the Russians seems to tell us something" about Henderson. I'd say it tells us how no other great power - aside from the Chinese, who actually invited him - would invite him to address the UN Security Council about the problems at OPCW. The US would probably block his visa to prevent his appearance, as it seems they did. That too might tell us something, eh?

It's disputed just what Higgins meant here, but he firmly denied the obvious reading when Max Blumenthal called him out: "Suggesting Ian Henderson is a Russian asset is indeed a vicious attack, and is in keeping with the tendency of Bellingcat and its troll farm." Higgins replied: "I didn't suggest he was a Russian asset, you're just so blinkered in your worldview and your perception of me that you projected that onto my words and drew a faulty conclusion, as usual. Maybe pull your head out of your arse and look around for once." But of course he didn't explain what his true meaning, because that was clearly it. It's deniable, but the denial rings flat.

(this follow-up tweet might clarify? Speaking at that session "demonstrates a lack of judgement if he's attempting to establish his credibility. Although, seeing who his report was originally leaked to, that's no surprise." We learned that the veteran inspector with OPCW from the start, re-hired to be a repeated team leader and innovator of Challenge Inspection techniques, and seemingly the most qualified person in the Douma FFM team (core or shed portions) to make the calls he made ... is not very good at "establishing his credibility" and this "tells us something" real? No, he meant the other thing.)

Bellingcat also titled their first three parts on "the Douma leaks" series "We need to talk about [x]" where the [x] was: whistleblower "Alex" (part 1), whistleblower Ian Henderson (part 2), and a false flag theory (the best and most dangerous answer to the raised question of what DID happen - part 3). This was almost certainly done in reference to Russia expert Mark Galeotti's recent book "We Need to Talk About Putin," the Russian dictator hacking our reality. The suggestion is that same crucial discussion should extend to dissenting views within and without the OPCW, as possible extensions of Russia's global disinformation campaign.

(Credit to "Malinka" for noticing this)

… and not about what matters here.
But when it comes time to consider the OPCW's shameful witch-hunt against its own investigators, it's just "The OPCW Douma Leaks Part 4: The OPCW Investigation." When it's other powers that might be pulling the strings, we don't NEED to talk ABOUT the OPCW reaction; little sis just repeats big brother's factually deranged damage control, linking to her own prior "analysis" to show how grounded it is. In fact "it is fitting" to let Director-General Arias have the last word, as they did, about the OPCW's former “Inspectors A and B" suspiciously insisting on views "not backed by evidence," yet still trying to "gain traction" in areas where they had no business. These two meddlers breached their obligations in an "egregious" manner, worsened by their exclusion from the latter investigation where the special magic was applied, the apparent Bellingcat findings worked in, etc. and so "their conclusions are erroneous, uninformed, and wrong.”

Again and again, DG Arias has answered the serious questions with vague platitudes and shows of confidence. He still stands by the FFM's Douma findings as all those before, even if they're careening and bound to collapse on him and the once-lauded OPCW he will have helped destroy. He's probably no villain by nature, just under pressure. It might be worse than the threats to his children and forcing from office suffered in 2002 by the first DG of the OPCW, José Bustani, when he insisted doing his job, even if it frustrated an illegal war on Iraq. Bustani has already called the suppression of findings and investigators in the Douma probe "unacceptable behavior" for the OPCW and its leadership. How much worse now to see his own successor playing the part of John Bolton against his own in defense of that corrupt situation?

Bellingcat describes itself as "independent" - which is debatable and deserves clarification - but wisely doesn't even claim political neutrality. In fact it brags of being "particularly significant for advancing narratives of conflict, crime, and human rights abuses," and generally the same narratives pushed by the US and UK governments in Syria and beyond (if not exclusively). We note their role in shaping the UK's investigation of the Skripal poisoning - the who if not the how. Despite a weak show of "openly" addressing the evidence of the Douma incident in particular, Bellingcat's argument relies mainly on blind (or vision-impaired) faith in findings that are sometimes pure nonsense; appeal to authority is far easier when it's someone else's you appeal to, and that someone else is the still-trusted OPCW.

This is the same stance taken by US and UK governments and their allied states at a UNSC aria-formula meeting of 20 January, 2020 (my analysis). The ambassadors of the US, UK, France, and several allied states pointed to the fact that the OPCW is widely trusted, or extremely trusted by them, is reason enough for everyone to maintain that. Along the way they ignored the words of Mr. Henderson, eyewitness and visual evidence that was presented, the views of the host state - the People's Republic of China - and concurring states including at least the Russian Federation, Iran and Egypt, besides softer doubts aired from Niger, South Africa, Indonesia, Vietnam, and other states. Their criticism of the OPCW's current process was grounded, and mainly no harsher than that of its first Director-General, but it was all implicitly dismissed as "Russian disinformation."

The Western powers will find the OPCW in its current state very useful; it can be relied upon to churn out politicized findings to "justify" various forms of "accountability" against enemy states, regardless of the physical reality. If this were ever changed, they'd lose a weapon on the world stage. So they insist on keeping the faith - the consensus the OPCW rely on - attached to its current form, not its ideal one. But now that the dishonesty of their investigative process has been exposed - long after being suspected in some quarters - it's lead to a serious loss of faith by everyone else. One camp's favorite features are the same that would destroy the needed consensus.

So depending how one looks at it, the OPCW - and the Chemical Weapons Convention it's the enforcer of - faces either:
- an undeserved crisis to resist and ride out, or
- an opportunity to solve an existing crisis that's been sharpened to the point of undeniability.

Awareness of the problem allows for a solution, which denial would just forestall. The western powers benefiting from the current slant would deny it for as long as possible. Current OPCW leadership follows that lead. And "independently," Bellingcat is there to help squander this rare chance at a more honest world. After all, their proven talents make them "truth" leaders only in what supporters call a "post-truth world."

Looking to the Future
So to their former employers at a politicized OPCW and to these (self-appointed?) attack dogs, veteran CW inspector Ian Henderson and this "Alex" - and any others who have voiced or might voice agreement - are knowing liars who used fake science to try and get Bashar Assad off the hook for a hideous war crime. There can be no legitimate reason for this. Henderson was glad to see his bogus report leaked, in this view, knowing it would be used to attack the OPCW's honest work; clearly a villain. Higgins especially grows ever more specific on this, recently stating the core problem was always "a couple of disgruntled OPCW employees personal crusades to attack the work of an organisation investigating horrific war crimes." They were the enemy within. How could such reckless or compromised people get past the screening to ever be hired? And what if there are more?

As I've read in several places, the OPCW is openly not a "career agency," observing a general 7-year maximum tenure. This is why even Ian Henderson had to be hired back after a break in order to have that impressive 12 years experience. (and according to Peter Hitchens, "Alex" managed to get 17 years in before he quit in disgust amid the Douma investigation - is that 2x hired back?) I don't know the official and real reasons for the 7-year rule, but high turnover might help prevent nesting, the confidence of tenure, and willingness to oppose management. The Henderson and Alex cases could be seen as showing how long service and broad knowledge just makes for problematic employees likely to meddle where they don't belong.

One partial solution they might propose is shorter tenures. But if the manipulation piles up too quickly, people could catch on and rebel within weeks. Maybe it's more a question of who's involved than for how long.

Next up in the short future of the OPCW, I wouldn't be surprised to read about what they might dub "Veri-Science" for example. Bellingcat could partner with a well-funded European outfit linked to universities in a joint venture to improve the scientific input at the OPCW, among other trusted institutions like the ICC. They could either provide their scientific analysis directly or, more likely run a database of screened and green-tick "VS-checked" scientists better suited for "today's hostile information environment." Increasingly the Russians and other villains will seem to have bought off reality itself. "The old science is not enough," they could explain. "Its practitioners - good folks though most of them are - are bound to fail you. There are dictators violating the laws of physics to kill babies. There are nerve agents with bizarre, mutable properties being spritzed around European cities. And it's likely to get even weirder. This is why you need to stay VS-checked!"

Sunday, October 14, 2018

Assad Files-Caesar Photo Line-Ups: Genuine or Phony?

Assad Files 2018, part 4
Caesar Photo Line-Ups: Genuine or Phony?
October 14, 2018
(slightly rough)

Intro/Summary
In general, I've found these damning documents the "Assad Files" to be innocuous records of a government's response to the terrorist proxy war called the Syrian uprising. And that's upon careful review of the best examples provided by those trying to convince us of their value in proving regime atrocities. But in part 1 of this 2018 series, I was thrown for a bit of a loop by a relatively strong-seeming 2-point pattern. Two apparent line-up between detainees who died and bodies photographed at the right time among the Caesar photos - both detainees of MI (military intelligence) branch 227, both matching roughly for date with photo of alleged 227 detainees sporting the same 4-digit numbers.

It might seem impressive, but that's two cases of apparent line-up, in a narrow class (just one branch of military intelligence, in a certain 2-month span), between an enormous set of photos with sub-numbers, and a pool of dead prisoners of a less certain size (allegedly the same thousands in the photos, but maybe just a relative handful of different people). Far below is a section to explain the scale of numbers of likelihood of random line-ups.

It's presumed these two cases are just examples out of thousands of the same kind of paperwork-to-photo matches we'd expect if the stories of mass prisoner extermination were true. But it might be there are just these 2, or just a few more than that, which would mean almost nothing but chance can be at work.

For now and maybe forever, we cannot settle that with certainty. But with a little more analysis requiring this new post, I'm less impressed than I was at first. I still can't be certain what the truth here is, or prove anything, but I'll make the case that this might have been another carefully-framed illusion.

First, a visual summary of my timeline analysis suggesting a mismatch. In the graphic below are the alleged 2 matches (each with photo and linked memo, all in more detail below).


The green boxes here are what should line up, if these are the same men, and my photo date estimate, and understanding of collection dates are right. None of that is certain. I think this all refers to 4 men, not 2. But I can only offer a suggestion of mismatch, far from definitive. The rest of this post mainly explains how I decided this, and raises some notes on the way, adding up to some decent basis to doubt the matches.

Below is long, will take a while to clean-up fully. No one probably should read this end-to-end. But it can be skimmed, and should be by some people. It's organized so:

- first each detainee / pair / alleged match is explained with a section: basics and some case details considered, emphasis on timeline match (many numbers, averages, estimations involved)
- then my theory about how there may be 2 different number systems that happened to almost line-up and match pace for this 2 month span to explain both cases.
- then some related concluding thoughts, especially on how these alleged line-ups clash with an earlier explanation offered by "Caesar" himself.


Detainee(s)2040
Deceased Detainee 2040/0
We'll start with the earlier of the two apparent matches, not explained much previously. He enters the record via a document shown by Human Rights Watch in their December, 2015 report If the Dead Could Speak. There it's shared in photographed form (atop a portrait of Bashar al-Assad) and marked © 2013 “Caesar” collection. The summary of its content, as given there:

A note from the head of the 227 Branch noting: “During the investigation with [DETAINEE], his health conditions declined and he was given emergency treatment in the 601 Military Hospital. On June 2, 2013, the [DETAINEE] died after his heart and breathing stopped. He was placed in the morgue refrigerator, with the number ‘2040.’ Please bury his corpse…in coordination with the Burial Office in accordance with the written [DECISION] of the National Security Office.” With copies to three security branches. 

In the report, they cite a total of three such documents they were shown, all three claiming heart or breathing failure as cause of death. Of course, three isn't very many to support the claim this is used to explain thousands of deliberate murders. But it is consistent with such a system, and might just be a tiny sampling. Of those three reports, only this one is shown to be verified.

Here's the full letter, cropped from the photo, enhanced and sharpened, with minor redactions added (black boxes). In the spirit of hiding the victim's name (the only thing blurred out in the original), I blacked out also his mother's name, and possible identification numbers, all in the first paragraph. We couldn't do much with this information right now anyway. Translation etc. in more detail at ACLOS posting.

In short, HRW's translation was accurate enough, and didn't seem to skip anything relevant, except that he was stored "under the number 2040/0." They missed the zero, which is easy to do.

It's dated 9 June. It requests photography and then burial of the body "in a known place," in accordance with cited codes. "Attachment: A ‎Sealed envelope with the ID of the Mentioned person" Official-seeming stamp, and Amin 2511 notes "signed by the head of section/branch 227 also Head of the Intelligence Division "per procuration""

This document doesn't offer an obvious problem. It sounds like that is a detainee of theirs, and with all text present it's clearly the same man who dies after problems during an "investigation with him." But there's no mention of torture as the cause. If it did happen they took care not to mention it, even in this top-secret internal memo.

So for whatever reason, they say he died on the 2nd, and exactly a week later, on the 9th, the order is put out to photograph and bury him. There's one other to compare it to (see below), and he's held 6 days. Why wait a week to bury your secret detainees? Maybe they have a policy of waiting a week to try and contact family and get the body back to them. Maybe if there's no luck after that, they document and bury the guy. If so, all such cases should be 7 days later. So far it's just two for two.

Assessing HRW's Match With (Terrorist Hostage?) "227-2040" In their report, Human Rights Watch matches the deceased detainee with a "Caesar photo" victim labeled 227-2040. That's reasonable, in that the he's the only option if one were to find an exact match in the photos, for the 227 part and/or for the basic date. But the match is not certain, maybe because the photos simply don't show detainees in actual Syrian security centers, but someone else's prisoners.

Here is the person they refer to as the same one in that memo. SAFMCD cropped face-shot (a bit blurry) - 227-2040 (3) 7-6-2013. This is just one of the several better photos HRW will have seen (cropped from #3 in a sequence of however many).

Age: born 1976 as the memo says, so the detainee 2040/0 would be 36 or 37 in mid-2013. That could be the age of this man who - as usual - is in bad shape and hard to read. Many will look older than they really are, and some people started out looking young for their age. Totally inconclusive.

I notice his eyes are sunken, and teeth are in bad shape, maybe missing some. These are consistent with malnutrition seen in most photo victims. His face and shoulders don't evidence much wasting, but we don't see his ribs or hips, and he still may have been poorly fed, just for a shorter time than some, or with peculiar effects. It's alleged branch 227 and the rest starve most detainees...

HRW: "His body shows purple bruising in the throat, abdomen and lower legs, cuts on his lower legs, and a cut on his forehead."

I can't see a cut on the forehead, but maybe it's too high up. Lower body details unknown. As for the purple neck bruising, he may show a different and milder form of some common neck injury - bruising/burning/unclear, worth more study. But mostly rather, his body shows a purple tint all over in the parts we see, and likely the rest. The lips especially are deep purple. That means cyanosis, from prolonged lack of oxygen in the blood. Most of the victims in the "Caesar photos" display this to some degree, and often to the extreme. It's not something "torture" usually causes.

Anyway, we refer to the same person here, but we don't agree that he's the same man described in the memo. I don't suppose I can prove this, but …

Date Mismatch?
HRW's report stated "Photographs of Detainee 2040 reveal that his body was photographed on June 7, 2013." If so, then why is an order to take the photo only issued on June 9?

Rather, the photos they identified as relevant were put in a folder dated June 7 (7-6). This will usually be the date of photo collection, of photos taken earlier, since last collection. This would mean a photo taken June 9 or 10 is simply too late to be included.

But the basic logic of the system isn't totally clear yet, it seems to change at points, and might have exceptions. Here's my big timeline of seen "hospital numbers" compared to photo folder dates, for the final and heaviest 9 months (not the whole span back to 2011). (hospital number explained here - it means  either false heart-attack-death-report # or, I think, unidentified found body #). This case and some others with dates are pinned on at the bottom (new window for readable-size view). I'm looking for any more dated entries I can place to help fill this in, but they're pretty rare.


See below, on the left in the span under 1-11-2012 (purple) that includes entries (allegedly) from days later than that, and many others after it. There, 1 Nov. seems like a start date for collection, in a folder named first and added to on later dates. The same seems to apply to 1-8-2012, off-frame here. But that's not well-illustrated yet, and both dates are far from gospel.

Patterns in mid-2013 will be more relevant, and it seems like the MO changed somewhere before that. The same Dec. HRW report shows a May 24 order to photograph 11 bodies that came out as numbered 2614/b-2624/b on this timeline. As we can see here, a whole lot of bodies dated June 4 (about 1,800-1,900) were photographed before that, running back - it seems - to March, when the last folder was compiled. It should probably run up to the collection date, including photo taken on or just before 4 June - unless perhaps the gathering session was cut short, with the last few days still to grab, for example.


So the photos put in a 7-6 folder should be gathered three days later, and cover just those three days, plus any missed before. How it seems to cover app. 250-300+ bodies suggests it might cover more than 3 days, likely including quite a few entries from June 4 and earlier, because the last session was not completely current.

But more than likely, 7-6 brought things current, and none of the photos in it was taken after the 7th. Anyone snapped on the 9th or 10th would then have to wait for the sizeable 24-6 folder, the next one compiled. So, just by the apparent logic of folder dates, the provided "Caesar" photo was taken some days too early to match with that memo.

There's another even less certain way to check for a likely date. I estimate 227-2040's hospital number at around 3000/b (proportionally between the two closest 227 bodies with seen H#s, and presuming an even distribution of 227-stamped bodies). That would be in the middle of the smaller 7-6 folder's span (whatever days that actually ran).

With an overall average of 33 bodies a day, some 350-400 bodies before 3,000/b = 10-12 days after the May 24 memo, or June 4-6 is the most likely span for the 227 photo - 3-5 days too early to match with the June 9 memo. But this remains uncertain, not a very reliable estimate (but better than nothing, at least). Maybe the rate here was slower, or this folder was added to after its start date so it's a match. But suggested line-up and the apparent logic of folder dates agree in their uncertain indication that the memo comes a bit too late to match the photo.

That would present this coincidence: 2 different dead men wound up stamped 2040, at Hospital 601, within a few days of each other. That might sound unlikely on first blush, but see below for the scale of things to realize it's not so unlikely at all.


The Other Case: Detainee(s) 2668

2668/0 = (Terrorist Hostage?) "227-2668'?
Another case from two months later was covered in more detail in part 1. It was published by the CIJA (Committee for International Justice and Accountability) via an August, 2018 Channel 4 program. The relevant document they shared has very similar content. In this case, a "terrorist" detainee (different wording) of branch 227, is most likely the "he" who died of heart and breathing failure at hospital 601, after questioning. There's some ambiguity from 95% of the text preceding "he" being redacted (whoever was referred to last in that black box). But comparing to this earlier case, it's likely the same story, maybe with some extra details not worth seeing on just how this bad state finally came about.

It says he died on July 31,and was ordered photographed and buried in an August 6 report. In between, he was put in the cooler with a number 2668/0. That (minus the zero) was matched by Channel 4 investigators with a starved guy with eyes gouged out, 227-2668, date not clear but (as I found) pretty current with the memo. That's two cases where 227's numbers ate least are current with two dead detainees - are they just the same thing then?

To me it seemed likely the dead man was another character introduced, one of the mostly-dead people dumped by the terrorist, one of whom was caught in the act and became the "terrorist" under questioning. Maybe one dumped body still had a pulse, but then died in this hospital, and was documented as unidentified. But the 2040 case weakens that option - a dead 227 detainee with the same kind of number has details, an ID card, he clearly dies, still gets held a week, and processed the same way. Most logical; the same story happened twice.

This memo is clearly a different format, some kind of fax, not the stamped official form seen for 2040. The requested forwarding is similar for both, but not exact: 2040's form in June is forward to: division/branch 291 (in "reference to your letter No. 56122 dated 7/6/2013, for view"), 248, 294. This one has: something 248, 294, 217, and a shorter entry blacked out. (291?)

As with the first case, there's a delay here - not 7 days, but 6. So maybe the rule is try to contact his family for about a week, then document and bury the body, or to get the whole thing done within a week.


So if this all refers to one man - there he was under questioning, already weak from starvation, and they gouged his eyes out … and if the blacked out parts explained any of this, it would be odd to black it out. In this case, there's no purple, coughing blood and mucous, or any other chemical signs. That all remains super-common from Nov. 2012 on, but becomes less common in the final stretch. Instead, eye-gouging appears suddenly with most victims, closer to the end in mid-August 2013.

But anyway, they then rush his to the ER as if to keep him alive? And he wound up displaying no signs of medical intervention, like washing the wounded eyes, etc.?

There are hundreds in this span with eyes gouged out. It looks extermination-oriented, but maybe it was a whole lot of interrogations gone overboard, like with this guy? No, I doubt that - for the rest and for him.

Time Mismatch?

Aug. 6 order, photo presumably that day or the next, compared to folder 000. That's not obvious. But I can say 000 is somewhere between July 27 and what seems to be a folder dated August 6 (just called 6, but containing body numbers running up to those in a final 14-8-2013 folder, so I take it as meaning 6-8, or Aug. 6). The folder sizes here (from my hard-to-assemble and 99% complete database):
- 000 = 143 photos
- 6(-8) = 62 photos
- 14-8 = 126 photos. 
He comes just another entry that's in Aug. 6, so late in his span of 143.

When was 000? Considering just 62 photo gathered on 6-8, that's like 2 days worth of bodies in the usual flow. So the last collection (000) might be about August 4. Otherwise, right between the dated folders makes most sense. That would be August 1 or so. 000 by usual rates = 4-5 days' worth of bodies. From July 27/28, that should be Aug. 1. Some implied entries missing photos are mixed in somewhere... So we could say best estimate for 000 is Aug. 2-3, give or take a day or so.

Best single-day guess: photo on July 31. As usual, he appears dead perhaps 1-2 days at most, or longer if under refrigeration. Now, to be the body in that memo, he has to die on the 31st and only pass under the lens 6-7 days later, august 6 or 7. He would have his photo collected later yet - too late for the 000 folder, and maybe even for the Aug. 6 one. He would likely end up in the final August 14 folder instead.

The date of 000 remains unclear, and if that's the date of last collection... the numbers might also line up better, or even be the same number and same man entirely, as alleged. But again, his body/ hospital number and the folder date both suggest the photo is too early to match the memo, and here by a bit longer, more like 5-6 days. 

And both clues agreed in the same direction in the other case above. Hm.

Two Number Systems?
A Hypothesized /0 System
Both documents add an unmentioned /0 to the body number. It looks like a /. and coming at the end of sentence, it looks like the end of the sentence. This is a traditional "Eastern Arabic" number system commonly used in the region, with its easily-missed zero. 

There's also a slash before the number, but I'm inclined to ignore that as marking a number here: it's worthwhile, as the order of reading changes at each slash. The usual right-to-left order is maintained, but within the slashes, number blocks are read left-to-right. So "number / 2040 / 0" and "number / 2668 / 0" is how it's given in both cases. 

Those numbers seem to be issued in the same system, but does it really link to those men in the Caesar photos? If so, it seems 0 is the hospital's code for 227's share of the body flow, and they just use the branch's own ID number. Maybe 215 gets their dead prisoners stored with their current detainee/body number with the suffix /1, and so on. That's the implication of the CIJA case 

One other option I held out from the start was two different number systems happening to line up, at least roughly. Seeing that happen twice about 2 months apart did seem a challenge, but not a great one. I've come back around to this theory as my best explanation, for now at least.

A number system that could explain the pattern under study is one for all deaths IN military hospital 601, as opposed to those special cases logged out back. It would include the occasional prisoner who dies after a struggle in the ER (not ones found dead, or meant to die), delayed combat deaths from both sides (but mainly the government side), civilians mortally killed in shelling, etc. Maybe a few are "Caesar photo" victims who were found dumped among the dead but with a faint pulse, but then died in the ER. 

In all but the latter case, the number wouldn't usually replace a name, as the victims are identified or likely to be, only stored short term with bodies claimed by family, ideally. The number might just be for reference, a running death toll. It would probably refer to crisis-related and not natural deaths, starting at 1 around March 2011. (this is how the unidentified body numbers work; they start low at the conflict's start) 

Why 0? Could mean detainee deaths, with others given numbers like /1 for killed civilians, /2 for killed security forces, and /3 for killed militants. /4 would probably be better for prisoners than the non-number 0.  Maybe it just means hospital 601, the one that did all the counting at first (hence 0, the original0? The zero would be redundant in-house, but useful when combining the tolls at each hospital (others using the same numbers but getting suffixes /1, /2, etc.)  

In such a system, body #2039 might have been a girl who died at hospital 601 after her school was hit by a terrorist mortar shell, for example. She might be 2039/1 for example, or /0, depending - but there would be just one number per body, with the right suffix (so if 2039/1, there would be no 2039/0, etc.).  

I'm just hypothesizing here, but as far as I see, the speculation has to be about correct. Otherwise, it would seem the CIJA matches are genuine, despite the doubts and counter-clues and their shady track record. Everything else to me says these things do not connect, but if not, then something else would have to explain those 2 numbers emerging then, and I don't see much alternative to something like this.

How It Would Kind-Of Line Up With "Caesar's" System
So let's say this system - that really might and probably should exist - would happen to reach death number 2040, with a detainee of branch 227, at about the same time the "Caesar photos" unidentified bodies credited to branch 227 also reached 2040.

So we'd have 2040 deaths logged at hospital 601 by June 2 of 2013. The rate of deaths in that time would start slow and then accelerate as the militancy expanded. Quite likely a smaller half of these deaths were in the first half of 2013, while the slight majority took the first 22 months to accumulate. That's just a guess, but would yield a 2013 average of around 160-170 a month. It might be low in the winter, like 90/month, and extra-heavy in June and July, like 250/month, amid escalated fighting, especially over Jobar and east Ghouta.

The second coincidence about two months later (span June 9 to August 6) just means the two systems didn't happen to pass briefly, but stayed roughly synchronized for several weeks - the same basic pace was kept between the 227 bodies and everyone who died at the hospital. Their system would log 628 fatalities of all classes combined in app. 2 months (2040 - 2668), an unusually high rate of about 300-320 a month at this time. Considering the above, the uptick in deaths could be even sharper than that rough guess.

as for the "Casear photos," likely unidentified found bodies of immense number, which seem to directed totally to the garage behind  Hospital 601 - In this same span, my H# timeline suggests that system documents more like (est. 3000/b - 4738/b) 1,750 unidentified bodies As it happens, the minority stamped 227 also rose by about 600 in the same 2 months (comparing 2040's estimated H# and 2668's seen H#). At close to 1/3, that's a pretty normal ratio for 227. In total, the photos at the SAFMCD site break down so by (alleged) MI branch:

* 215 = 3,556
* 227 = 2,047
* next 3:
** Air Force Intel - 350
** 216 - 297
** 235 - 128
* the other folders/branches hardly count or don't (misplaced 215s, unknown branch, etc.)

So 215 = 56% - 227 = 32% - next 3 combined = 12%

Now this, used to project the expected number and proportions of dead in the span between our two deceased detainees in the hypothesized Hospital 601 /0 number system. Nothing exact, but useful in showing the rough correlation of the red bars (est. 560 vs. 628), and likelihood of many matches here - if very many of those who died inside the hospital were 227 detainees. And it might be just the two.



Both photos seeming to come too early to match suggests the hospital's system of total deaths passed the current 227 number just a few days behind it, and kept approximate pace for about two months, staying about as far behind then. Therefore, it would keep pace for a bit before and after this span as well, but would get increasingly out of sync further from this zone..

Here it seems the hospital's number grew faster (628 to 560), so the second entry should line up better, but things just aren't precise enough yet on any end to settle points like that. Likely there are more 227s than average in this span. In fact:

The 7-6 folder includes 160 from 227, and only 73 from branch 215, of 256 total. The other folders are less 227 heavy or have none, but tend higher than average.

24-6 folder, total: 544, includes: 215: 267 - 227: 213

7-7 folder, total 439, includes: 215: 279 - 227: 117

26-7 , total 218, includes: 215: 78 - 227 = 106

later 000 (Aug. 1?) folder, total 143, includes: 215: 0 - 227: 117

6(-8)-2013, total 62, includes: 215: 62 - 227: 0?

14-8-2013, total 126, includes: 215: 55 - 227: 45

The two prisoners who die happen to be 227 - in two cases, maybe more. Is that a lucky break? (and how lucky?) Or, perhaps, 215 and someone else had a couple detainees die in this span as well, but they were put in the hospital's cooler under numbers in the same sequence with these 227 guys and whoever else, and NOT based on their branch 215 etc. ID. That is, maybe others were found but didn't line up, so the CIJA et al. didn't mention it... this would be par for the course if those investicutors (prosecution-minded fake investigators) did find such a thing.

If this scenario were true, it means compared to the large number of people dying in hospital 601 in this span - a bit over 300 a month on average, from all causes combined as I propose - three times as many starved and purple found bodies were photographed in the garage area during the same span. And it did this constantly through late 2012 and 2013, to the tune of about 1,000/month on average. Whatever crime system is behind that stream of death, this gives an idea of the scale of it.

The sheer number of bodies with their attached numbers makes it likely enough that  two men stamped 2040 and two stamped 2667 passed through the same hospital within a few days of each other. Virtually every number prior to that had already been used in the hospital's inner system, and several times among the victims out back. The hospital number there is debatably relevant, but it too gets linked to false detainee death reports, and might be used in the same way - see below. Every number up to 5,000 gets used twice here, and a few lower numbers get used a third time (it runs 1-4,999 first plain, then again with /b, then with /another letter(unclear - s?), allegedly running up past 1,000). And then each alleged MI branch responsible for killing their prisoners on such a scale issues virtually every number up to whatever. And there are nine branches to issue numbers. 

For example, over the whole span, the number 458 would be passed seven times between all sources in that graphic above. Once in the "/0 system" and six times in the "Caesar photos" system:
as unidentified body number three times, and also with photo victims 215-458, 216-458, 227-458. So there are 6 chances for the /0 system's body #458 to line up with one of those.

Lower number should be repeated more time with the lower-killing branches included, but 215 and 227 are missing a lot of lower / early entries, so the most common numbers come out at best like 59:
Branches 227, 216, 251, 220, 235, and 248 each have a "detainee" #59. 215 does not (that's included as such). These six plus 59 used 3x as body number in this system, and once in the hospital's inner system = ten bodies logged as #59, one way or another, at one point or another, just at this one place.

Other numbers like 1441 just get repeated five times total (just twice as hospital number, once each for 227 and 215, the only two huge-yield branches, and once in the /0 system). The numbers in question here (2040, 2668) are of this kind - only 5 instances. And numbers 5,000 or past are used maybe zero times. I've seen a number past 5,000 written on a card with a body once, but it seemed odd, out-of-place, and everything else says they stop just before that and re-start with a new letter suffix for body numbers, and no other system is seen ticking that high. 215's detainee/body numbers stop in the low 4,000s, and everyone else's stop far lower than that (except the stray, misplaced-seeming high numbers found here and there).

Usually, the 4-9 outer repetitions of a given number won't come close at all to lining up, on the calendar, with the same number on the one system running inside the hospital. But with that many systems running at once, it's likely at least 2, and even "several" cases will. They probably wouldn't line up down to the day, but close enough to explain the two cases of possible or near-matches we've seen. And so I propose something very much like this does in fact explain it.

Some Closing Thoughts and Overview
If this is the kind of coincidental line-up I propose, it could be tested against the documents by anyone with access. There wouldn't be any non-227 "detainees" that roughly match with the hospital's /0 system in this span (e.g. branch 215 bodies were numbered in the 3100s at this time, and no one else issued number so high, except AF intel, but just a few and sporadically, and at random times -allegedly. Let's skip that for now). And even 227s will fail to line-up outside this time-span. Investigators well be able to find a couple more detainees who died around the time their own numbers line up the same way with some branch of the bodies out back, even if these are two different systems. One with enough data may could test that against the hypothesized /0 system for logical consistency - is the number too small or too large to make sense at that date? Or does my theory still make sense even with that added point? 

But if this is just a trick here, one could not locate the thousands of death reports suggested by the December order to document every death in custody see part 2), to show in thousands of cases heart attack claimed, body held with current branch number regardless of the date, that lines up with the numbers on those starved bodies ... I suspect there are only dozens, not thousands, of such reports, because there was no systematic killing. and it's probably just these 2 and possibly a couple more that have that convenient feature  of seeming to line up with photo victims.

The later case is said to be just one of at least "several" shown the Channel 4, each with "matching Caesar photos." How well these others matched is unclear. As noted, every number from 1 to whatever was used 5-10 times here, so it means nothing that they found a matching number in several cases. If their interpretation is right, there should be thousands of these matches, all being number AND date matches. But maybe all but 2 or 3 of these "several" are just some random rare detainee death that has a best of 1-3 matches in the photo set, but the dates don't even come close to matching, so the CIJA don't give out any details, even to Channel 4

As shown, that "several" might be the few sheets on top of some binder, or maybe the whole binder as well - that's unclear. The two we see (one presumably being the one included on the show) are both 95% redacted. 



But no, we'd need more information - more examples with clearer matching details, a better sense of the timeline that winds up a true match, etc. - before it would be wise to link these benign-seeming documents to that horrific crime spree.

Also consider how these 227 matches fly in the face of - or combine awkwardly with - a previous explanation offered by the central witness in all this, "the Defector code-named Caesar."


As the 2014 Carter-Ruck report was paid by the Qatari royal family to explain "the procedure for documentation was that when a detainee was killed each body was given a reference number which related to that branch of the security service responsible for his detention and death." That's the top dual-number in this card shown at right, as a refresher. "Caesar" himself later claimed it was a prisoner number issued on order of arrest. But noting how every prisoner would then be killed in their order of arrest, the Carter-Ruck report, Human Rights Watch, and others have overlooked that claim to decide this number is issued only upon death. It's a branch-specific dead body number. But opinions differ, even among those blaming "Assad."

Then, the Carter-Ruck report continues, "When the corpse was taken to the military hospital it was given a further number so as to document, falsely, that death had occurred in the hospital." They were citing the explanation provided by "Caesar." (p. 13, under "V. The Evidence of “Caesar”") This will be the hospital number as seen above, the number used for the big timeline further above, that runs to 5,000, then re-starts with a /b. HRW and others have repeated this over the years, and it seemed like the evident truth. 

But in these specific cases considered in this long post, the CIJA now propose hospital storage number is adopted from the responsible MI branch # (issued at death? So only then?). So their detainee/body # 227-xxx becomes xxx/0, maybe with other branches swapped out with 1s and whatever. The bottom number has no clear use in that scenario. If it had much value like Carter-Ruck heard, it should be sent back to MI leadership for their reference, as the new thing added at the hospital. But only their own alleged prisoner number (already known) is re-affirmed here. That seems pointless.

So "Caesar" and the CIJA may contradict each other here - or not. The logical way they might correlate that so no one is wrong: there's  a number for the prisoner/stored body (top), and one for the covering paperwork (bottom). A card shows them together for correlation. So the late case is stored under 2667/0, and then given a false death report numbered 4738/b. Why not file the paperwork conveniently under the number used for storage? Who cares? It's going to the Hague!

And it's not the biggest or clearest deal I've seen. But it does seem like both numbers are cited for the same basic purpose because too many people are trying too hard to take these heart attack reports (alleged thousands of them, at least a few proven) and connect them to those thousands of very real dead bodies. Different people link them randomly to every number they see, at different times, making short-circuits likely.