What went wrong today, on the record
Thursday, November 12, 2026 · UTC
Conflict

Airstrikes near Sanaa kill 33, Houthi-run health ministry says

The count rose from 27 to 33 through the day. The Houthi-run Saba agency blamed Saudi Arabia for the strikes on Bani Hushaysh. Saudi Arabia said it was investigating. Reuters could not verify the toll.

Conflict Correspondent
References:
Share on X
Stands on 21 placed sources from 3 publishers.
Airstrikes hit Yemen town, killing dozens
Airstrikes hit Yemen town, killing dozens AI illustrationhow this picture was made
Airstrikes near Sanaa killed 33 people and wounded 39, the Houthi-run Saba news agency said.[1] The strikes hit Bani Hushaysh, a town east of the Yemeni capital.[2] Outlook India reported the same toll of at least 33 killed and 39 injured.[3] The source of the figures The casualty figures come from the Houthi side. Saba attributed the strikes to Saudi Arabia.[1] Houthi authorities blamed Saudi Arabia for the attack.[4] Reuters could not independently verify the account.[5] Saudi Arabia's Center for International Communication said it was investigating the report.[6] Outlook India also reported that Saudi Arabia was investigating.[7] An earlier count The toll rose through the day. The Deccan Herald, carrying an earlier Reuters report, gave at least 27 killed and 36 wounded.[8] That report said the strikes hit homes in Bani Hushaysh.[9] It said Saudi Arabia did not immediately comment.[10] The later figure of 33 killed and 39 wounded replaced it.[1] Who was killed Most of the people reported killed were women and children, Reuters reported.[11] Outlook India carried the same description of the dead.[12] Victims, including first responders, remained trapped under rubble after the strike.[13] The director of Sehatuna Hospital said medical responders were killed in follow-up strikes.[14] The wider fighting Fighting between Saudi Arabia and the Houthis resumed in July 2026.[15] That broke a truce brokered by the United Nations in 2022.[16] Outlook India reported the same sequence, a 2022 truce and a return to fighting in July 2026.[17] The Houthis said they had carried out missile and drone attacks on Saudi targets in retaliation.[18] More than 200,000 people have been displaced since the fighting resumed, as of October 2026.[19] Outlook India gave the same figure.[20] The war in Yemen has produced one of the worst humanitarian crises in the world.[21] What is established Two outlets carry the same toll, 33 dead and 39 wounded, and both trace it to the Houthi-run health authorities.[1][3] Neither has an independent count.[5] The strikes fall in a war that resumed in July 2026 and has displaced more than 200,000 people since.[15][19] The Saudi side has not confirmed or denied the strike; it has said only that it is investigating.[6] The report of medical responders killed in follow-up strikes comes from a hospital director in the Houthi-held capital.[14]
Proof21 sources · 3 publishers · signed
What this stands on
  1. Houthi-run Saba news agency stated Saudi airstrikes near Sanaa killed 33 people and wounded 39. · al-monitor.com
  2. The reported airstrikes hit Bani Hushaysh town east of Sanaa. · al-monitor.com
  3. At least 33 people were killed and 39 injured in airstrikes near Sanaa, Yemen. · outlookindia.com
  4. Houthi authorities blamed Saudi Arabia for the airstrikes. · outlookindia.com
  5. Reuters could not independently verify the airstrike casualty account. · al-monitor.com
  6. Saudi Arabia's Center for International Communication is investigating the airstrike report. · al-monitor.com
  7. Saudi Arabia was investigating the airstrike report. · outlookindia.com
  8. At least 27 people were killed and 36 wounded in alleged Saudi airstrikes near Sanaa. · deccanherald.comIndia
  9. The airstrikes hit homes in Bani Hushaysh, east of Sanaa. · deccanherald.comIndia
  10. Saudi Arabia did not immediately comment on the alleged airstrikes. · deccanherald.comIndia
  11. Most people reported killed in the strike were women and children. · al-monitor.com
  12. Most reported fatalities were women and children. · outlookindia.com
  13. Victims including first responders remained trapped under rubble after the strike. · al-monitor.com
  14. Sehatuna Hospital director stated medical responders were killed in follow-up strikes. · al-monitor.com
  15. Fighting between Saudi Arabia and the Houthis resumed in July 2026. · al-monitor.com
  16. Renewed fighting shattered a 2022 UN-brokered Yemen truce. · al-monitor.com
  17. Yemen fighting resumed in July 2026 after a 2022 UN truce. · outlookindia.com
  18. Houthis claimed retaliatory missile and drone attacks on Saudi targets. · outlookindia.com
  19. Over 200000 people were displaced since fighting resumed as of October 2026. · al-monitor.com
  20. Over 200000 people were displaced in Yemen since fighting restarted. · outlookindia.com
  21. The Yemen war has caused one of the worst global humanitarian crises. · al-monitor.com
The one we could place publishes from India. 2 could not be placed by their address. None is an official body: that part stands on reporting, not on the underlying document or transcript.
Article provenance · signed receipt ✓ · 21 sources · v 002The worldThe recordThe writingThe pictureThe filing

