Mushroom Field Dossier

Mushroom Field Dossier is built to the one rule that matters: it will not name a species and it will not judge edibility. No such output exists anywhere in the program. Standing over a specimen, it asks what you were hoping for and then runs the destructive-sampling protocol in order, with the one-way steps marked: excavate the entire stem base before picking, photograph in situ, cut lengthwise once on the right axis, and start a spore print — because those are the actions that cannot be repeated. It then walks a character ledger of recognition pairs, not vocabulary: two schematic drawings side by side, tap the one that matches, or record the honest answer that you could not observe it. Unobserved characters are printed in the dossier as missing evidence, never guessed. Required photo slots (cap, underside, cut section, base in situ, substrate, scale) are filled by choosing JPEGs; EXIF date, GPS, elevation and flash are parsed in the tab and used only in the dossier you choose to export — photos are held in memory and never stored. The spore-print card takes your predicted colour before you look, refuses to let you edit it, and after enough prints shows the signed bias — the classic white-called-cream misread that turns one genus into another. The dossier is a single HTML file: characters observed, characters not observed, protocol steps done, EXIF habitat data nobody transcribes by hand, and the standing line to take it to your regional mycological society. It will not export with an empty required slot. Off-season, the same recognition skill runs as a 120-item paired-drawing drill with sub-second verdicts and a same-protocol cohort percentile. Aggregates only are stored (calibration counters, up to 8 in-progress specimens, the drill score); the knowledge pack is stamped on every screen and export. Four locales, keyboard operable, works offline.