The Warrant That Isn’t There

A public records request, a reported search, and a system that cannot produce a document that should exist

By Aaron Christopher Knapp
Investigative Journalist | Lorain Politics Unplugged

I. INTRODUCTION

The Warrant That Isn’t There

There are moments in a public records investigation where the volume of material stops mattering and the focus narrows with precision onto a single document that should exist, a document that the law requires to be created, preserved, and accounted for, yet one that does not appear where it is supposed to be when a lawful request is made, and this is one of those moments where the absence of that document becomes more important than any amount of surrounding correspondence. The record that follows is not constructed from speculation or secondhand reporting but from direct email communications, formal requests made under Ohio law, and the written responses provided by the offices responsible for maintaining those records, and at the center of it is a search warrant that was reportedly issued, referenced in connection with a real world event, and treated as something that existed, yet cannot be located within the very system that is required to maintain it.

The request itself was precise and left no room for confusion about what was being sought or why it was being sought, because it identified a specific warrant, tied it to a specific timeframe in August of 2024, and connected it to a specific location involving Mercy Health in Lorain, and it was made explicitly under Ohio Revised Code 149.43, which governs access to public records and imposes clear obligations on public offices when responding to such requests. The law does not require the public to navigate internal systems or guess at how records are categorized, and it does not allow a public office to respond in a way that obscures whether a record exists or is being withheld, because when a record is denied the statute requires the agency to identify the record and cite the specific legal authority that justifies withholding it, and that requirement exists so that the response can be tested, challenged, and reviewed if necessary.

What the record shows is that this requirement was never met in a way that resolves the request.

Instead, the response moves through a series of explanations that describe the system without answering the question that triggered the request in the first place, beginning with the Clerk’s Office, which acknowledges that search warrants are maintained as a defined record series within its control and explains that those records are separated into sealed and unsealed categories, while also confirming that sealed warrants are physically restricted and cannot be accessed even by staff, and then stating that a search of unsealed warrants within the relevant timeframe produced no results connected to Mercy Health in Lorain. That response does not close the request because it does not place the specific warrant within the system it has just described, and instead introduces the possibility that the warrant may exist in sealed form while simultaneously confirming that no unsealed version can be located.

At the same time, the response from the City, issued through the office of Patrick Riley, does not engage with that framework or attempt to reconcile the absence of an unsealed warrant with the existence of sealed records, and instead states that the office has no records regarding a warrant involving Mercy Health and directs the requester to another office, which shifts the request without resolving it and leaves the question of custody unanswered. That is not a denial grounded in a specific statutory exemption and it is not a statement that the record does not exist, because it does not take a position that can be tested under the law, and instead operates as a transfer of responsibility that leaves the underlying issue intact.

What makes this moment different from every other record examined in this series is that a search warrant is not an informal communication or a discretionary document that may or may not be preserved depending on internal practices, because it is created through a defined legal process that requires an application, judicial review, sworn statements, and formal authorization, and it is then filed within a system that exists specifically to preserve that record as part of the official record of the court. Whether a warrant is sealed or unsealed affects access to its contents, but it does not eliminate its existence within that system, because the classification of a record does not remove it from the structure that is required to maintain it.

And yet, that is where this record now sits, not within a clearly defined category of sealed or unsealed records, not identified by any office as existing or not existing, but in a position where the system has described how it would be stored without ever confirming that it is there.

Because if the warrant exists, it should be identifiable within the system that maintains such records, and if it is sealed there should still be confirmation of its existence within the framework that governs sealed records even if its contents are restricted, and if it does not exist then the references to it and the actions attributed to it raise a different set of questions that move beyond access and into accuracy. The record presented here does not resolve which of those outcomes is true, and what it shows instead, clearly and without interpretation, is that the question was asked directly, repeatedly, and under the authority of Ohio law, and the system responsible for answering that question did not provide a definitive answer.

