A CONNECTED CASE PATH · WALMART STORE #131

Complaints, inspections, records and response.

This route keeps Store #131 at the center while connecting the City’s permitting and inspection records, agency activity, Council response, public-records disputes and the October 22 trespass event. Each stage points to the full page or source collection; it is a guide, not a replacement for the evidence.

1. 01

   START WITH THE DATED MATERIAL

   Reported conditions and complaints

   Read Kyle’s reported concerns with the dated photographs, recordings and request context. Each image or account remains attributed; it is not an independent inspection finding.

2. 02

   FOLLOW THE CITY RECORDS

   City permits, inspections and notices

   Keep each permit, application, inspection result, notice and corrective-action record attached to its own project and date. Missing records in a reviewed production remain a production limitation, not proof that a record never existed.

3. 03

   READ SCOPE AND FINDINGS SIDE BY SIDE

   Compare City and state food-inspection records

   The City’s and DSHS’s records may use distinct criteria and reporting outcomes. Compare the reports and the City’s explanations by inspection date; do not treat different labels alone as proof of contradiction.

4. 04

   A REFERRAL IS NOT A FINDING

   Follow referrals and each agency’s role

   Track what was sent to DSHS, TCEQ, EPA, OSHA, law enforcement or another office, and what each agency documented within its own remit. Referral, investigation, file possession and overlapping jurisdiction do not independently prove wrongdoing.

5. 05

   WHAT WAS SAID AND WHAT HAPPENED NEXT?

   Read City routing, Council response and follow-through

   Compare correspondence and meeting records with the stated routing or response. A direction, acknowledgment or meeting shows what its source records; it does not alone establish that a complaint was ignored or resolved.

6. 06

   REQUESTS, SEARCHES AND PRODUCTIONS

   Trace the public-records requests

   Follow the request scope, City search descriptions, estimates, production batches and later located records. Read the City’s explanation beside the specific records and preserve the difference between a link working, a file being produced, receipt, completeness and proof of delivery.

7. 07

   CLAIM · SOURCE · EXPLANATION · LIMIT

   Compare important statements with their records

   The comparison pages place consequential statements alongside cited documents, later productions or corrections, and the City’s explanation where available. Kyle’s assessment is attributed to him; discrepancies are not silently converted into findings of knowledge or intent.

8. 08

   THE DEDICATED TEMPORAL PROXIMITY PAGE REMAINS

   Keep October 22 in its complete context

   Read the date-by-date analysis with its body-camera context and source links. Kyle’s reported OSHA §11(c) complaint and notice to others are part of the documented context; a filing alone does not decide protected status, retaliation, motive or the merits. Temporal proximity does not prove causation or intent.

9. 09

   THE FILINGS ARE THE PARTIES’ POSITIONS

   Read the court filings and what remains unresolved

   Use the filings and complete source records to assess the disputed search, production and delivery questions. The record retains unresolved provenance, completeness and timing qualifications; this guide does not decide them.

Back to the recommended reading path ↑Open the Temporal Proximity page →