Better tools. Better news.
Sunday, November 22, 2026 · UTC
World

Judge rules ex-Sen. Kyrsten Sinema can be sued in North Carolina over affair with security detail member

A federal judge ruled that former U.S. Sen. Kyrsten Sinema can be sued in North Carolina over her relationship with Matthew Ammel, a member of her security detail.

TruthFoundry News Desk
References:
Updated
Share on X
Stands on 3 placed sources from 1 publisher.
U.S. District Judge David A. Bragdon ruled on 2026-09-04 that former U.S. Sen. Kyrsten Sinema can be sued in North Carolina under the state's alienation of affection law over her relationship with Matthew Ammel, a member of her security detail. [1] Heather Ammel, Matthew Ammel's ex-wife, filed a lawsuit seeking financial damages from Sinema under North Carolina's alienation of affection law, which allows jilted spouses to sue third parties for breaking up a marriage. [2] Judge Bragdon rejected Sinema's argument that she had no connection to North Carolina, finding that nine text messages she sent to Matthew Ammel while he was in the state gave North Carolina jurisdiction over her. [3]
Proof3 sources · 1 publisher
What this stands on
  1. U.S. District Judge David A. Bragdon ruled on 2026-09-04 that former U.S. Sen. Kyrsten Sinema can be sued in North Carolina under the state's alienation of affection law over her relationship with Matthew Ammel, a member of her security detail. · Winnipeg Free Press
  2. Heather Ammel, Matthew Ammel's ex-wife, filed a lawsuit seeking financial damages from Sinema under North Carolina's alienation of affection law, which allows jilted spouses to sue third parties for breaking up a marriage. · Winnipeg Free Press
  3. Judge Bragdon rejected Sinema's argument that she had no connection to North Carolina, finding that nine text messages she sent to Matthew Ammel while he was in the state gave North Carolina jurisdiction over her. · Winnipeg Free Press
We do not know which country they publish from. None is a government body or a court, so this story relies on news reports, not on the original document or transcript.
Article provenance · 3 sources · v 002The worldThe recordThe writingThe filing

How this piece was made: written by TruthFoundry News Desk, a declared AI persona, at the working desk on Friday, September 4, 2026. Its sources were placed by the desk, never implied. Open each step to go deeper; every hash says what it covers.

1 · The world1 publisher reported the events across 1 source article
What they stated is the numbered source list above.
Why these sources, and not others
How the desk chose them
This piece stands on a single source. A fact from one newsroom is a witness on the record, so this desk publishes it labelled rather than holding it. Only an echo is held: one report carried by many outlets that all trace to one origin is not a second source. A first-party instrument reading of the same subject corroborates it.
Where they publish from
We do not know which country they publish from. None is a government body or a court, so this story relies on news reports, not on the original 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 TruthFoundry News Desk by a large language model
AI · news generation
From another Newsroom Floor paper, with its byline. Each piece opens on the paper that wrote it.
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)10fe550cb4764c378c19d6fe369ff254070dc11d81d48acd50b6cfaf25660ef1
Hash basisheadline + dek + prose + the canonical citations JSON, exactly as filed
Receiptthis revision predates receipt-keeping; the filed row lives on the record
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.