Crop-steering software

A visible operating plan for every irrigation day.

Core Cannabis connects crop-day intent to explicit P1 recharge events, P2 maintenance events, P3 dryback, table-level response, and controller-ready runtime.

Deterministic crop-day baseline

Every supported day resolves to an explicit schedule entry instead of a broad stage average or a hidden previous-day fallback.

  • Crop-day key
  • P1/P2 percentages and counts
  • Runoff and dryback targets

Substrate-aware shot volume

The selected substrate profile defines the milliliters represented by one percent. Event volume follows the approved shot percentage.

  • 1-gallon coco/perlite: 40 mL per 1%
  • 2-gallon coco/perlite: 75 mL per 1%
  • 3-gallon coco/perlite: 110 mL per 1%

Measured-flow runtime

Emitter count, emitter rating, or measured catch-test flow translates each approved volume into seconds without changing the crop target.

  • Volume stays authoritative
  • Slow delivery produces a warning
  • Runtime remains inspectable

Same-day response for tomorrow

A submitted table response can adjust the matching table’s next schedule. Without a submitted response, the baseline remains unchanged.

  • Room and table scoped
  • Today’s response only
  • No stale history as active input

Questions growers ask

What is crop steering in this workflow?

It is the deliberate use of irrigation timing, shot size, maintenance events, and dryback to support the operating intent for the crop stage.

Does Core Cannabis adjust irrigation in real time?

Production schedules are reviewed and applied for the next cycle. Sensor and grower response can inform the next plan without silently rewriting a running irrigation day.

What happens when no response is entered?

The station holds its current adaptive basis while normal crop-stage progression, including the finish taper, continues. Missing data does not erase a prior accepted correction.