This is not an isolated issue confined to a single request or a single document, because the handling of this warrant exists within a broader pattern that raises the same concerns about how warrant related records are identified, maintained, and disclosed, including issues that have arisen in connection with other warrants tied to this reporting, where the same absence of clear answers, the same shifting of responsibility, and the same failure to provide a legally sufficient response begin to appear across different requests involving different events but the same underlying system.

That is where this story begins, not with a theory, but with a record that shows a request made under the law, a system that explains itself without resolving the request, and a document that should exist but cannot be placed where the law says it should be.

24 Download

II. THE REQUEST THAT SHOULD HAVE PRODUCED A RECORD

The sequence begins in a way that is both routine and legally precise, because a public records request is issued that does not wander, does not speculate, and does not ask for interpretation, but instead identifies a single document tied to a defined event, a defined timeframe, and a defined legal basis for disclosure, using language that is direct and unmistakable in what it seeks. The request calls for “the full and complete warrant request served to Mercy Hospital during the month of August 2024 per 149.43 ORC,” and in doing so it removes any ambiguity about what is being requested and why the request is being made under Ohio law.

That level of specificity matters because it triggers a corresponding level of obligation on the part of the public office, since under Ohio Revised Code 149.43 once a request is sufficiently clear the burden shifts entirely to the agency to respond in a way that resolves the request, not in a way that reframes it or redirects it, but in a way that produces the record, states that the record does not exist, or identifies the exact legal exemption that justifies withholding it. The statute does not allow a response that leaves the requester in a position where they cannot determine what happened to the record, because the entire structure of the law is built around the idea that the response must be clear enough to be tested, challenged, and, if necessary, reviewed by a court.

What the record shows instead is a request that moves through multiple offices without ever reaching that point of resolution, beginning with outreach to the Clerk of Courts and then expanding outward to include the Sheriff’s Office, the Law Department, and a wide range of city officials, with the same question being carried forward across each step of that communication without ever being answered in a way that satisfies the statute. The emails show the request being repeated, clarified, and reinforced, but the core issue never changes, because it remains centered on a single, unavoidable question, which is whether a warrant was issued and, if so, where that warrant is maintained and why it is not being produced.

The initial response from the Clerk’s Office does not resolve that question, because it states that there are no records available for public access that are responsive to the request, and that phrasing is not the same as stating that no record exists, since it introduces a distinction between the existence of a record and the accessibility of that record without explaining which of those conditions applies in this case. The request is not clarified through that response, and it is not closed, because it leaves open the possibility that the record exists but is not being made available, while failing to identify the legal basis for that position.

That lack of resolution drives the request outward, leading to additional officials being copied, additional offices being brought into the chain, and the same question being asked again in more direct terms that focus not on the document itself but on the system that is supposed to hold it, including questions about who is the keeper of the record, which office is responsible for maintaining it, and where the warrant would be located if it had in fact been issued. These questions are not rhetorical and they are not speculative, because they are grounded in the way search warrants are processed, approved, and filed, which is a process that necessarily creates a record at each stage and assigns responsibility for maintaining that record within a defined system.

A warrant is not created in isolation and it does not exist outside of that system, because it is applied for through an affidavit, reviewed by a judge, authorized under oath, and then filed as part of the official record of the court, and each of those steps creates documentation that must be preserved, whether the final warrant is sealed or unsealed. That is why the request continues to press for identification of the custodian, because once the custodian is identified the legal obligation becomes unavoidable, and the question can no longer be redirected without being answered.

Instead of identifying that custodian, the responses continue to shift in a way that keeps the request moving without resolving it, with the Clerk’s Office acknowledging that it maintains search warrants as a record series and then distinguishing between sealed and unsealed warrants, while confirming that sealed warrants are physically restricted and cannot be accessed even internally, and at the same time confirming that a search of unsealed warrants within the relevant timeframe produced no result connected to Mercy Health in Lorain. The existence of sealed warrants is acknowledged as part of the system, but the response stops short of confirming whether the specific warrant being requested falls within that category.

