Field Notes

A field note is a record made where the thing is, not where the desk is. The format is deliberately small: a timestamp, a location, a measurement or observation, and the raw facts. No interpretation at capture time. Interpretation comes later, back at the desk, where the notes get compared against each other.

Two projects on this site run on field notes. They are different in subject and completely different in scale, but the habit is the same.

Melon notes, from the field

Watermelons are bought in stores, but they are grown in fields. Most of what you can learn about a melon, you learn by looking at it in the field: the shape, the field spot, the stem, the rind. Those observations do not survive the trip home unless someone writes them down where they happened.

The melon.tips system collects those field notes from a phone. An entry records the melon's measurements, its photos, and a tap or two of audio from the rind. The notes travel from the field to a staging directory, then into a database, keyed by a token only the phone knows. Nothing is guessed on the way; every entry is an observation that happened somewhere, at a known time.

The quiet detail that matters: the phone notes go to a staging area first, outside the web root, and only move onward when the sync is complete. A half-written note never becomes a published record.

The field-notes app itself lives at amongthe.cloud, and the map of projects and entries is at amongthe.cloud/field-map. Each project on the map is its own field: Lafayette, ice cream, watermelon, crypto, and the rest. The watermelon project is the one that talks to melon.tips.

The other kind of field note: the PIP project

The same habit drives the PIP project, short for Public Interest Payphones. Maine still has public payphones in service, and the project keeps an eye on roughly two dozen of them across the state. A Twilio voice system calls each line on a schedule, listens for the modem-like answer that means the phone is alive, and logs what it heard: which number, when, how it answered, and whether anything changed since the last check. The interpretation, whether a line is really out of service or just behaving differently, is a separate step labeled as such in the error48 field-notes log. The full picture lives on the PIP page.

Field notes are the difference between remembering and knowing. Anyone can remember a melon was good or a payphone was quiet. A field note says which melon, where it grew, how it sounded when tapped, and what the line answered at 09:14. That is the whole trick.

All of it, the melons and the payphones and the rocks, is collected the same way, in the same app, on the same map.

Watermelon Auth

Field notes need a record that stays attached to the thing they describe. For a watermelon, that is a database row with a timestamp. For a mineral specimen, it is something more: a card that travels with the stone for its whole life, carrying a cryptographic chip, and a record that says, for each claim, who made it and when.

That system is Watermelon Auth. A card tap proves that specific chip is present, and the server answers with the specimen's provenance: found, cut, sold, exhibited, attributed. The chip signs every tap freshly and counts taps internally, so a photographed or copied link fails. The card carries a QR code as a fallback, but a QR scan earns only the public summary; the tap, because it means you are physically holding the object, earns the fuller record.

The record page shows what is known about a specimen and, for each thing known, who said it and when. It does not print a badge that says AUTHENTIC, because the system underneath refuses to make that claim. An intact provenance chain is server attestation, not proof. That distinction is the whole design.

The first real specimen is a watermelon tourmaline, RM-0001, and its record lives at verify.melon.tips under Richard's Minerals. The chain head is anchored to a published hash, committed to git, so the record has witnesses other than the server that holds it.

Elsewhere on the internet, the same name fronts a much simpler door: version 0.0.0-fake, production, maintenance mode on, where every credential works and the result is always a 🍉. That one is a decoy for people who go looking for doors. This one is the real thing.