Diagnostics
FeedScan
The capture and result workflow is built and attached to the flock and feed programme it belongs to. What FeedScan should measure is a question still with the Devenish nutrition team.
Where this actually stands
The capture, storage and result framework is built on the shared diagnostic machinery. What FeedScan should measure has not been defined, and that is a larger gap than it sounds: it is not only the reference method that is outstanding, it is the list of outputs itself.
Nobody has yet said whether a FeedScan result is a single number, a spread, a set of proportions or a category — and those are not the same kind of answer. So the platform does not name one. Until the nutrition team settles it, no result of any shape can be stored and nothing is presented as a measurement.
The result contract
The shape of a result is declared, not assumed
The mechanism that will hold a FeedScan result is built and is deliberately empty. It refuses a figure until somebody publishes what shape the answer takes.
A declared shape
A single value, a spread, parts of a whole, a category, or several named values. Which one applies to FeedScan is exactly what is outstanding.
Published, then immutable
Editing a contract would retroactively change what every result stored against it claimed. A change is a new version.
Stamped on every result
A result carries the hash of the contract it satisfied, so it still explains itself after that contract is retired.
No figure without one
While no contract is published, no measurement and no structured payload can be stored — by anything, through any path.
No summarising
If the answer turns out to be a spread, nothing may reduce it to one number. A distribution is not its mean.
Re-scores add, never overwrite
When a method finally exists, earlier results are superseded rather than rewritten, so what a producer was told at the time survives.
An earlier version of this page listed the measurements a FeedScan result would carry. None of them had been agreed, so they have been removed rather than left standing as a specification nobody wrote.
Why it sits inside the platform
Whatever it turns out to measure, it is only useful next to what the birds did with it
Tied to the feed programme
Tied to the flock
Tied to the report
Help define what FeedScan should measure
If you already assess feed on farm, we would like to hear how — what you look at, what you measure, and what you would change on the strength of it. That is the question, and it is genuinely open.