At that point, the request reaches a critical threshold where the system has established several key facts without resolving the issue that triggered the request, because it has confirmed that the type of record being sought exists as a defined category within the system, it has confirmed that no unsealed version of that record can be located within the relevant timeframe, and it has introduced the possibility of sealed records without confirming whether the requested warrant exists in that form.

What it has not done is answer the question that was asked.

That is the point where the request stops being routine and begins to expose a structural problem, because the process has been followed, the request has been made clearly under the law, and the system has responded in a way that describes itself without resolving the issue, leaving the record in a position where it cannot move forward and cannot be closed.

III. WHEN THE ANSWERS STOP ANSWERING THE QUESTION

By the time the request reaches this stage, the issue is no longer whether the question itself is clear or properly framed, because the record already establishes that the request identified a specific document, a specific timeframe, and a specific legal basis, and instead the issue becomes whether any office involved in the chain of communication is willing to take ownership of providing a complete answer that satisfies the requirements of Ohio law. What begins to emerge in the emails is a shift away from identifying facts tied to the requested warrant and toward managing responsibility in a way that allows each office to respond within a limited scope without resolving the request as a whole, and the same question continues to move through the same group of officials while the responses become increasingly narrow and controlled in how they address it.

The Clerk’s Office provides the most detailed explanation anywhere in the record, and that explanation is structured, technical, and grounded in how the system is designed to operate, because it confirms that search warrants are maintained as a defined record series, explains that those records are divided into sealed and unsealed categories, and states that sealed warrants are physically inaccessible even to staff because they are enclosed and restricted by court order, while also confirming that a search of unsealed warrants within the relevant timeframe produced no results connected to Mercy Health in Lorain. That level of detail gives the appearance of completeness, but it does not resolve the request, because it explains how warrants are handled in general without placing the specific warrant being requested within that system.

The explanation therefore creates a framework without producing an outcome, because it establishes that no unsealed warrant can be found while acknowledging that sealed warrants exist as a category, yet it does not confirm whether the requested warrant exists in sealed form, and it does not state that no warrant exists at all, leaving the request suspended between two possibilities without identifying which one applies. The absence of an unsealed record is established, but the existence or nonexistence of a sealed record remains unaddressed, and that omission is the one point that prevents the request from being resolved.

At the same time, the City’s response moves in a different direction that does not connect to the framework provided by the Clerk’s Office, because through the office of Patrick Riley the position taken is that no records exist within that office related to a warrant involving Mercy Health and that the request should be directed elsewhere. That response does not engage with the explanation already provided regarding how warrants are stored, it does not reconcile the absence of an unsealed warrant with the possibility of a sealed one, and it does not attempt to identify where within the system such a record would be located if it exists, and instead it removes the Law Department from the chain of custody without addressing the underlying issue.

The result is a record that now contains two positions that operate independently of each other without ever being reconciled, because one office explains the structure of the warrant system and confirms that no unsealed record can be located, while another office states that it has no records and redirects the request, and neither position answers whether the warrant exists, neither position identifies the custodian if it does, and neither position provides a specific legal citation for withholding the record in the event that it is being withheld.

That is where the breakdown becomes visible in a way that cannot be attributed to misunderstanding or lack of clarity, because under Ohio law a public office is not permitted to respond to a records request by describing the system in general terms while avoiding the outcome required by the statute, since the obligation imposed by R.C. 149.43 is not to explain process in the abstract but to respond to the request itself in a way that resolves it. If the record exists, the office must produce it or cite the law that allows it to be withheld, and if the record does not exist the office must state that directly, and if the office is not the custodian it must identify who is so that the request can be properly directed.

