How we write

Scubaspot is a small team building a dive log app. We do not have a travel desk, and we would rather say so than pretend. The destination and wreck articles on this blog are written by an AI model, from public sources, with automated checks and no human editor. This page explains exactly how, so you can decide how much weight to give them.

Where the facts come from

Every article starts from a fact sheet assembled from open, attributable sources. Nothing is scraped from dive operators, magazines, review sites or booking platforms.

• Wikipedia and Wikivoyage for the history of a wreck and the shape of a destination. Both are licensed CC BY-SA 4.0. We use them as sources of fact and write fresh text; each article links the pages it drew on.
• Wikidata for structured facts: dates, dimensions, positions, countries. CC0.
• Wikimedia Commons for photographs, only under licences that allow reuse. The photographer and licence appear under every image.
• Open-Meteo for the month-by-month sea temperature and wave height tables, computed for the coordinates of the place in the article from the last twelve months of marine weather data. CC BY 4.0.

How an article is made

• A topic is picked from Wikivoyage's diving guides, Wikipedia's articles on dive sites by country, or Wikipedia's list of wreck diving sites. Articles too short to support a post are skipped.
• The fact sheet is built from the sources above.
• A language model writes the article from the fact sheet and nothing else. It is instructed to leave out anything the sources do not say rather than fill the gap.
• Automated checks reject the draft if it contains a number that is not in the fact sheet, a link to a site outside the sources, or any medical or safety language. A second, independent model pass looks for claims the sources do not support. A draft that fails is revised or discarded.
• The article is published with its sources listed at the end and a note that it was machine-written. Every article closes with a short invitation to log the dive in Scubaspot. That is the one place the app appears in the text.

What we never write

The blog does not give medical or safety advice, and it does not say who a site is suitable for. You will not find certification recommendations, depth or current judgements, gas planning or anything about how to dive a site. Those questions belong with your instructor, your dive operator and your physician, not with a blog. A wreck's depth may appear as a fact about the wreck; whether you should dive it is not something we will tell you.

What can still go wrong

Sources can be out of date, and a model can misread them. Ferry schedules change, dive centers close, marine parks add fees. Treat every article as a starting point for your own planning, and check anything that matters with the operator you are booking with. If you spot an error, tell us and we will correct or remove the article.

Release notes and announcements

The posts about Scubaspot itself, and every entry on the releases page, are written by the team.