CONCERNS, RECORDS AND RESPONSES
The mandamus case grew out of earlier concerns about Store 131, public-records requests and disagreements over the City’s responses. Read the court dispute, or follow that wider history through the eight issue guides.
Start with the recommended reading path or follow the connected Store #131 case path.
THE COURT CASE THAT FOLLOWED
Kyle Moring asked the court to compel the City to provide public records; the City asked for dismissal. The dedicated guide places the parties’ filings, all 13 counts, later productions and three documentary comparisons together. A party’s filing is not a judicial finding, and a delivery or search result does not by itself establish completeness.
Read the complete mandamus guide and source records →
These stable links now lead to the same count in the focused guide.
01 / ENVIRONMENT & PUBLIC HEALTH
Two separate threads belong here: Store 131 conditions and complaint routing, and the City-owned Southwest wastewater plant operated by Pilgrim’s Pride. Read each through its own records.
Routing a complaint does not establish an investigation or confirmed violation. The plant’s permit and agreement describe an operating relationship; they do not resolve which records the City maintained or searched in a later request.
DSHS received the complaint June 30 and inspected July 1. The report describes approximately 18,000 square feet of roofing removed before a survey, a work pause, and subsequent notification and testing. The later limited survey found asbestos in remaining silver mastic at HVAC flashing outside the then-current work area.
Read entry, limits & sources →EPA routes the complaint to TCEQ. Hodo emails James on October 27; James forwards the quoted chain that evening to Bryan Denney and Code Enforcement, copying Buhman. On October 28 James separately asks Hodo to send the video to the Chief because she cannot forward it.
Read entry, limits & sources →02 / FOOD SAFETY
Start with the June 29, 2023 DSHS background findings. Compare the 2025 reports, closure explanations and the October City–DSHS sequence.
Read each inspection’s scope and date. An unsubstantiated complaint and other observations made during the same visit are distinct findings.
The June 29, 2023 DSHS inspection documents flies in the deli and a collapsing bread-room ceiling. Flies appear again in the July 28 and October 28, 2025 state observations; the October notice also records missing bread-room ceiling tiles. These are findings on separate inspection dates.
Read entry, limits & sources →DSHS’s July 28 report marks complaint 1524250148 substantiated. Its notice records six observation categories, including personal clothing near packaged meat, roof debris on selected packaged products/displays, flies, inadequate handwashing-water temperatures, missing thermometers and sanitizer/testing issues. The City’s August 1 letter for a same-day follow-up says food was protected from roof debris and no more follow-ups were required.
Read entry, limits & sources →Lewis Ressler states that the complaint was reviewed and closes complaint 1524250148. His stated reason is that the local health authority is addressing the issue and further DSHS action is not warranted at that time.
Read entry, limits & sources →Milan Patel asks Ankrum to discuss a complaint in the City’s jurisdiction. Ankrum agrees to 10 a.m. the next day. The invitation schedules October 17, 10–11 a.m. Central, with Patel organizing and Martinez, Barrett and Ankrum invited; Webster is optional. Kyle identifies this as the Teams discussion of his complaints before the October 28 joint inspection. The linked scheduling exchange comes from DSHS; the linked City records are Ankrum’s and Webster’s acceptances.
Read entry, limits & sources →DSHS names Webster, Barrett, Ankrum and Martinez at the joint inspection and lists eight observation categories. Its report treats the original July roof-debris complaint as a continuing file with newer submissions uploaded. DSHS calls the triggering complaint unsubstantiated. The City separately records Passed, a hot-water issue and a November 7 compliance date. Flies, inadequate handwashing-water temperatures, sanitizer/testing issues and personal clothing also appear in the July 28 state notice.
Read entry, limits & sources →03 / LIFE SAFETY
Start with the documented 2023 water shutoff and fire-watch instruction. Then compare the fire inspection and plan-review records with the later roof evidence, dispatch production and recorded follow-up.
A dispatch call and an instruction to begin a fire watch do not show who staffed it or how long it continued. Other water, electrical or alarm incidents require separate evidence of a fire-protection impairment and any watch decision.
The collection documents roof activity, debris, refrigeration, storage and other reported conditions, alongside earlier roof-leak photographs submitted to OSHA.
Read entry, limits & sources →Nipp transmits fire dispatch logs on October 20 and directs fire-report and utility-report requests to the appropriate City departments. Kyle acknowledges receipt.
Read entry, limits & sources →Vine questions the blank inspection form, immediately qualifies that he is not saying a rubber-stamp inspection occurred, and asks Kyle to email documentation. Kyle offers OneDrive and raises fee-waiver denials despite findings he describes as substantiated. Vine promises a status update by the end of the following week. The prepared transcript’s Wednesday wording differs from Kyle’s audio-based correction; neither makes Wednesday the promised deadline.
Read entry, limits & sources →Kyle contrasts City and DSHS inspection records, raises the October 17 agency meeting and disputes the characterization of his complaints. Vine later describes a platform migration reported to him by Lin, while expressly acknowledging uncertainty about whether missing fields, PDF conversion or absent inspector notes explain individual records. Lyon identifies code-enforcement standards as something to examine; Vine proposes an internal process review and says he will look at the points marked with red stars.
Read entry, limits & sources →04 / BUILDING & CODE
Compare the permit history, recorded inspection outcomes, contractor and payment records supplied for the remodels, Titus CAD’s valuation questions and the revised TLE notice. The FY2020 audit had already identified missing inputs that prevented auditors from recalculating selected permit fees; the City said it corrected that issue in 2020.
The reviewed productions do not establish a complete job-by-job record of remodel invoices, payments or contractor correspondence. Appraisal values, application values and permit fees serve different purposes; a contractor visit alone does not establish that a permit was required. The missing July 20 inspection pages are a separate production-completeness issue.
ROOF35226 records a $520,499 construction valuation and $3,250 fee/payment. The application shows $959,950; the manager history records the valuation changing to $520,499 on May 27. Payment on June 26 and permit issuance on June 27 are separate from the application and later print dates.
Read entry, limits & sources →The inspection is marked Fail with a July 28 compliance date. Ramirez, accompanied by Ankrum, records debris concerns and cleanup/food-protection instructions.
Read entry, limits & sources →The summary says Courtesy Inspection and Passed; the report says Roofing Final and almost complete, with unfinished edges.
Read entry, limits & sources →In the September 2, 2025 email chain supplied by Titus CAD in August 2026, Dickerson asks Ankrum to reconcile CAR25958’s $19,633,400 construction value with the application’s $1,023,210. Ankrum confirms the lower value, says the old-to-new-system import left some things “jumbled,” and later says HS GovTech changed the permit number for a reason he does not know. The manager history records the September 2 valuation, status and description changes.
Read entry, limits & sources →The original October 20 notice expressly records a complaint about auto-lube work before the October 17 visit and identifies a fire-alarm issue and correction. Ankrum’s email says Barrett suggested removing the work-without-permit reference; the revised notice retains the fire-related finding.
Read entry, limits & sources →The 14-page annual inspection packet supplied July 23 lacks a standard PDF document-information dictionary and XMP metadata stream. The complaint-inspection packet supplied the same day also lacks those containers. These copies limit verification of creator, producer and creation-date fields.
Read entry, limits & sources →05 / SEARCH & SCOPE
Follow the requests through the search descriptions, DTRG correspondence and Webster’s OAG certifications. Compare the statements with source pages and the September 18 search discussion.
A result count shows how many items a search returned, not which mailboxes, dates or terms were actually searched. Compare the stated method and available query with records located later and any identified withholding.
The request seeks City records involving Moring’s name, email address and specified terms, beginning January 1, 2024.
Read entry, limits & sources →The City identifies Microsoft 365 and Purview, describes native PST or MSG exports, and identifies Bryan IT as the technical administrator executing complex mailbox searches at its direction.
Read entry, limits & sources →Webster’s signed form for OR-26-006368-IC represents that all existing responsive information was made available. Production date written on the form: 2/2/26. Compare the certification with search scope, later-located correspondence and completeness objections.
Read entry, limits & sources →The letter answers Moring’s follow-up questions and discusses earlier productions and searches for the selected requests.
Read entry, limits & sources →Bryan discusses changing AND to OR and anticipates more emails; Lyon discusses the parameters. Webster says an earlier OR screenshot returned the same amount, while Kyle says he has not received it. The discussion includes possible review costs, a proposed export and conditional dismissal. Those statements do not establish that the export or dismissal was completed.
Read entry, limits & sources →06 / FEES & CONSISTENT TREATMENT
Ream linked Ordinance 2025-24 to Moring’s requests. Compare that internal email, Hageman and Webster’s Council discussion, the later accounting notices, and Moring’s direct emails asking Council to intervene.
The records show charges and notices in Moring’s requests. One other requester’s closure email does not show a time charge, but that single email cannot establish different treatment. The full histories and any applicable exceptions are needed for a fair comparison.
At 8:37 p.m. on November 25, Ream sent the Mayor and Council an email headed “Attorney Client Privileged Communication.” She attributed the recommendation to Kyle’s requests and identified Beck’s role in suggesting the ordinance. Webster replied to the same internal chain on November 26, saying she had attached the ordinance and updated the online agenda packet. The thread later appeared in the City’s February 2 production.
Read entry, limits & sources →Kyle’s November 25 request sought the ordinance and drafts, staff materials, September 1–November 25 communications, and implementation/time-tracking records. Webster replied that the City had no responsive records and would seek an AG opinion on attorney emails. The next day she sent the ordinance and said the request was closed. Kyle disputed the closure and asked again on December 12 for the filing date, OAG number and asserted exceptions.
Read entry, limits & sources →Webster’s February 2 transmittal supplied the Moring-related records link and receipts and closed that request. The ZIP includes the marked November 25–26 thread. Kyle’s March 2 email to the Mayor, all five Council members, City administration, Ream and Beck attached a binder that reproduces it as Exhibit E, including the privilege label and both instructions not to reply. The March 20 and two March 21 submissions also attached a meeting transcript referring to Ream’s internal ordinance email.
Read entry, limits & sources →07 / FORMAT & CONTEXT
Compare the requested CDR date range and format with each delivery, the second charge, the native-email and header concerns, and the July inspection and compensation files. Moring disputes Webster’s interpretation of his CDR request because the replacement still did not match the requested period or format.
A different export format does not by itself establish alteration. Check each request, invoice and delivered file separately; missing metadata shows what the supplied copy lacks, not who changed an earlier version.
Kyle raises differing call-log formats and requests a replacement March 4-forward production, accepting a further fee under protest. Reviewed files include older vendor CDR workbooks, newer City PBX exports and a later CSV delivery.
Read entry, limits & sources →The June 15 invoice charges one hour/$15 for the separate CDR update. Kyle subsequently confirmed he paid the second $15.
Read entry, limits & sources →The 14-page annual inspection packet supplied July 23 lacks a standard PDF document-information dictionary and XMP metadata stream. The complaint-inspection packet supplied the same day also lacks those containers. These copies limit verification of creator, producer and creation-date fields.
Read entry, limits & sources →The City transmits Call log.csv for the May 31–July 24 request. The invoice and receipt record a $15 sale. Kyle asks for the original vendor transmittal with the attachment intact.
Read entry, limits & sources →The two PDFs lack standard information/XMP containers. Five Office files have blank or absent creator and lastModifiedBy fields and September 15 core timestamps. The saved SharePoint listing names Webster under Modified By. All seven files byte-match the delivered ZIP.
Read entry, limits & sources →08 / RESPONSE & REVIEW
Trace Webster’s June 30 and October 8 response instructions, the October 16 forwarding email, Vine’s October 17 direction, Council escalations, DA correspondence, OAG determinations and the positions presented in court.
The June 30 and October 8 messages explicitly direct others not to respond to Moring or his identified follow-up. The October 16 wording says not to reply to Webster’s forwarded email; that wording alone does not establish an instruction to ignore the underlying safety request. Later actions must be assessed from their own records.
Webster’s email says “Do not respond to the message” about the identified TLE follow-up.
Read entry, limits & sources →Vine’s internal email addresses complaints from Kyle about Walmart, OSHA or other violations, and construction practices at that location. He directs the named recipients to forward those emails to him, avoid back-and-forth, and notes Webster’s work with an attorney regarding Kyle’s continued requests for information.
Read entry, limits & sources →At 8:37 p.m. on November 25, Ream sent the Mayor and Council an email headed “Attorney Client Privileged Communication.” She attributed the recommendation to Kyle’s requests and identified Beck’s role in suggesting the ordinance. Webster replied to the same internal chain on November 26, saying she had attached the ordinance and updated the online agenda packet. The thread later appeared in the City’s February 2 production.
Read entry, limits & sources →OAG’s signed April 17 determination identifies an apparent missing section 552.221(d) certification and an apparent failure to determine the City complaint or provide a conflict notice within the stated period. It concludes these appeared cured and declines action, relying on TCDA’s production representation and preliminary determination.
Read entry, limits & sources →After acknowledging the complaint on May 8, Bailey’s June 6 letter states he finds no violation in the complaint or supplemental materials and will take no action. The letter does not explain how he resolved each allegation about the March 17 meeting.
Read entry, limits & sources →146 distinct outgoing emails to the Mayor or a Council member were reconciled to original mailbox bytes using SHA-256, Message-ID, date and actual recipient headers. The retained classification contains 28 action requests, 6 governance notices and 112 records/administrative exchanges.
Read entry, limits & sources →Moring opposes the City’s jurisdictional arguments and identifies records and record families he says remain unsupplied. The filing includes the PR exhibit series.
Read entry, limits & sources →The timestamped links in Kyle’s same-week media emails identify 13:55–16:49 public comment and 28:21–31:03 budget remarks. Kyle reports the cutoff, microphone switch-off and threatened police escort; he says he was not escorted out.
Read entry, limits & sources →THE SAME STANDARD FOR EVERY ADMINISTRATION
People who seek credit for exposing misconduct should be willing to answer for their own decisions.
COMPARE THE STANDARD WITH THE RESPONSE
STATED STANDARD · FEBRUARY 18, 2026
“We’re being very transparent.”
“you should at least be getting a response back”
Rob Vine, in the meeting with Wesley Lyon, Carl Hinton and Moring.
Moring’s recording and transcript: p. 92, 01:02:22; p. 95, 01:04:04. The discussion also addresses workload and requests the City regarded as repetitive. These locators use the original recording clock, which may differ from the excerpt player.
Read the statements in context ↗INTERNAL DIRECTION · OCTOBER 17, 2025
“Do not respond to this individual or engage in any back and forth.”
Vine’s email directs the named recipients to forward the described complaints to him.
Internal email, p. 1. This documents a communication instruction. It does not alone establish a prohibition on producing records or show how each recipient acted.
Read the email and subsequent context ↗COUNCIL CORRESPONDENCE · NOVEMBER 25–26, 2025
“Please do not reply to Mr. Moring.”
Lea Ann Ream’s November 25 message to the Mayor and Council links the ordinance recommendation to Moring’s requests. Candias Webster replies the next day about the updated agenda packet.
The marked thread was included in the February 2 production. Its production, notice and privilege history is documented separately; the instruction alone does not establish unlawful intent.
Read the produced thread and source notes ↗MAILBOX COUNT · OCTOBER 2025–AUGUST 2026
28 action requests in 146 distinct outgoing messages that include the Mayor or a Council member.
The action category contains 27 oversight, complaint-review or agenda requests and one fee-waiver request.
The saved-mailbox audit deduplicates messages across six mailbox files. Message dates run from October 16, 2025 through August 6, 2026. A separate check of later saved emails identified six distinct outgoing Council-addressed messages dated August 17–September 16, including two additional oversight requests; they have not been added to the earlier mailbox count because that later set is not a complete mailbox export. Inclusion of an official in an address field does not prove that the official read the message, and 146 is not a count of unanswered action requests.
Inspect the count and classified messages ↗DECEMBER–FEBRUARY FOLLOW-THROUGH
After the December assurances and OneDrive access problems, Moring emailed a binder on January 11 and delivered a USB on January 14. Ruff urged City leadership to examine the evidence on February 3. The next day, Lyon described a public perception of stonewalling while acknowledging that it might be inaccurate; outreach followed on February 5. At the February 18 meeting, Moring pointed Vine to his linked memorandum when Vine asked for a “smoking gun.” Moring says he had received no written response addressing the memorandum’s requested actions or setting another review schedule before that meeting. This chronology includes the acknowledgments, outreach and February 18 meeting alongside the questions that remained unanswered.
Read the December–February chain ↗QUESTIONS FOR THE PRESENT LEADERSHIP
A CLOSING QUESTION · AUTHOR’S COMMENTARY
When the same institution controls a search, explains its results and closes a complaint about those results, who independently checks the answer? When responsibility moves from one office to another, who is accountable for providing a documented decision?
Meaningful oversight should not depend on a resident’s ability to hire an attorney or navigate a complex records system. It should address the specific concerns raised, explain its conclusions and identify the records supporting them. Read the responses and evidence here, then decide whether that standard has been met.
These questions concern the specific statements, responses and records linked on this page.
Compare the statements and supporting records ↗