What the record shows instead is a set of responses that each satisfy a portion of that obligation while avoiding the full requirement, because the Clerk provides a process explanation without confirming existence, the Law Department disclaims possession without identifying the custodian, and the request continues to move without reaching a point where it can be closed or challenged in a meaningful way. The result is not a clear denial that can be tested in court and not a production that can be reviewed, but a space in between where the request remains active, the record remains unproduced, and the answer never arrives.

That is not a failure of communication or a misunderstanding of what was being asked.

It is a failure to provide an answer that the law requires to be given, and it reflects a gap in accountability that becomes visible only when the record is examined as a whole rather than as a series of individual responses.

IV. WHEN THE RECORD POINTS IN TWO DIRECTIONS AT ONCE

At this point in the record, the issue is no longer confined to what the government says it can locate within its own system, because the request did not originate in a vacuum and it was not based on speculation or theory, but instead followed descriptions of an event that had already been treated as real, discussed as real, and referenced in a way that assumes the existence of a corresponding warrant. The request did not create that event and it did not invent the underlying facts, because it was made in response to statements and circumstances that indicated a warrant tied to Mercy Health in Lorain had been issued and used, and that is what brings the record to the point where the contradiction becomes unavoidable.

What emerges here is not a disagreement over interpretation or a delay in processing, but a situation where two separate realities are reflected in the same record and cannot be reconciled without a definitive answer that has not been provided. On one side of the record there are statements and references that treat the warrant as something that exists, something that was issued and acted upon, and something that formed the basis for the request itself, and on the other side there is a formal search of unsealed warrant records that produces no result, combined with an explanation that sealed warrants are inaccessible even to staff and a separate statement from the Law Department that no such records exist within its possession.

That is not a routine denial and it is not a simple delay in locating a document, because it reflects a structural conflict between what is being described as having occurred and what can be identified within the system that is required to document it. The system itself has already defined the only two ways a warrant can exist within that framework, which means that once the unsealed records have been searched and found to contain nothing, the only remaining possibility within that system is that the warrant exists in sealed form under a court order, and if that is the case then its contents may be restricted but its existence is not erased and must still be acknowledged in a way that satisfies the law.

The distinction between existence and accessibility becomes critical at this stage, because the explanation provided does not confirm that a sealed warrant exists in this case and does not state that no warrant exists at all, and instead leaves the request positioned between those two outcomes without identifying which one applies. A sealed record is still a record that exists within the system, and while access to its contents may be restricted, the classification itself does not remove the record from the system or eliminate the obligation to respond to the request in a way that identifies its status.

If the warrant does not exist, then the problem moves in the opposite direction and becomes one of accuracy rather than access, because the references to a warrant, the descriptions of its use, and the basis for the request itself would no longer be supported by a record that can be identified within the system that is supposed to maintain it. That outcome carries its own implications, because it would mean that the event being described does not align with the records that are required to document it, and that disconnect becomes part of the record as well.

This is the point where the record stops being passive and begins to carry weight on its own, because the absence of the document is no longer neutral and cannot be explained away as a matter of timing or process, and instead forces a choice between two explanations that lead in very different directions. Either the warrant exists and is being withheld without a clear statement of legal authority that complies with Ohio law, or the warrant does not exist in the way it has been described and the record that should document it cannot be produced.

The emails themselves do not resolve that choice and do not attempt to resolve it, because the Clerk explains how the system works without placing the warrant inside it, the Law Department removes itself from custody without identifying where the record would be located, and the request continues to press the same question without receiving a definitive answer. No one confirms that the warrant exists in sealed form, and no one states that it does not exist at all, and that leaves the record in a position where it points in two directions at once without committing to either.

That is the moment where the issue shifts from access to accuracy, because a public records request is not only a mechanism for obtaining documents but also a way to test whether the official version of events can be matched to the records that are supposed to document those events. When those two things do not align, the gap between them becomes the focus of the inquiry, and the absence of a clear answer becomes the most significant part of the record.

