Website Interference Allegations Surface in Detention-Contract Reporting
After noticing missing sentences and altered passages, LeRoy Nellis says his detention-contract reporting appeared to change on the live site. This article reports those observations as allegations, not as a proven intrusion.

An Editorial Problem Becomes a Security Question
LeRoy Nellis reports that he first noticed small discrepancies between articles he had written and the versions appearing on his website. A sentence would be missing, or a paragraph would read differently than he remembered. At first, he considered ordinary causes: a plugin conflict, a formatting error, or a content management glitch.
According to Nellis, the pattern did not fit routine website breakage. He says entire sections of investigative material disappeared, prompting him to treat the issue as possible interference rather than a publishing mistake. That conclusion is reported here as his account.
The Reporting Context
The page’s subject is tied to Nellis’s reporting on intergovernmental service agreements and detention-related contracting, including coverage associated with Williamson County. The timing matters in his account because the material he says was affected involved investigative reporting, not random posts.
This article does not identify a perpetrator and does not assert that any specific agency, contractor or individual altered the site. Establishing responsibility for website changes would require logs, access records, hosting data, backups and forensic review.
Why Unexplained Changes Matter
When investigative text changes without a clear editorial explanation, the harm is not limited to broken formatting. Readers may see an incomplete record, sources may appear unsupported, and the publisher may lose the ability to show what was originally published. Even accidental changes can damage credibility; deliberate changes, if proven, raise more serious concerns.
Nellis’s account highlights a practical safeguard for publishers: keep off-site backups, preserve revision history, record timestamps, and document discrepancies as soon as they appear. Those steps do not prove a hack, but they create evidence that can be examined later.
What Can Be Verified
The verifiable questions are concrete. Did the page content differ from prior saved versions? When did changes occur? Which accounts or systems had access? Do server, plugin, or hosting logs show edits or compromise? Until those records are reviewed, the strongest accurate description is that Nellis alleges unexplained and possibly unauthorized changes to his reporting. This rewrite keeps that distinction clear while preserving the same URL.