Store 131 conditions, access to public records, and the handling of sensitive information reached City leadership through emails, supporting records and public comments at City Council meetings. The record also includes David Ruff’s request that leadership examine the evidence and Mayor Lyon’s report that several people perceived stonewalling. This page lets readers compare each concern with the response and documented follow-through.
Through September 25, 2026 · Mount Pleasant, Texas
How to read the Council record
What happened
Kyle sent oversight requests and supporting material to City officials and Council; later meetings and public comments continued the discussion. Follow the dated correspondence.
What the City said
The record includes City routing instructions, Vine’s acknowledgments and responses, and Mayor Lyon’s concern about public perception. Their wording and dates matter. Read the records-and-response discussion.
What the records show
Messages, delivery accounts, meeting material and produced records document contacts and some follow-through. Inclusion on an email does not establish that a recipient read it or reached a decision. Check the source-linked milestones.
Kyle’s position
Kyle says his requests for a documented Council review and written resolution were not fully answered. That account is identified as his position and should be assessed beside the City’s recorded replies. Read the submitted account.
What remains unresolved
The reviewed record does not settle every search, inspection, disclosure or Council-action question. The sections below keep each subject and its limits separate.
146distinct emails including the Mayor or Council
28requests for Council action
6additional governance or preservation notices
These counts cover messages dated October 16, 2025–August 6, 2026. The 28 action requests comprise 27 oversight, complaint-review or agenda requests and one express fee-waiver request. The other 112 messages concern records or administration. Later events appear below but are outside this count. Delivery to a listed recipient does not establish that the recipient read the message, and these are not counts of unanswered complaints.
01 / NOTICE & RESPONSE
The escalation sequence
Requests for review continued across correspondence, meetings and public comment. Read the actual responses alongside the requests.
The first escalation is followed by a no-reply directive
Kyle sends Barrett and Ankrum a written request for permit confirmation and enforcement follow-up concerning Store 131. Later that afternoon, Webster forwards it internally and writes, “Please do not reply to this email.” The record documents the instruction; it does not establish whether another official separately reviewed or acted on every request in the underlying message.
Vine directs the named recipients to forward Moring’s Walmart, OSHA and related complaints to him and not engage in further back-and-forth. The instruction concerns the described complaints; it does not by itself establish a direction to withhold responsive public records.
Kyle asked the Mayor and Council to postpone Ordinance 2025-24 while the documented concerns were reviewed. The produced internal correspondence links the ordinance recommendation to his requests and directs Council members not to reply.
A formal ethics and records-management complaint reaches Council
Kyle submits a complaint concerning Candias Webster, John Ankrum and Juan Ramirez. It asks for an independent investigation, preservation, agenda consideration and a written response. The document records Kyle’s allegations and requested remedies; it is not a finding that a violation occurred.
Kyle submits a complaint concerning Lea Ream and Austin Beck and again requests independent review, preservation, agenda consideration and written findings. The document records the allegations submitted to Council; it is not an adjudication of attorney conduct.
A written request to reconcile the inspection records
The Council submission asks how the City’s October Passed record fits with DSHS’s observations. It seeks clearer inspection standards, retention and public reporting, and a written response with corrective actions and timelines.
After the January 11 emailed binder, Kyle reports delivering a USB to Karina Memije at City Hall around 1:30 p.m. His afternoon email documents the handoff. Vine’s 9:14 a.m. acknowledgment was earlier that day; it does not establish that he had already reviewed the drive.
Another resident asks leadership to examine the evidence
David Ruff asks City leadership to meet with Kyle, review the photographs, recordings, timestamps and inspection records, and act on any substantiated issue—or explain if nothing is established. Ruff expressly says he has not independently determined whether every claim is correct.
Lyon tells City counsel and Vine that he and Council members have heard that perception from several people. He also says the perception may be inaccurate and raises a possible Council agenda discussion.
A meeting addresses searches, inspections and follow-through
Lyon, Hinton and Vine meet with Kyle. The discussion includes the search terms used, inspection discrepancies, the submitted memorandum and workload explanations. Vine says Kyle should at least receive a response; Hinton says they will not tell him to stop submitting requests.
OpenGov and payment-system concerns reach leadership
Kyle sends City leadership notices concerning reported portal access and payment-system information. Vine acknowledges the April 28 notice and says the City will investigate and work with its partners. A later records request seeks the handling and investigation records; Webster’s May 27 certification identifies Kyle’s notice but says no responsive records were located for items 1–25.
Disclosure concerns become Council action requests
The May 21 request seeks agenda review of Schneider customer and payment information. The May 28 request seeks agenda placement of the police-report disclosure and pending ethics complaints. Separate notices also went to the DA and OAG.
Inspection-production objections reach City leadership
The City supplies the July 9 and July 20 inspection packets and closes the request. Kyle’s follow-up identifies missing Permit Manager pages, complaint records and electronic source material. It copies the Mayor and Council for awareness, while directing the records response to the City Secretary and expressly requesting no Council action in that email.
A formal request for Council oversight of data security
Kyle sends a signed submission to the Mayor and Council seeking preservation, documented incident-status reconciliation, records-compliance reporting and an oversight agenda item. He separately renews his ethics-complaint agenda request. These later requests are outside the correspondence count above. As of September 25, 2026, Kyle reports receiving no written response addressing this submission and knows of no Council decision on it.
Two timestamped passages preserve Kyle’s Council appearances. He reports that his budget remarks were cut off and that a police escort was threatened; he says he was not escorted out. The following day he requested preservation of the recordings and related records.
Postpone Ordinance 2025-24 pending review of the documented concerns
Investigate the formal ethics and records-management complaint
Investigate the formal ethics complaint concerning City attorneys
Council review of the October 28 inspection and records standards
Commission a records audit, correct discrepancies and consider a fee waiver
Independent investigation and internal audit of the two identified MPPD cases
Council approval of a public-interest fee waiver for shared-link records
Formal review, independent investigation and agenda placement
Council review of fire-inspection documentation and close-out practices
March 17 written requests for acknowledgment, outside review and conflict-free counsel
Clarify the Council decision, review process and promised revisit date
Supplement the ethics-review record with the Webster comparison and request acknowledgment
Council review of the Ankrum comparison and requested independent follow-up
Council review of governance statements and clarification of oversight responsibilities
Return the ethics complaints and TPIA practices to a posted agenda
Agenda review of the Schneider production and handling of sensitive records
Agenda placement of the police-report disclosure and pending ethics complaints
Return the ethics complaint to Council following missing CDR production
Renew agenda request over CDR format and fee discrepancies
Renew agenda request while agreeing to pay for the replacement CDR request
Agenda review of ethics complaints, TPIA practices and IT records
Council review of the plan-records ruling and prior production history
Agenda placement and independent audit of TPIA and internal controls
Independent review of production controls and outside-counsel handling
Agenda placement following a further CDR completeness objection
Agenda placement following a further native-format objection
Reconcile personnel time, justify or refund the paid $15, and correct production format
Renew Council agenda request over telecom correspondence and charges
The count uses distinct outgoing messages, deduplicated by Message-ID across six mailbox files. Quoted histories, duplicate copies and multiple Council recipients do not add messages.
Refrigeration, electrical conditions and repeated inspection concerns
The available photographs, recordings and complaints span different dates. Together they document recurring concerns; each item has its own evidentiary limits.
THE 2026 SEQUENCE
New outage reports, followed by a City complaint inspection
June 27–28: public posts report that Store 131 stopped admitting customers when its systems went down, with a breaker or power issue described. A subsequent post reports reopening on June 28.
July 9: posts describe another closure, power loss in the front of the store, registers down and a reported fuse problem. These accounts do not independently diagnose the electrical cause.
July 19: Titus County News posts describe refrigeration being down across meat, dairy, produce and other refrigerated products. Current-employee statements from the supplemental submission are not reproduced here.
July 20: Kyle sends the material to TDLR in the existing Store 131 matter. The City’s separately produced report dates its complaint inspection July 20, 2026.
Only the public reports needed for context are summarized here. The full TDLR submission and current-employee material remain off this public page while the matter is under review. The submission does not establish that the earlier remodel caused the outages or that TDLR found a violation.
What the City’s July reports say
July 9 annual inspection: the deli sheet records a score of 95. Its observations list hot holding at 112°F and multiple items out of date, with the corresponding Correct By and Action fields blank. A separate sheet lists cold-holding readings of 32°F, 35°F and 37°F.
July 20 complaint inspection: the narrative says the Code Department learned of the outage on Sunday. It attributes a flipped breaker and leaking refrigeration line, repairs, protective measures and product handling to the store’s AP coach. The inspector records a Passed outcome, a July 30 compliance date and temperatures checked that day under compliance. The narrative says affected items remained below 41°F and only lettuce/salad products were removed.
What reached the August agenda packet: the July Code Enforcement Monthly Report in the August 18 City Manager’s Report lists 51 cases and 155 inspections, but it displays no Food Service Complaint or FS row and does not identify the July 20 Walmart complaint inspection. Because the report provides category totals rather than case numbers, it does not let a reader reconcile that inspection to the month’s published activity.
The report’s date is July 20. The outage was reported July 19. The July 20 photographs show readings when photographed; they do not reconstruct the previous day’s temperature history.
Produced on July 23. Completeness still disputed.
Webster’s July 23 email supplied both PDFs and declared the request closed. That evening Kyle identified missing source pages, complaint-intake records, original photographs and electronic exports.
Missing pages: the seven-page refrigeration packet starts with Permit Manager pages numbered 3/4 and 4/4. The remaining five pages are photographs; source pages 1/4 and 2/4 are absent.
Image-only copies: both packets contain page images with no searchable text. The complaint report retains browser print headers, consistent with a print-based copy. The supplied PDFs do not establish every step of a physical print-and-scan process.
Metadata: neither supplied PDF has a standard document-information dictionary or XMP metadata stream. This verifies the absence in these copies, not who removed information or why. Original photo metadata and system history cannot be recovered from the visible page images.
The July 23 follow-up copied the Mayor and Council for awareness and expressly requested no Council action in that email. It brought the inspection-production issues to leadership’s attention while directing the records response through the City Secretary.
A September 11, 2025 recording shows the Freshpet cooler’s base and an exposed electrical panel. Kyle’s accompanying account says the cooler concern went back to his December 2024 message to the store manager. A public Facebook post also reports dogs becoming ill after eating Freshpet food purchased at the store; that account does not establish the food’s condition or the cause of illness. An October 17 photograph shows absorbent material and a wet-floor marker beside a refrigerated case, consistent with a reported leak or condensate problem. Kyle’s October 22 DSHS escalation describes continuing refrigeration, drainage and pooling concerns.
A post, case display or photograph alone does not measure food temperature, diagnose a failure, establish the cause of an illness or show that the same fault persisted continuously.
Electrical conditions during water intrusion and roof work
A December 28, 2024 photograph shows water beside electrical cabinets in the General Merchandise backroom area. A July 12, 2025 recording shows dangling wiring and a light fixture with daylight through roof openings. The later OSHA production records an allegation of electrical arcing from roofing work in Electronics and includes a July 29 work-order screenshot stating that an old light fixture above Electronics smoked and burned through the roof.
The OSHA narrative says management later supplied a closed repair work order and that the compliance officer could not substantiate a hazard during the August 19 inspection. Those later findings belong beside the dated report; they do not erase what the July 29 work order records.
The photograph, recording and work-order image document conditions reported on their respective dates. They do not establish whether a circuit was energized when photographed, whether the same condition continued after the recorded repair, or the cause of later outages.
MONTHLY REPORT CHECK · 2025
Food-service totals do not identify the complaints or inspections behind them
The July 2025 Code Enforcement report lists an ungrouped Food Service Complaint row with two cases and zero inspections. Kyle’s saved portal confirmations document anonymous submissions on July 25 and July 26—also two submissions—but the report provides no dates, case numbers or addresses, so the count alone cannot establish that those are the two cases reported.
The City-produced July 18 record expressly says, “Conducted complaint inspection,” records concerns about debris falling on food and packaging, and marks the outcome Fail with a July 28 compliance date. The same record classifies its Purpose as Routine and leaves the complaint-number and complaint-type fields blank. The monthly report nevertheless records zero inspections on its Food Service Complaint row. The record and aggregate report therefore do not show how the July 18 inspection was classified or counted.
The phone records separately support Kyle’s same-morning calls and another contact he identifies as a second complaint. The available call log establishes the contact, not what was said.
The September report makes the abbreviation explicit: FS means Food Service Complaint. A City-produced letter identifies FS-473734, says a Food Service Complaint inspection occurred September 16, and records no present violations and no further follow-up. The monthly report shows one ungrouped Food Service Complaint case with zero inspections and, under FS, three cases and 20 inspections, but it provides no dates or IDs. It therefore does not show where FS-473734—or Kyle’s September 22 anonymous submission—was counted.
These are reconciliation gaps in public summaries and within the City’s own classification fields. They do not establish that a complaint was deleted, that an inspection never occurred, or which individual case each aggregate count represents.
The connection to Council oversight
The July and October 2025 inspection records, the monthly summaries, the October internal briefing and the December 22 Council submission put the question of reconciliation in writing. The City’s July 28 follow-up says food was protected, temperatures were compliant and no further follow-up was required. DSHS’s notice from the same visit separately documents six categories of observations. The October joint report calls the triggering complaint unsubstantiated while listing eight observation categories; the City records Passed with a compliance date. Those different records should be read together when evaluating repeated complaints and follow-through.
Can the public follow the search and the decision?
The oversight requests go beyond obtaining another copy: they ask how records were searched, retained, produced and used to resolve the underlying complaints.
Search scope and production
The issue is whether the searches matched the requests and can be reproduced. Kyle repeatedly asked what methodology was being used after responsive messages—including some of his own sent emails—were absent from the productions. The February 18 discussion, the produced search screenshots, later-discovered records and Microsoft’s KeyQL guidance allow readers to compare the requested scope with the documented searches.
The later records include July DSHS referrals, the EPA–TCEQ–MPPD thread and Walmart-related messages that appeared only after separate or subsequent requests. Their later production does not by itself establish why they were absent earlier. The HS GovTech agreement separately confirms electronic export capability; it does not identify which searches the City ran.
Vine said on December 3 that he would provide a status update by the end of the following week. The later record documents failed delivery links, alternative delivery offers, the emailed binder, the January USB handoff and the February meeting. Kyle received communications about delivery and the meeting, but reports no written response resolving the memorandum’s requested actions before that meeting.
The record contains serious disclosure concerns, a counsel response, and requests for technical investigation. These are separate events; the evidence does not establish a single system-wide breach or a common cause.
OpenGov notices reached Council
Kyle’s April 28 governance notice told the Mayor and Council that he had separately notified City administration and OpenGov about apparent SSN-format values in a public financial export. His April 29 follow-up notified Council of apparent victim- and patient-identifying information in the same publication environment. Both Council notices omitted the sensitive underlying values and requested containment, preservation, technical review and documented follow-through.
Vine’s April 28 reply to the separate administrative notice says the City would investigate and work with its partners. Webster’s May 27 signed certification later identifies Kyle’s notice but says no responsive records were located for items 1–25. That creates a focused question about what systems and custodians were searched and why the City-generated acknowledgment was not produced or treated as responsive. Kyle’s later cybersecurity referral is a separate step and is not presented here as a finding that compromise occurred.
Public financial exports: the April Council notices report apparent SSN-format values and victim- or patient-identifying information and request preservation and review.
Customer and payment information: the May notices concern Schneider information and related payment records.
Police information: Beck acknowledges an apparent inadvertent disclosure, asks Kyle to delete the unredacted report and offers a redacted replacement.
The May 21 and May 28 Council requests seek agenda review of the disclosures and pending ethics complaints. The August 19 submission requests governing-body review across the incidents and cites Hunter Bonner’s August 18 public allegations concerning electronic signatures and vendor-account offboarding. Bonner’s statements remain attributed allegations, not verified technical findings.
What was exposed, who could access it, what was preserved, and what corrective action followed? An access log, incident assessment or documented corrective action would answer a different question from a notice of concern or an offer to replace a disclosed record.
CONTRACTS, HIRING & LEGAL SPENDING
What Council approved. What the available records show.
The recruitment proposal, fee terms, payment records and appointment minutes address different questions. Read each alongside the correspondence about searches and oversight.
DTRG’s City Attorney fee terms
The August 27, 2024 engagement letter proposes $225 per hour for Ream and other partners, $180 for associates, $100 for paralegals and $300 for specialized assistance. It provides monthly billing and allows later rate adjustments. These are the terms in this letter, not a claim that every later invoice used the same rates.
The acceptance signature is blank in the available copy.
DTRG’s September 2024 proposal caps work billed to a separate “CM Recruitment” file at $15,000, with a $110 paralegal rate and a $225 rate for Ream. Council-meeting attendance and preparing the employment contract are assigned to the separate Employment Matters file.
The proposal calls for Council selection of interview candidates, reference checks to verify prior employment, and a third-party background search after acceptance of a conditional offer. The available records do not show what that third-party search found, which Dayton matters were surfaced or what Council received. The February 18 exchange may indicate that Hinton was only then learning of the material discussed, but it does not establish what DTRG, every Council member or other officials knew.
Council approved Vine’s agreement. The signed copy is missing from Kyle’s collected records.
The August 12, 2025 minutes record a unanimous vote to approve an employment agreement with Rob Vine. They specify employment beginning August 18 and full responsibility beginning September 4, 2025.
Kyle’s observation: I have not found the signed agreement in the records I have collected. That gap is itself part of my concern about the City’s records: the minutes establish approval, but I cannot compare the approved agreement with the City’s implementation without the agreement itself.
The minutes do not supply the contract’s pay, severance, duties or other terms. The March 4, 2025 contract packet names Kimberly Meek and is not Vine’s agreement.
The City’s vendor export identifies 47 distinct checks through August 2025 totaling $1,018,540.68. Seven later register entries add $119,996.03, through July 2026. Repeated invoice rows are counted only once per check.
This is a subtotal across multiple legal matters. October 2025 and January 2026 amounts found only in Kyle’s working reconciliation are excluded. February and June 2026 registers are also missing from the reviewed source set; those months are not treated as zero.
Ream’s November 25 email describes Beck and Webster working on Moring’s requests and attributes a substantial resource burden to the disputes. The search correspondence and recordings show the tasks and explanations that can be compared with the engagement terms.
The payment records do not isolate costs caused by Moring’s requests, this lawsuit, Walmart matters or Webster’s work. Matter-level invoices or a nonprivileged allocation would be needed to answer that question.
Kyle’s question: What did Council receive about Vine’s prior employment, what follow-up occurred, and how can residents evaluate the cost and quality of records administration from the records actually made available?
COSTS & RESOURCES · REAM’S STATEMENTS
“I’m not billing the city” beside the taxpayer-resource claims
The September 18 conversation and the written explanations raise a specific question: which work was billed, which was discounted, and which costs were staff time?
September 18, 2026 · conversation excerpt
Reviewing Kyle’s emails
“I’m not billing the city for reviewing all of your emails and all that I kind of scan them”
Ream then says she lets Austin handle the emails for efficiency unless something requires her attention. This statement addresses her review of the emails; it does not say that all records-request work by DTRG was free.
Earlier, Ream describes “an extraordinary amount of money responding to these things,” refers to a third trip to a hearing, says taxpayers are paying, and says she is giving “discounts upon discounts.”
September 10, 2026 · emailed letter to Judge Parish
“Waste of taxpayer resources”
Ream circulated this letter to the judge and the other recipients by email. The City filed a separate hearing notice; Ream did not file this letter with the District Clerk. The letter appears in the linked PDF as an attachment to Kyle’s response.
Ream asks the court to consider the City’s plea first, invoking judicial economy and preventing “the waste of taxpayer resources.” The surrounding letter states the City’s position that Kyle had not identified records it refused to provide. Kyle’s response disputes that position.
Ream writes that disputes about responses cause the City to spend “a significant amount of resources responding to his requests and emails.” She identifies Webster and Beck as handling the requests.
How much was actually billed for records-request work, how much was staff time, and how were the claimed discounts calculated? I want readers to compare these explanations with the underlying bills and work records.
The statements describe different kinds of work and do not, by themselves, establish contradictory billing. The City payment subtotal covers multiple matters and cannot resolve the allocation.
Dayton records concerning Rob Vine provide a comparison about complaint review and search completeness. Melancon’s 2021 report sustains a failure-to-reprimand concern but calls a false-report allegation inconclusive; Willard later recommends retaining Vine’s roles and compensation. In another investigation, Prado reports that an IT search did not provide the full email strings obtained through open records and recommends an IT study. These separate matters do not establish email deletion or the same technical problem in Mount Pleasant.
Resolution would be shown by a documented result: reconciled inspection findings, verified repairs, reproducible search methods, a written Council decision or a completed disclosure review. The linked records allow readers to compare each concern with the response and decide what the record establishes—and what remains unanswered.
March 17 presentation directions in the Council record
Page 1 places the March 17, 2026 presentation directions beside the underlying March 16 request. The four-page selected thread also contains later clarification; the correspondence date and the later discussion should be read separately.
Selected correspondence; March 17 directions and later clarification · page 1
Source check. The March 17 message quotes the March 16 request. These correspondence dates are distinct from any later meeting action.
Scope. The message documents directions and correspondence. It does not by itself establish a Council decision or resolve the later clarification or a legal question.