In this case, that gap is no longer incidental and it is no longer avoidable, because it is the only part of the record that has not been resolved, and it is now the only place where the truth of what happened can be determined.

V. THE LEGAL OBLIGATION THAT NEVER GETS MET

By the time the record reaches this point, the issue is no longer about whether a document can be located through additional searching or whether another email might produce a different answer, because the process itself has already been completed in a way that allows the legal obligations to be measured against what actually occurred, and the question becomes whether those obligations were ever satisfied at all. Ohio Revised Code 149.43 does not permit partial compliance, informal explanations, or responses that describe a system without resolving the request, because it imposes a direct and enforceable duty on the public office to respond to the request itself, not to the general subject matter surrounding it and not to the internal structure of how records are maintained.

That duty is not abstract and it is not discretionary, because it is defined in clear terms that require a specific outcome depending on the status of the record being requested. If the record exists and is not exempt from disclosure, it must be produced. If the record is being withheld, the public office must provide a written explanation that identifies the record and cites the specific legal authority that justifies withholding it. If the office does not maintain the record, it must identify the correct custodian so that the request can be directed to the office that does. These are not options that can be selected based on convenience, because they are the minimum requirements imposed by the statute to ensure that a request can be evaluated, challenged, and enforced if necessary.

What the record shows here is a series of responses that approach each of those requirements without ever completing any of them, which creates the appearance of engagement without producing the outcome required by law. There is no production of the warrant that was requested. There is no written denial that cites a specific statutory exemption applicable to that warrant. There is no definitive identification of the custodian who holds the record if it exists. Instead, the responses move between categories, with the Clerk’s Office explaining how warrants are stored without confirming whether this warrant exists within that system, and the Law Department, through the office of Patrick Riley, stating that it has no records and suggesting that the request be directed elsewhere, while other officials remain part of the communication without providing a statement that resolves the issue.

That pattern is what makes the legal problem unavoidable, because the statute does not measure compliance based on the number of responses or the level of effort shown in addressing the request, and it does not allow a public office to satisfy its obligation by explaining why a record might be difficult to locate or by describing the categories under which it would be stored. Compliance is measured by outcome, and the outcome required by the statute is a response that allows the requester to determine whether the record exists, whether it is being withheld under a specific legal authority, or where it is maintained if it is not held by the responding office.

A response that leaves the requester unable to determine any of those things is not a complete response under the law, because it cannot be tested, it cannot be challenged in a meaningful way, and it does not provide the information necessary to enforce the statute. That is exactly what the record reflects in this case, because the request remains unresolved not due to a lack of clarity but because the responses never reach the point where the law requires them to go.

The emails themselves show that this deficiency was recognized as it was happening, because the request was not simply repeated in the same form but was refined to address the specific requirements of the statute, with the distinction between existence and withholding being raised directly and the obligation to cite the legal authority for any denial being stated in clear terms. The statement “I see no Laws being quoted on your denial… STATE THE LAW” is not a general demand for explanation and it is not an expression of frustration detached from the legal framework, because it is a direct invocation of the requirement imposed by R.C. 149.43(B)(3) that a public office must provide a written explanation that includes the legal basis for withholding a record.

What follows that statement does not satisfy that requirement, because no specific statutory exemption is identified, no written denial is issued that can be evaluated under the law, and no position is taken that allows the request to move forward through the mechanisms provided for enforcement. Instead, the structure of the response avoids creating a position that can be challenged, because there is no clear denial to contest, no production to review, and no identified custodian to pursue directly, leaving the request active without providing a path toward resolution.

That is not the result of a misunderstanding or a breakdown in communication, because the record shows that the legal requirements were stated clearly and repeatedly, and it shows that the responses stopped just short of meeting those requirements at each stage. What remains is a record that reflects a request made in compliance with the law and a series of responses that do not meet the standard that the law imposes, which is what transforms the issue from a question of access into a question of compliance.

