Before a dashboard can answer a useful question, the information underneath it needs a shared structure.
The first job is a system of record
FarmOS is being developed to support Amanzi Life’s work on MoGro+. Its starting point is the information that should remain connected throughout product development: trial identity, field conditions, product batches, applications and measured outcomes.
Foundation
Records and relationships
Define trial, plot, batch and application identifiers, with consistent measurement definitions.
Review
Evidence people can inspect
Make sources, corrections, missing information and protocol changes visible.
Later exploration
Decision support
Explore analytical and recommendation workflows once the records support reliable review.
Design for the person doing the work
A field record should be practical to capture. A reviewer should be able to understand where a measurement came from. A product-development question should lead back to the batch and application records that matter. These user needs shape the platform before any particular dashboard does.
Keep people responsible for decisions
More advanced analysis is a staged direction. A proposed Plant Health Score, for example, would begin as a documented research index. It would need validation before becoming a recommendation signal. Automated application is not a current platform promise.
For the bigger picture, read why we are starting with farming.