THE LAW THEY CITED, THE CHARGES THEY CHOSE
A February 2025 record of meeting disruption, a statute the City said “constitutes a crime,” and why only two individuals now face charges under R.C. 2917.12
By Aaron Christopher Knapp, BSSW, LSW
Investigative Journalist and Public Records Litigant
Editor-in-Chief, Lorain Politics Unplugged
Knapp Unplugged Media LLC
I. THE LAW THEY CITED BEFORE THEY USED IT
Internal emails show officials knew exactly how “disturbing a lawful meeting” was supposed to work
By Aaron Christopher Knapp
Investigative Journalist | Editor-in-Chief, Lorain Politics Unplugged
I. THE STANDARD WAS WRITTEN BEFORE IT WAS EVER ENFORCED
A documented rule, a defined process, and a record that predates every charge that followed
Before anyone was charged, before any warrant was issued, before March of 2026 and even before July of 2025 when enforcement under this statute first appeared in a criminal case, the City of Lorain had already established, in writing, exactly what it believed the law required when conduct at a public meeting crossed the line.
This was not something developed after the fact. It was not created in response to a specific incident. It was not a position taken during litigation. It was a contemporaneous internal communication circulated among City leadership that defined both the nature of the conduct and the process that was supposed to follow.
That communication included the Mayor, Law Director Patrick Riley, and the Safety Service Director, and it addressed public behavior at council meetings directly. It did not rely on general language or broad policy statements. It connected the City’s internal rules to Ohio criminal law in clear and unmistakable terms.
Within that email, the City made a definitive statement about the legal status of disruptive conduct at a meeting. It stated that Council Rule 47 is the same as Ohio Revised Code Section 2917.12 and that if violated, it constitutes a crime.
That statement is not subject to interpretation. It does not suggest that such conduct might be criminal under certain circumstances. It does not leave room for discretion at the threshold level. It establishes that when the rule is violated, the conduct is criminal as a matter of law. In doing so, it removes any ambiguity about how the City understood its own authority and its obligation to act.
The communication then moved beyond defining the law and laid out the mechanism for enforcement. It explained that police should conduct a complete investigation into the conduct at issue and that the results of that investigation should be presented to the Law Department. It further stated that if the evidence warranted it, criminal charges should be filed.
This is not a general guideline. It is a structured process that identifies each step in the chain of enforcement. Conduct is identified, an investigation is initiated, evidence is gathered and reviewed, and a charging decision is made based on that evidence. The language used in the email reflects an expectation that this process would be followed when the elements of the statute were present.
What is significant about this communication is not only what it says, but when it was said. It predates every charge that has since been filed under R.C. 2917.12 in this context. It exists before July 2025, when the statute was first used in a criminal case involving meeting conduct, and it exists before March 2026, when additional charges were brought.
At the time this was written, the City was not reacting to enforcement decisions. It was defining the standard that would govern those decisions. It was establishing how disruptive conduct at a public meeting would be classified and what steps would be taken in response.
That insertion matters because it further reflects the same understanding within the chain of command that conduct at public meetings was not to be handled informally or selectively, but rather through a defined process tied directly to criminal law. When read together with the earlier communication, it reinforces that the City’s position was consistent at the policy level. Disruptive conduct was to be identified, investigated, and, where supported by evidence, charged.
Taken as a whole, this record establishes that the City of Lorain did not lack a standard. It did not lack clarity about the law. It did not lack a defined process for enforcement. All of those elements were in place before any of the events that now form the basis of criminal charges.
The significance of that fact is not theoretical. It means that when conduct later occurred that fit within the framework the City had already described, the expectation created by its own words was that the same process would be followed.
II. THE HILTON INCIDENT WITHIN THE CITY’S OWN FRAMEWORK
A contemporaneous record describing conduct that aligns with the standard already defined
When the internal standard established by the City is placed next to the February 2025 email record, the comparison does not require interpretation or expansion. It is a direct alignment between what the City said the law required and what was reported to have occurred at a public meeting.
The February 18, 2025 email is not framed as opinion or speculation. It is a contemporaneous communication documenting conduct that had just taken place the night before. It was sent broadly to City Council, the Law Department, law enforcement, and media, placing the described conduct directly in front of the same officials who had already articulated how such situations should be handled under Ohio law.
The language of that record is clear.
“Last night, on video, Tia Hilton disrupted a public meeting. When asked to leave she refused multiple times.”
The communication then provides additional detail regarding the nature of that conduct.
“She made me fearful… she told someone their ‘days were numbered’… it’s on video.”
These statements are not generalized descriptions of disagreement or routine participation in public comment. They describe specific conduct that includes disruption of a meeting, refusal to comply with a directive to leave, and statements that were perceived as threatening. They also explicitly reference the existence of video evidence documenting the incident.
When these elements are read alongside the City’s previously stated position regarding Council Rule 47 and R.C. 2917.12, the connection is direct and unavoidable. The City had already established that conduct which violates the rule constitutes a crime. It had already outlined that such conduct should be investigated and that charges should follow if supported by evidence.
The February 2025 email describes conduct that falls squarely within that framework. It identifies the type of disruption the City had classified as criminal. It identifies a failure to comply with removal, which is a key factor in evaluating whether a meeting has been disturbed. It identifies statements that created fear, which further elevates the seriousness of the conduct being described. It confirms that the incident was captured on video, providing a basis for the very investigation the City had outlined in its own internal communication.
Equally significant is the distribution of that email. It was not sent to a single office or handled informally. It was directed to the same group of officials who had already defined the enforcement process. Those officials were placed on notice of conduct that, based on their own stated standard, would trigger investigation and potential charges.
Taken together, the February 2025 record does not exist outside of the framework the City created. It exists within it. It reflects the same elements, the same type of conduct, and the same evidentiary basis that the City had already identified as falling under R.C. 2917.12.
The result is not a comparison built after the fact. It is a record that, at the time it was created, already fit the standard that had been defined.
III. WHAT THE CITY DID WHEN THE CONDUCT INVOLVED GARON PETTY
Immediate escalation, formal framing under criminal law, and a clear expectation of enforcement
The same body of records does not simply define the standard in the abstract. It shows how that standard was applied when conduct at a public meeting involved Garon Petty. When that incident occurred, the response from City officials was not delayed, uncertain, or limited to internal discussion. It was immediate, direct, and framed in terms of enforcement.
The July 1, 2024 email chain documents an incident in which Garon Petty was alleged to have entered a restricted area of the council chambers and engaged in conduct that was described as intimidating toward the Clerk of Council.
The characterization of that conduct within the email is not neutral. It is described as “absolutely unacceptable,” language that reflects not only disapproval but a determination that the conduct crossed a clear boundary requiring action.
That reaction is followed immediately by a call for a response. The communication does not suggest waiting, further observation, or informal resolution. It calls for action, and it does so in a manner that mirrors the enforcement framework already outlined by the City in its internal communications.
The email reflects a request that the matter be investigated. It calls for a formal review of what occurred and for that review to be conducted by law enforcement. It further indicates that the results of that investigation should be presented for legal evaluation, with the expectation that consequences would follow if the conduct met the applicable standard.
What is critical in this exchange is that the conduct is not treated as a mere violation of decorum or internal rules. It is tied directly to criminal law. The same statute, R.C. 2917.12, is invoked as the governing framework for evaluating the behavior. The conduct is framed as potentially criminal, and the pathway from identification to investigation to potential charges is clearly articulated.
There is no ambiguity in how the City approached the situation. The conduct is identified, it is labeled as unacceptable, it is connected to a criminal statute, and the expectation is that law enforcement will take the necessary steps to determine whether charges are warranted.
This response is not passive. It is not exploratory. It is structured and directive. It reflects a system that recognizes conduct it believes violates the law and moves immediately toward enforcement through the mechanisms it has already defined.
The significance of this record is not limited to the incident itself. It lies in how clearly it demonstrates the City’s willingness to act when it identifies conduct it believes falls within the scope of R.C. 2917.12. It shows the standard being applied in practice, with urgency, with clarity, and with a direct connection to criminal enforcement.
IV. TWO SETS OF RULES, ONE CONTINUOUS STANDARD
The Rules in effect in February 2025, the later revisions, and the internal email that confirms the law never changed
When the timeline is laid out correctly, the existence of two different versions of the Rules of Council does not create confusion about what standard applied. It clarifies that the standard never actually changed. The City of Lorain had already enacted Rules of Council governing the period from January 1, 2024 through December 31, 2025, and those Rules were fully in force at the time of the February 2025 Hilton incident. Those Rules were not informal or advisory. They were adopted by resolution and controlled how meetings were conducted, how disruption was defined, and how that disruption was to be addressed when it occurred.
Within those Rules, the City did not leave the concept of disruption open to interpretation or evolving standards. It incorporated Rule 47, which directly adopts the language of R.C. 2917.12 – Disturbing a Lawful Meeting, making clear that conduct which interferes with or obstructs a lawful meeting constitutes a criminal offense. That incorporation is critical because it establishes that, at the time of the February 2025 incident, the City had already tied its internal meeting rules directly to Ohio criminal law. There was no gap, no ambiguity, and no need for later clarification. The legal framework already existed and was already enforceable.
The Rules also imposed a duty on the Presiding Officer to maintain order and decorum during meetings. That duty included the authority to address disruptive behavior in real time, including directing removal when conduct interfered with proceedings. This was not a theoretical authority. It was a defined responsibility within a structured system that linked meeting conduct to enforcement mechanisms.
When the City later adopted a revised set of Rules extending beyond 2025 and into the next term, it did not create a new definition of disruption or a new connection to criminal law. It continued the same standard.
The later Rules refine procedure. They expand on documentation requirements, warnings, and how incidents must be recorded. They place additional emphasis on preserving the record of what occurred. But they do not alter the underlying definition of disturbing a lawful meeting, and they do not remove the direct connection to R.C. 2917.12. The same conduct that constituted disruption under the earlier Rules remains disruption under the revised Rules.
That continuity is not just reflected in the Rules themselves. It is reinforced in internal communications from City leadership, including the email authored by the Chief of Police, which addressed how meeting conduct is actually enforced.
That communication makes clear that law enforcement does not operate based on Council rules alone, but on criminal law. It explains that when individuals are removed or enforcement is initiated, it is not because they violated a procedural rule, but because their conduct rises to the level of a criminal offense. In doing so, it confirms that the operative standard has always been R.C. 2917.12, regardless of which version of the Council Rules was in effect.
Taken together, the Rules in effect during 2024–2025, the later revisions extending beyond 2025, and the internal enforcement guidance all point to the same conclusion. The City operated under a continuous and consistent legal framework governing disruptive conduct at public meetings. That framework defined the conduct, tied it to criminal law, and established the authority to act.
The February 2025 Hilton incident occurred squarely within that framework. The contemporaneous email describes disruption of a public meeting, refusal to leave when directed, and statements that were perceived as threatening, all tied to video evidence and communicated directly to City officials.
Those elements fall directly within the definition of disturbing a lawful meeting as it existed at the time and as it continues to exist under the revised Rules. The later adoption of updated Rules does not change that analysis. It confirms it.
The presence of two sets of Rules does not create two different standards. It demonstrates that the same standard existed before, during, and after the events in question. The definition of the conduct did not change. The authority to respond did not change. The connection to criminal law did not change.
What changed was how that same framework was applied once the conduct was placed in front of the City.
V. WHEN THE LAW IS FINALLY USED
July 2025 and March 2026, and the same two names attached to enforcement under a standard that already existed
The statute does not remain theoretical or unused within this record. At a certain point in the timeline, the City moves from defining the law and discussing enforcement to actually invoking it through criminal charges. That shift occurs first in July 2025, when Garon Petty is formally charged under R.C. 2917.12 – Disturbing a Lawful Meeting, marking the first clear instance within this sequence where the statute is applied in a prosecutorial context.
The timeline does not end there. On March 20, 2026, the same statute is used again, this time in connection with the October 20, 2025 council meeting, and the charges extend beyond a single individual. Both Garon Petty and Aaron Knapp are named in that enforcement action, with a warrant issued as part of the process moving the matter into the criminal system.
What is significant about this sequence is not simply that enforcement occurs. It is how that enforcement develops over time and who it is applied to. The statute is invoked more than once, across different meetings and different dates, but the names attached to those charges remain the same. The individuals who become the subjects of enforcement are the same individuals who appear repeatedly in earlier records, earlier complaints, and earlier communications where calls for action were made.
This continuity in enforcement stands in contrast to the February 2025 record. That earlier incident does not exist as an abstract comparison. It is documented in a contemporaneous email, it describes conduct that aligns with the same statutory framework, and it was communicated directly to City officials who had already defined how such conduct should be handled.
Within that email, the conduct is described as disruptive, involving a refusal to leave when directed, and including statements that were perceived as threatening, all supported by the assertion that video evidence existed. Those elements are not peripheral to the statute. They are the types of factors that form the basis for determining whether a lawful meeting has been disturbed.
The record shows that the February 2025 incident was reported, described, and placed before the same system that later produced charges. It shows that officials were notified and that the issue of enforcement was raised at the time. What it does not show is that the same enforcement process was initiated in response to that incident.
By the time charges are filed in July 2025 and again in March 2026, the legal framework is not new. The statute has already been defined, incorporated into the Rules, and discussed in internal communications. The difference is not the existence of the law or the authority to use it. The difference is when that authority is exercised and against whom.
The February 2025 incident remains in the record as it was when it was first documented. It is a report of conduct, a description of behavior that fits within the statutory framework, and a notification to officials responsible for enforcement. It exists within the same legal structure that later produces charges, but it does not result in a case.
The timeline therefore reflects not a change in the law, but a change in its application. The statute is used. It is enforced. It results in criminal charges. But when it is used, it is used in a way that attaches consistently to the same individuals, even as the record shows that similar conduct had been presented to the same officials at an earlier point in time.
VI. THE GAP BETWEEN THE RULE AND ITS APPLICATION
A conduct based statute that remains constant while the outcomes do not
When the full record is read from beginning to end, the standard itself is not unclear, disputed, or evolving. The City’s own communications, its adopted Rules of Council, and its internal directives all point to the same conclusion about how disruptive conduct at a public meeting is supposed to be handled. Disturbing a lawful meeting is defined as criminal conduct under R.C. 2917.12, and the process that follows that designation is not left to interpretation or informal judgment. The structure is laid out in the City’s own words, repeated across multiple documents, and reinforced over time without meaningful deviation.
That structure is consistent. Conduct is identified. Law enforcement investigates. The evidence is reviewed. Charges follow if the standard is met. This is not a theory of how enforcement might work. It is how the City itself described enforcement before any of the events now at issue occurred. It is reflected in internal emails, embedded in the Rules of Council, and confirmed by the way certain incidents were handled when the City chose to act.
The February 2025 email record describes conduct that, on its face, fits squarely within that framework. It identifies disruption of a public meeting, refusal to comply with a directive to leave, and statements that were perceived as threatening, all tied to the existence of video evidence. That information was not withheld or delayed. It was communicated directly to the same officials responsible for applying the law, placing the conduct inside the system that had already been defined for addressing exactly that type of behavior.
At the same time, the surrounding record shows how the City responds when it determines that conduct warrants action. In those instances, the reaction is immediate and direct. The conduct is labeled unacceptable. The statutory framework is invoked. The expectation is clearly expressed that law enforcement will investigate and that consequences will follow if the facts support that conclusion. There is no uncertainty in those responses. They reflect a system that recognizes conduct it believes meets the standard and moves forward accordingly.
By July 2025 and again in March 2026, that process is carried through. The statute is invoked in a criminal context. Charges are filed. The matter proceeds into the court system. The record leaves no question that the law can be applied and that the City is willing to apply it when it determines that enforcement is appropriate.
What emerges from this sequence is not a question about whether the statute exists or whether it can be enforced. Both are clearly established. The statute is defined, incorporated, and ultimately used. The question that remains is how the same framework produces different outcomes when similar elements are present.
The February 2025 incident does not exist as an abstract comparison. It is a documented report of conduct that aligns with the same statutory elements later used to support criminal charges. It was communicated at the time it occurred, directed to the appropriate officials, and framed within the same legal context. It placed the issue of enforcement directly in front of the system responsible for acting on it.
Yet it does not move forward.
By contrast, later incidents involving meeting conduct do move forward, and when they do, they result in charges against the same individuals who had already been the focus of prior complaints, prior communications, and prior calls for action. The pattern that develops is not based on a changing legal standard. The statute does not shift. The definition of disruption does not expand or contract. The authority to enforce remains the same throughout the timeline.
The difference is found in the application.
The record shows a conduct based statute that remains constant across multiple incidents, multiple meetings, and multiple years. It also shows that the outcomes tied to that statute are not consistent across those same circumstances. The law does not change between February 2025, July 2025, and March 2026. The framework does not change. The elements that define disruptive conduct do not change.
What changes is when the law is applied and to whom it is applied.
That distinction is not inferred. It is reflected in the record itself, where the same standard produces different results depending on the context in which it is invoked.
VII. FINAL THOUGHT
The City wrote the rule before it chose when to use it
The most important part of this record is not what is being argued now, after charges have been filed and positions have been taken. It is what was already written before any of that occurred. Long before July 2025 and long before March 2026, the City of Lorain had already defined what disturbing a lawful meeting meant, how that conduct should be evaluated, and what steps were supposed to follow when the elements of the statute were present.
The City did not leave that standard vague. It defined disturbing a lawful meeting as criminal conduct under R.C. 2917.12. It incorporated that definition into its Rules of Council. It reinforced it through internal communications. It outlined a process that required identification of the conduct, investigation by law enforcement, review of the evidence, and the filing of charges when the standard was met. That framework existed in writing, in multiple places, and in consistent terms.
The record also shows how the City responded when it identified conduct it considered unacceptable. In those instances, the reaction was immediate and direct. The conduct was labeled, the statute was invoked, and the expectation of enforcement was clearly stated. The system functioned exactly as it had been described.
What makes the February 2025 record significant is not that it introduces a new issue. It does not. It presents conduct that fits within the same framework the City had already defined. It describes disruption of a public meeting, refusal to comply with removal, and statements that were perceived as threatening, all supported by the existence of video evidence and communicated directly to the officials responsible for acting on that information.
The difference is what followed.
The process the City had already outlined does not appear in the record in response to that incident. The same sequence of investigation, review, and potential enforcement that had been described in earlier communications is not reflected in what occurred after that notice was given. The conduct was documented. The officials were notified. The legal framework was already in place. But the system did not move in the same way.
Then the charges came.
In July 2025, the statute was used to charge Garon Petty.
In March 2026, it was used again, this time charging both Garon Petty and Aaron Knapp for conduct tied to the October 20, 2025 meeting.
The law was not new at that point. The definition of the conduct had not changed. The authority to enforce it had already been established and reaffirmed. What changed was the moment at which that authority was exercised and the individuals to whom it was applied.
The record shows that the standard was never the issue. It was clearly defined, consistently stated, and repeatedly reinforced.
The application was.
Legal Disclaimer
This article is part of an ongoing investigative journalism series authored by Aaron Christopher Knapp and published by Knapp Unplugged Media LLC. It is based on documents obtained through lawful public records requests, including email correspondence, attachments, and related materials maintained by public offices. All factual statements contained herein are derived from those records or from the author’s direct involvement in the events described.
This publication addresses matters of public concern involving the conduct of government, the actions of public officials, and the administration of public records under Ohio law. Any analysis, interpretation, or conclusions expressed are the protected opinion of the author based on disclosed facts and a good faith review of the available evidence. To the extent that statements may be interpreted as opinion, they are presented as such and are grounded in the underlying record.
This article may reference individuals who are public officials, public employees, or participants in matters of public concern. All such references are made strictly in a journalistic context for the purpose of reporting, analysis, and public accountability. Nothing in this publication is intended as a direct communication to, or solicitation of action from, any public official, government employee, attorney, or party referenced herein.
Certain subject matter discussed in this article relates to ongoing legal proceedings. This publication is not intended to interfere with, influence, or prejudice any pending case, nor is it directed toward any court, judge, or tribunal. It is a work of journalism disseminated to the general public in furtherance of transparency and the public’s right to know.
No statement in this article is made with knowledge of falsity or reckless disregard for the truth. Allegations, claims, or statements attributed to third parties are identified as such and are included for the purpose of reporting on their existence within the documented record. Readers are encouraged to review the underlying materials and draw their own conclusions.
All content is published in accordance with the protections afforded by the First Amendment to the United States Constitution and corresponding provisions of Ohio law governing freedom of speech and freedom of the press.
This article does not constitute legal advice. Any references to statutes, case law, or legal standards are provided for informational and analytical purposes only.
© 2026 Knapp Unplugged Media LLC. All rights reserved. Unauthorized reproduction or redistribution of this material, in whole or in part, is prohibited without prior written permission, except as permitted under applicable fair use doctrines.
About The Author