VI. WHEN RESPONSIBILITY IS DISTRIBUTED AND ACCOUNTABILITY DISAPPEARS

As the emails continue, the structure of the response becomes more revealing than the content of any single reply, because what begins as a direct request directed toward a records custodian evolves into a layered communication that includes multiple officials, multiple departments, and multiple levels of government, with the same names appearing repeatedly across expanding email chains while additional recipients are added at each stage. What should have remained a focused interaction between a requester and the office responsible for maintaining the record instead becomes a distributed exchange in which responsibility is shared across participants but never fully assumed by any one of them, and that shift changes how the request is handled in a way that becomes visible only when the record is viewed as a whole.

This expansion is not incidental and it is not neutral in its effect, because once multiple offices are involved each one gains the ability to define its role narrowly and respond only within the limits of its own function, which allows the overall obligation imposed by Ohio law to be fragmented into smaller pieces that do not independently resolve the request. The Clerk’s Office explains how warrants are filed and categorized within its system, the Law Department through the office of Patrick Riley states that it has no records in its possession and suggests the request be directed elsewhere, and other officials remain included in the communication but do not intervene in a way that consolidates those responses into a single position that answers the question being asked. The request becomes visible to everyone involved in the chain, yet no one provides a response that brings the inquiry to a conclusion.

The record shows this pattern clearly through the progression of the communication, because questions about custody are raised directly and repeatedly in a way that reflects the structure of how such records are supposed to be maintained, including questions about who holds the warrant, which office is responsible if the Clerk does not have it, where a sealed warrant would be maintained if it exists in that form, and where the record would be filed if it had been issued. These questions are not abstract or rhetorical, because they are the necessary steps required to identify the record within a system that has already been described in detail by the offices responding to the request.

What follows from those questions is not a refusal to engage with the request in an overt sense, but something more structured and more difficult to identify at a glance, because each office responds within the boundaries of its own defined role and provides an answer that is technically accurate within that limited scope while avoiding the broader obligation to resolve the request in full. The Clerk can state that no unsealed warrant was found within the timeframe searched, the Law Department can state that it has no records within its possession, and other offices can remain silent or defer without taking a position, and each of those responses can stand on its own without being incorrect in isolation. When those responses are viewed together, however, they do not connect in a way that answers the central question.

This is how accountability disappears without any single office explicitly denying the request, because the system is not required to function as a collection of isolated responses, and under Ohio law a public records request is directed at the public office as a whole, not at individual departments acting independently of each other. The obligation to provide a complete and legally sufficient response remains collective even when records are maintained across different offices, and the presence of multiple custodians does not diminish that obligation but instead makes coordination necessary to ensure that the request is resolved.

What the record shows instead is a structure in which that collective obligation is fragmented across multiple actors, allowing the request to be passed, copied, and redirected without ever reaching a point where it is answered in full. No single office claims responsibility for providing a complete response, and no single official issues a statement that reconciles the positions already reflected in the record, leaving the request in a position where it cannot be closed and cannot be meaningfully challenged because no definitive answer has been given.

The result is a response that exists everywhere and nowhere at the same time, because every participant in the communication is aware of the request and is part of the exchange, yet no one provides the answer that the law requires. The communication continues, the record expands, and the question remains unresolved.

This is not a failure of coordination or an isolated breakdown in communication, because the pattern reflects a structure that allows the question to remain open without ever being formally denied, which prevents the request from reaching the point where it can be tested under the law while still creating the appearance that it has been addressed.

VII. WHAT THE RECORD REQUIRES IF IT IS TAKEN SERIOUSLY

By the end of this exchange, the issue is no longer something that can be explained away through interpretation, delay, or internal process descriptions, because the record itself has now established the framework within which the request must be resolved if the law is applied as written, and that framework leaves only a limited number of outcomes that are legally sufficient, each of which requires a clear and direct statement that has not been made anywhere in the communication. The emails have already defined the system, the categories of records, and the obligations imposed by Ohio Revised Code 149.43, which means the question is no longer what might be happening but what must be said to bring the request into compliance with the statute.