How this piece was made: written by Viktor Lindahl, a declared AI persona, at the working desk on Wednesday, November 11, 2026. Its sources were placed by the desk, never implied. Open each step to go deeper; every hash says what it covers.

1 · The world3 publishers reported the events across 3 source articles
What they stated is the numbered source list above.
Why these sources, and not others
How the desk chose them
We do not pick publishers. The desk reads the fact record for the event, groups the reports that carry the same claim, and writes from that group. Within it, what rises is an interest score: how much attention a claim is drawing across the record, and how recent it is. That measures INTEREST, not truth and not authority, and a widely carried claim is not a truer one. A piece is held unless at least 2 INDEPENDENT origins carry it, where outlets running the same wire copy count as one origin, not many. We do not currently ingest transcripts, filings or press releases directly, so unless an official body appears in the list above, this piece stands on reporting about the document rather than on the document itself.
Where they publish from
The one we could place publishes from India. 2 could not be placed by their address. None is an official body: that part stands on reporting, not on the underlying document or transcript.
The source articles and their ingest receipts
Every article was fetched, extracted and analyzed upstream, and each of those legs was signed with its own key. This opens the record's own receipts for them.
2 · The recordextracted those reports into signed fact rows
AI · semantic search
The facts this piece stands on were selected by semantic search over the record: AI embeddings match each section's query to fact rows by meaning, not keywords.
This newsroom read the facts through the record's public door, and the door signed the read. The read receipt was not captured for this early revision.
3 · The writingwritten as Viktor Lindahl by a large language model
AI · news generation
The automated line wrote this as Viktor Lindahl using a large language model.
The prompts, verbatim
System instruction (the grounding rules)

The assignment: persona voice contract + this desk's standing instructions + the numbered facts
3b · The picturean AI illustration, hash-pinned and signed by the art station
Painted after the piece was written. The picture sits OUTSIDE the story's signed content hash, so changing it never rewrites the record.
The caption (written for the reader by the art director)
Airstrikes hit Yemen town, killing dozens
Painted by
mordiem:flux-2-max on mordiem, at 2026-11-12T00:12Z. Scene directed by @cf/meta/llama-3.3-70b-instruct-fp8-fast.
The paint prompt, verbatim
The scene the art director wrote
A damaged residential street in Bani Hushaysh, near Sanaa, with rubble and debris scattered, a few people in plain clothing walking among the ruins, under a harsh, overcast sky with a single, ember-orange glow from a damaged vehicle, deep shadows cast across the scene.
Inside the house scaffold (the fixed style + safety clauses), the full prompt the painter received
A damaged residential street in Bani Hushaysh, near Sanaa, with rubble and debris scattered, a few people in plain clothing walking among the ruins, under a harsh, overcast sky with a single, ember-orange glow from a damaged vehicle, deep shadows cast across the scene. Rich painterly texture, visible brushwork, coherent single scene, cinematic light, a restrained ink-and-wash newspaper palette. Coherent single scene, wide composition that FILLS THE ENTIRE FRAME edge to edge: no black bars, no border, no letterboxing, no empty margins. Every person has a natural, fully painted face with real features: never faceless, never blank mannequins, never smooth featureless heads. All people are fictional and resemble no real public figure. Strictly no text ANYWHERE in the image, whatever the model: no letters, no numbers, no typography, no signs, no road signs, no billboards, no neon signs, no storefront or shop lettering, no marquees, no banners, no placards, no posters, no license plates, no printed pages, no screens or displays showing any text or UI, no brand names, no company names, no product names, no watermark, no logos. Plain unmarked clothing on every person: no lettered vests, insignia, badges, or name tags. Plain unlettered bodies on every vehicle, truck, screen and vessel. No such surface appears at all: not lettered, and not blank either, because an empty screen or billboard leaves the figures around it reacting to nothing. If the subject is a company (a chipmaker, a carmaker, a bank), draw its WORK and its WORLD - the factory, the lab, the product, the people - never its name or its logo on a sign.
The picture's own pin (SHA-256 of the exact bytes served)
1a736c91c1d2efeab62e4feb1bfe1a2718bbca6aa0885cd6a627c9e0d319824b
4 · The filingwritten to the permanent record
Once published, the piece is written to the permanent record. Its receipt - proof it has not changed since - is under Integrity, below, and the button there re-checks it in your own browser.
Integrity
Content hash (SHA-256)1280317f294ef335d6a9f1aea4a74b1e068631220c0990283e2558c324a8d637
Hash basisheadline + dek + prose + the canonical citations JSON, exactly as filed
Receipt signature (Ed25519)10k-eQoUB3uQbfwUGdhg7gwWOF15gU8e9MugcUmC0ve4CQnDw39lqpaDRf5uXhq3tmyRv8gfLvJCzsAgCtnBDg
Signing keybMUigy8O0jOnBxQ4Sc-5lwhIZ8LQVAhxMbR7qESVuUE
SignerDRM3 · data-extract v1
Filed asingest:raw_newsroomfloor.stories v1
Slice hashaea7140d16a6ab84e62d61d28e60919481d7f055564184bd73486374adcc7f06
Machine readablethe full proof, JSON
Verify

A signature proves who filed this and that it has not changed since. It never makes a claim true.