Field reporting toolkit
Tools that keep field observations in structured records and build the trip report from those records.
A field trip produces notes, contacts, and a report, and those are easy to blur together. Field reporting keeps them apart. Observations go into structured records for objects, people, organizations, and the trip. The report is assembled from those records, and a second role reviews it.
Git versions the system: schemas, playbooks, scripts, and role profiles. A line-oriented log versions the facts. One append script is the only write path for a record. Other scripts create and activate a trip, validate the records, check the report, and seal an export for delivery. A dry-run trip is included so validation and sealing can be checked without a live trip.
The current design is two roles. Field Report runs the trip: notes, contacts, and the report, which is built from the records rather than from chat memory. Field Review reviews that report. Playbooks hold the instructions. The person running the toolkit is the only one who commits. The roles write files and do not.