If the warrant exists and is unsealed, then the obligation is immediate and non discretionary, because a search warrant that has been filed and is not subject to a sealing order is a public record that must be produced upon request, subject only to limited redactions where specific exemptions apply, and it cannot be withheld in its entirety without a written explanation that identifies the legal authority justifying that withholding. The absence of production in that scenario is not a matter of interpretation but a failure to comply with the statute, because the law does not allow an unsealed warrant to exist without being produced when properly requested.

If the warrant exists and is sealed, then that fact must be acknowledged in a way that satisfies the requirements of the statute, because while the contents of a sealed warrant may be restricted by court order, the existence of the warrant itself is not erased by that classification, and a response that merely describes sealed warrants as a general category does not resolve a request for a specific document. The response must address whether the requested warrant falls within that category and must do so in a way that allows the requester to understand that the record exists but is restricted, because a sealed record is not a nonexistent record and the distinction between those two conditions is central to compliance under Ohio law.

If the warrant does not exist, then that must be stated directly and unambiguously, because the statute does not permit a public office to imply nonexistence through silence or through the absence of results in a limited search, and it does not allow the question to remain open where the record should either be produced or definitively identified as not existing. A statement that closes the question is required to bring the request to an end, and without that statement the request remains unresolved as a matter of law.

What the record shows is that none of these positions have been taken in a way that satisfies those requirements, because the responses move around each possibility without committing to any of them, leaving the request in a state where it cannot be advanced and cannot be closed. The Clerk confirms that no unsealed warrant was located within the timeframe that was searched but does not state whether a sealed warrant exists, and the Law Department, through the office of Patrick Riley, states that it has no records without reconciling that position with the broader system that maintains warrants as a defined record series, while other officials remain part of the communication without providing a statement that resolves the conflict.

That leaves the request in a position where it exists in a kind of procedural limbo, because it has been made clearly under the statute and has triggered the obligations imposed by that statute, yet the responses provided do not meet the threshold required to satisfy those obligations, and the absence of a definitive answer prevents the request from being tested, challenged, or closed through the normal mechanisms of compliance.

This is the point at which the legal consequences begin to take shape, because a public records request that is not answered in a legally sufficient manner does not simply disappear or lose its force over time, and instead creates a record of non compliance that can be examined independently of the underlying request. The emails establish that the request was made, that the statutory requirements were invoked, and that the responses provided did not resolve the request in a way that satisfies the law, and that record becomes the basis for enforcement through the courts.

The communication itself shows that this step was anticipated as part of the process, because references to filing a writ of mandamus appear directly in the emails, not as a hypothetical escalation but as the mechanism provided under Ohio law to compel a public office to either produce the requested records or justify their withholding under a specific legal authority. A writ of mandamus is not an extraordinary measure in this context, because it is the enforcement tool built into the statute to address precisely the type of situation reflected in this record, where a request has been made and the response has not satisfied the legal requirements imposed on the public office.

That is the point the record has now reached, not because of tone, not because of escalation in the language of the emails, but because the process required by law has been followed and has not produced an answer that satisfies the statute. The request has been made, the system has responded, and the response has not resolved the request in a way that allows it to be closed or tested.

What remains at this stage is not another round of communication within the same structure, because that structure has already demonstrated that it will not produce a definitive answer.

What remains is a question that now has to be answered somewhere else, within a forum where the obligation to answer cannot be avoided by shifting responsibility or limiting the scope of the response.

VIII. FINAL THOUGHT

The Record Does Not Leave Space for Both

