Crop Recipes
Standardize the grow. Then let it run itself.
A recipe is a crop's whole life — stage durations, photoperiod, irrigation, fertigation, target bands — and the platform executes it.
On most farms, how a crop is grown lives in one person's head. It works, right up until that person is on holiday, or leaves, or the second room opens and the same seed comes out different.
A crop recipe writes it down in a form the platform can execute. Stage durations — germination, nursery, grow. Photoperiod per stage. Irrigation and fertigation. And the environmental target band for each stage: what this crop should be seeing right now, not on average across its life.
Those bands are not documentation. They are the setpoints the control layer drives to, and the bands Live Monitoring judges a rack against. Which means improving a crop is an edit to one document, not a memo to fourteen people.
Questions
The things people actually ask.
What is actually in a recipe?
The stages and how long each one runs, the photoperiod for each stage, the irrigation and fertigation regime, and the environmental target band the crop should be held in at that stage — temperature, humidity, CO₂, EC and pH.
Does the recipe drive the equipment directly?
The recipe holds the crop targets; Controls and Automation owns the equipment. The setpoint engine reads the stage a cycle is in and drives to that stage's band — but only as far up the autonomy ladder as you have allowed it to go.
Can different rooms run different recipes at the same time?
Yes. Ideal bands are derived per cycle from the recipe stage, so a nursery tray and a mature grow rack are judged and driven against what each of them should actually be doing.
See Crop Recipes on a real farm.
We'll walk an order all the way through to its margin — on live farm data, not a slide.