How This Was Built

If you read the previous page, you know what these clinical guides are for. This page is about how they were actually produced — the real workflow, including a mistake we made and corrected, because we think that correction is the strongest evidence we can give you that this process holds up.

The Thesis: Neither Half Works Alone

These 46 regional clinical guides were built through iterative collaboration between AI and human judgment — not AI running unsupervised, and not a solo human trying to hand-compile toxin data, symptom timelines, and treatment notes across dozens of regions and hundreds of species from scratch. Both halves of that description matter, and neither one is decoration.

AI does the fast data collection and cross-checking: pulling species and toxin data, checking it against itself across passes, flagging inconsistencies, restructuring hundreds of entries into a consistent format. A human — the founder — does the direction: deciding what counts as good enough to ship, catching claims that sound right but aren't actually backed by anything, and repeatedly sending work back for another verification pass before it goes live. That back-and-forth isn't a one-time step. It's the actual production loop, guide by guide, region by region.

State this plainly, because it's true and it's not a hedge: AI without a human applying direction and skepticism to its output would ship confident-sounding errors at scale. A human without AI's speed at collecting and cross-checking data across 46 regions and hundreds of species would either take years to do this alone or would have to cut so many corners that the coverage wouldn't be worth having. Put together, each one covers the other's actual weak point. That combination is why this exists at all, and why it's built the way it's built — not because "AI is the future" in some abstract sense, but because this specific problem, at this specific scale, needed both a fast collector and a skeptical editor, and one person filling both roles alone in either direction would have produced something worse than what you're looking at.

The "Physician Reviewed" Correction — A Case Study

Here's the concrete example, told straight, because it's the clearest proof of the process we can offer.

Earlier versions of these clinical guides carried a "physician reviewed" label. We removed it. Not because a physician found something wrong with the data — because the claim itself couldn't actually be verified or backed up. Nobody could point to a specific physician, a specific review date, or a specific record of what was reviewed and how. It was a label that implied a process that hadn't actually happened, or at least hadn't happened in any form we could stand behind if someone asked us to prove it. So we corrected it.

What replaced it is the accurate description of what actually happened: the data was AI-collected and confirmed accurate through our own verification process. That's a claim we can actually explain and stand behind — what the verification process consists of, how entries get cross-checked, what happens when something doesn't hold up. And we didn't stop at fixing the header disclaimer. We went through all 46 regional clinical guides and added source notes near the individual data entries throughout — not one blanket disclaimer sitting at the top of a page where nobody reads it, but sourcing context attached to the specific pieces of data it applies to, where a clinician actually encounters them.

We're framing this correction as a feature of the process, not an embarrassment to bury. A claim that couldn't be substantiated got caught and fixed before it caused harm — that's the system working, not the system failing. The standard going forward is simple and it doesn't have exceptions: claims on this site should be ones we can actually back up. If we can't explain exactly what stands behind a claim, we don't make it. "Physician reviewed" failed that test. "AI-collected and confirmed accurate through our own verification process, with source notes at the entries themselves" passes it, because every part of that sentence is something we can actually show you.

Why This Is More Credible, Not Less, to a Skeptical Clinical Reader

If you're a physician, an EMT, a poison control staffer, or a hospital administrator, you have every professional reason to be cautious about unverified claims — that caution is exactly the instinct your training built into you, and it's the right instinct to apply here too. So apply it, and compare the two options honestly.

Option one: a vague "reviewed by a professional" claim with no name, no date, no record of what was reviewed, and no way for you to check any of it. You either take it on faith or you don't, and if you're the kind of clinician worth trusting, you don't take unverifiable claims on faith. That kind of label tells you nothing you can act on — it's a badge, not evidence.

Option two: an explicit, checkable description of the actual process — AI-collected data, a stated verification methodology, source notes attached at the level of the individual entry, and a public record of a specific claim being caught and corrected when it didn't hold up. You can evaluate this. You can disagree with a specific sourced entry and tell us, and we'll look at it — that's what the clinician feedback and physician-review pathways on this site are for. You can see, in the correction itself, that when something on this site didn't pass the "can we back this up" test, it got fixed instead of quietly left in place.

A process that shows its own correction is more credible than a claim that can't be checked at all. That's not a hedge or a consolation prize for not having a formal review board — it's a straightforward claim about which kind of evidence a careful reader should trust more, and we think a clinician's own professional judgment, applied honestly, lands in the same place.

Why the Guides, the Search Portal, and Scout Exist at All

None of this — the clinical reference guides, the search portal, or the AI reference assistant — exists to make the clinical call for you. They exist to help you find accurate information fast, so your own judgment has better material to work with in the moment it matters. A clinician standing in front of a patient with a suspected mushroom ingestion still makes the call. These tools narrow the search, surface the relevant species and toxin data, and get you to a starting point faster than working through a general toxicology reference from scratch — they don't replace the assessment, they support it.

That's the same principle that governs how this site itself gets built. AI collects and cross-checks fast; the founder decides, corrects, and takes responsibility for what ships. The tool doesn't make the call. The person using it does. We built the guides that way on purpose, because it's the same relationship we think a clinician should have with any reference tool, including this one.