At this point, the record stands on its own in a way that does not depend on interpretation, outside context, or additional explanation, because every relevant piece necessary to evaluate what happened has already been placed into the record through the request, the responses, and the descriptions provided by the very offices responsible for maintaining the system at issue. The request is documented in clear and specific terms, the responses are preserved in full, and the structure of how search warrants are categorized, stored, and restricted has been explained directly by those charged with maintaining those records, which means there is nothing missing from the process itself that would prevent the request from being resolved under the law.

What is missing is the answer.

A search warrant tied to a defined event was requested under Ohio law, and the response from the Clerk’s Office confirmed how such warrants are maintained as a record series, explained the distinction between sealed and unsealed records, and stated that no unsealed warrant could be located within the relevant timeframe, while also acknowledging that sealed warrants exist without confirming whether the requested warrant falls within that category. At the same time, the City, acting through the office of Patrick Riley, stated that it has no records related to such a warrant and directed the request elsewhere, without reconciling that position with the system that has already been described or identifying where such a record would be maintained if it exists. The request was repeated, clarified, and framed in direct reference to the requirements of Ohio Revised Code 149.43, including the obligation to cite the legal authority for any denial, and no such citation was provided.

That is the record as it exists.

And the record does not leave space for multiple outcomes to exist at the same time, because the system that has been described allows for only a limited number of possibilities, each of which requires a clear statement that resolves the request. Either the warrant exists within that system, in which case it exists in a form that is recognized by that system as either sealed or unsealed and must be identified as such in a way that complies with the law, or it does not exist within that system at all, in which case the references to it, the basis for the request, and the actions described in connection with it stand without a corresponding record where one is required to be maintained.

The record cannot support both positions at once, and it cannot remain in a state where both possibilities are left open without resolution.

What the record shows instead is a response that avoids choosing between those outcomes, because the explanation of the system is provided, the categories of records are defined, the offices involved are identified, and the question that triggered the request is never answered in a way that satisfies the statute. The request does not fail because it lacked clarity, and it does not fail because it was directed to the wrong office, because the communication itself shows that the request was understood, expanded, and circulated among the officials who would be expected to resolve it. It remains unresolved because no one takes the final step required by law to state whether the record exists, whether it is being withheld under a specific legal authority, or where it is maintained if it is not held by the responding office.

That is where this leaves the story, not at the beginning of a dispute and not at the conclusion of one, but at the point where the record has fulfilled every requirement imposed on it by the law and the system responding to it has not provided the answer that the law requires.

The record does not move backward once it reaches that point, because it does not become less clear over time and it does not lose the question that was asked, and instead preserves that question exactly as it was presented and fixes it in place in a way that cannot be undone by later explanations that do not directly address it. Once the record is complete in that way, it does something that no description of process or internal procedure can overcome.

It forces a choice that cannot be avoided.

Because what remains after this is not another response within the same structure that has already failed to resolve the request, but the question of whether the answer will ever be given in a forum where it is required to be given under the law.

LEGAL DISCLAIMER:

This article is a work of investigative journalism based on public records, direct communications, and supporting documents obtained through lawful means, including requests made pursuant to Ohio Revised Code 149.43. The material presented reflects the author’s analysis and interpretation of the documented record and is published in the public interest.

Certain matters referenced in this publication are the subject of ongoing litigation and administrative proceedings. Nothing contained herein is intended to interfere with, influence, or circumvent any pending legal action, nor should it be construed as a filing, argument, or submission to any court or tribunal. All statements are made outside of judicial proceedings and are presented solely for journalistic and informational purposes.

References to named individuals, including public officials and candidates for office, are made in connection with matters of public concern. Any conclusions drawn are expressly presented as opinion based on disclosed facts and are protected under the First Amendment to the United States Constitution and Article I, Section 11 of the Ohio Constitution. No statement should be interpreted as a definitive assertion of criminal liability unless expressly supported by cited law and adjudicated findings.

This publication does not constitute legal advice. All individuals and entities are presumed innocent unless and until proven otherwise in a court of law. The author reserves the right to update, correct, or expand upon this material as additional records become available.