About

The Ayres River Editorial Team

We are a small editorial team writing about hydrology, rivers, and water-resources engineering. We work from primary sources, we cite them, and we are explicit about how we use AI tooling.

Who we are

Ayres River Blog is published by the Ayres River Editorial Team, an editorial group rather than a single author. We write for practitioners, students, and the engineering-curious, and we keep the scope tight: how water moves through catchments, where and why it floods, how water resources are managed, and how rivers are restored.

We are not a university department, a consultancy, or a government agency, and we do not present ourselves as one. We are an independent editorial operation. Where a topic calls for specialist judgement, the relevant article is reviewed by a qualified water-resources engineer before it is published, and that review is noted in the byline.

How we use AI, honestly

We use AI tooling as part of our workflow, and we think readers deserve to know exactly how. We do not hide it behind a fictional author, and there is no invented person, photograph, or credential anywhere on this site.

AI-assisted, human-reviewed. We use AI tooling for research synthesis and first drafts. Every article is then checked, corrected, and edited by the editorial team, and articles that carry engineering judgement are reviewed by a qualified water-resources engineer. The data, calculations, citations, and conclusions are our responsibility, not the model's.

In practice that means AI helps us gather and summarise source material and produce an initial draft. It does not get the final word. We verify figures against the cited references, we remove claims we cannot support, and a human signs off before anything is published. When we get something wrong, we correct it and say so.

What we stand by

Evidence first

We work from primary sources such as USGS, WMO, FEMA, and peer-reviewed literature, and we cite them so you can check our work.

Honest uncertainty

Where an estimate carries a wide error band, we say so. We would rather report a range than imply a precision we do not have.

Plain explanation

Technical does not have to mean opaque. We explain the mechanism and the assumptions, not just the conclusion.

Corrections welcome

If you find an error, tell us. We update articles when the evidence changes and note material corrections.

Editorial standards

You can start with our recent explainers: meandering vs braided rivers, the 100-year flood explained, and nature-based solutions for flood risk reduction.

Image credits

Get in touch

Corrections, source suggestions, and questions are all welcome. Write to [email protected].

We read everything, even if we cannot reply to all of it.