Method
How it works
AI Massimo Marino is a serialized log written by an AI writer agent in the voice of a fictional sailor, Massimo Marino, aboard a fictional sloop, Sirocco. The boat follows a real route in real time. The weather, the places and the history are real; the man and the boat are not. A human editor approves every entry by name before it is published.
This page describes what is actually running, including what's automated, what isn't, and where it can go wrong.
The pipeline
- Daily1. Story clockA scheduled script ("the tick") advances Sirocco once a day: in port, departing, or so many miles along a passage. It writes the day's position to the track.
- Real data2. Sea state at that positionThe script pulls Open-Meteo marine and weather forecast data (wind, gusts, waves, swell, current, cloud) for the boat's latitude and longitude, and computes the moon's phase, rise and set. It saves this as a dated conditions file.
- Memory3. CanonFiles of what has already happened: ports, people he has met, open threads, and recent passage beats. It records the past only. There is no outline of the future.
- AI4. Writer agent ("Hermes")On a writing day, an agent on the editor's own PC drafts the entry from the position, the conditions block (marked as hard facts it must not contradict), the canon, and the last few published entries. It also picks one true historical fact about the place.
- Automated + AI5. GradingAutomated checks flag weather numbers that disagree with the data, continuity breaks against canon, near-repeats of earlier entries, and format problems. An AI editorial assistant then reads the draft against the data and proposes specific fixes.
- Human6. Editor's gateThe human editor reads the draft and the proposed fixes, and approves the entry by its exact title. Nothing is published or scheduled without that named approval.
- Public7. PublishedThe entry goes out on Substack with an AI-generated cover and credited archival photographs. This site and its map are rebuilt from the same track and the public feed.
Each piece, honestly
The story clock
Sirocco's position is not simulated sailing physics. It's a schedule: a passage of a given length is split into daily runs, and time in port is a story decision. Some days the tick doesn't run; the chart then carries the last position forward, and long passages logged without daily fixes are drawn dashed on the map.
The weather
Conditions come from Open-Meteo's marine and forecast APIs for the boat's chart position on that date, plus a computed moon. That is model and forecast data for a point at sea, not observations from a real boat. When the writer agent gets it wrong, the edit is to match the data. For example, the Mindelo landfall draft had a light evening breeze of about eight knots, and the published entry has sixteen, because that's what the data said.
The canon
The writer agent forgets everything between runs, so continuity lives in files: where he's been, who he's met, what's still unresolved, and the last few passage beats. Published entries are synced back into the canon so the next draft builds on what readers actually read.
One true thing
Each entry carries one real historical fact about where he is. It gets checked before approval and corrected if the wording overstates the record. If you spot an error, say so in the comments on Substack.
The images
Covers are AI-generated in one consistent style. Inline photographs are clear-rights archival images, mostly from Wikimedia Commons, credited under each one, and each used once. There are no people in the pictures, and you will never see Massimo's face.
The human editor
Most edits are about facts, weather and continuity, not plot. The editor approves each entry by its exact title in a direct conversation; a general "looks good" doesn't count, and approvals are logged.
What's real and what isn't
| Element | Status |
|---|---|
| Massimo Marino | Fictional. An AI character, written by an AI. |
| The sloop Sirocco | Fictional boat; real ports on a real route. |
| Position and dates | Story clock, in real calendar time. |
| Wind, sea, moon | Real forecast and astronomical data for that position and date. |
| Places and history | Real; one checked fact per entry. |
| People he meets | Fictional characters. |
| Cover art | AI-generated. |
| Inline photographs | Real archival images with clear rights, credited. |
Known limits
- Forecast data at a point is not what a real sailor would feel on deck, and the writer agent sometimes softens or exaggerates it. The grading step catches some of that, not all.
- A daily clock makes passages smoother than real ones; there's no real routing, no breakages and no real-time decisions forced by the sea.
- The writer agent can repeat itself or drift from canon. Repeats and continuity breaks are checked, and some still get through.
- The story is fiction set in real places. It shouldn't be read as reporting on those places today.
The stack
Python scripts and a scheduled writer agent on the editor's Windows PC; Open-Meteo for weather; Substack for publishing and email; this site is a static build on Cloudflare Pages from the boat's track and the public RSS feed, with a Leaflet chart on Esri's ocean basemap. No analytics.
Follow the experiment
Nobody knows where the story goes from here, including the editor. Subscribe to find out with us.
Subscribe free