System

The Cultivation Loop

ALGX uses a closed-loop feedback system to refine cultivation decisions across seasons. AI is used as an operational lens, not an autopilot. Every critical decision point remains under human control.

The system captures field data, compares it against prior runs, generates confidence-weighted recommendations, and records outcomes. Each cycle makes the next one sharper without removing the cultivator from the process.

0

Process Stages

0+

Data Points per Run

0+

Seasons Logged

0%

Human Controlled

Data Architecture

What Gets Measured

Six data categories feed the model. Each is captured at the bed level, timestamped, and cross-referenced against prior seasons. This granularity lets the system detect patterns that aggregate tracking would miss entirely.

Soil & Substrate

  • pH levels
  • EC readings
  • Microbial counts
  • Amendment logs
  • Organic matter %

Water & Irrigation

  • Volume per event
  • Timing schedule
  • Runoff EC
  • Source water quality
  • Saturation depth

Environment

  • Temperature curves
  • Relative humidity
  • VPD calculations
  • Light intensity
  • CO2 concentration

Plant Health

  • Node spacing
  • Canopy color
  • Stretch rate
  • Root zone temp
  • Deficiency flags

Lab Results

  • Cannabinoid %
  • Terpene profiles
  • Moisture content
  • Microbial testing
  • Heavy metals

Operations

  • Feed schedules
  • Application rates
  • Harvest weights
  • Cure duration
  • Trim methodology

Process

Four-Stage Loop

Each grow cycle passes through four stages. The output of one cycle becomes the input for the next. Over time, the model gets sharper, but the cultivator always holds the final call.

01

Capture

Every measurable aspect of each grow cycle is logged into a unified season ledger. This is not selective tracking. It is comprehensive field documentation designed to surface patterns that would otherwise be invisible across seasons.

Soil Chemistry

pH, EC, microbial activity, amendment history per bed

Irrigation

Volume, timing, runoff EC, saturation levels

Environment

Humidity bands, temp curves, VPD, light hours

Canopy

Node spacing, color shifts, stretch rate, deficiency flags

Inputs

Feed schedules, amendment types, application rates

Grower Notes

Visual observations, anomalies, manual overrides

02

Compare

Raw data becomes useful when it's compared against similar conditions from prior runs. The system surfaces stable correlations and flags environmental drift that could affect outcome quality before the cultivator sees it in the canopy.

Season Matching

Aligns runs by grow conditions, not calendar

Drift Detection

Flags environmental shifts before visible symptoms

Yield Correlation

Maps input changes to harvest weight outcomes

Terpene Mapping

Tracks expression against feed and cure variables

Anomaly Isolation

Separates one-off events from systemic trends

Bed-Level Tracking

Granular comparison across individual grow beds

03

Recommend

The model proposes timing and process adjustments with confidence ranges, not rigid automation. High-confidence recommendations are presented differently from speculative ones. The cultivator always sees the reasoning, not just the output.

Feed Windows

Optimized amendment timing with confidence bands

Harvest Calls

Trichome maturity prediction against target profiles

Irrigation Tuning

Volume adjustments based on substrate and weather

Cure Parameters

Temp, humidity, duration targets for terpene retention

Risk Alerts

Early warnings for mold, deficiency, or pest pressure

Override Tracking

Logs when cultivators deviate and the outcomes

04

Execute

The cultivation team applies changes manually, then records outcomes for the next training cycle. There is no automated actuation. Every intervention passes through human hands and human judgment before it reaches the plants.

Manual Application

All changes are made by hand, not machine

Outcome Logging

Results documented for next-cycle model training

Deviation Records

Differences from recommendation logged with reasoning

Cycle Closure

End-of-run review feeds back into the full dataset

Team Calibration

Grower feedback shapes model weighting over time

Version Control

Every model revision is archived, never overwritten

Model Accuracy

Confidence by Category

The model's confidence varies by data category. Inputs with longer tracking histories and tighter feedback loops produce stronger recommendations. Categories where environmental variables dominate carry wider confidence bands.

Irrigation Timing91%
Feed Optimization84%
Harvest Window78%
Cure Parameters72%
Pest & Mold Risk65%

Season Progress

Learning Over Time

Each completed season adds depth to the model. Early seasons established baselines. Current seasons are where the system starts earning its keep, surfacing correlations that would take a human much longer to identify at this scale.

Season 1Foundation

Baseline Established

Initial data capture, no recommendations generated. Focus on building the measurement framework and validating sensor accuracy.

Season 2Calibration

First Comparisons

Cross-season patterns surfaced. Irrigation timing recommendations began. Harvest window predictions introduced with wide confidence bands.

Season 3Active

Active Recommendations

Feed optimization, cure parameters, and risk alerts operational. Override tracking enabled to measure cultivator alignment.

Philosophy

Operating Principles

These are non-negotiable rules that govern how the system operates. They exist to prevent the model from overstepping its role and to keep the cultivation process grounded in human expertise.

01

Human-First Control

The model advises. Humans decide. No recommendation is executed automatically. Every action requires cultivator approval and manual implementation. The system is designed to augment expertise, not replace it.

02

Transparency Over Opacity

Every recommendation shows its reasoning: what data produced it, how confident the model is, and what would change the output. Cultivators see the logic, not a black box answer.

03

Consistency Over Optimization

The goal is not maximum yield or peak potency. The goal is repeatable quality: the same clean expression, run after run, with minimal variance between harvests.

04

Data Stays on the Ranch

No cultivation data leaves the operation. No cloud syncing, no third-party analytics, no external model training. The dataset belongs to ALGX and stays physically on-site.

Guardrails

·Outlier signals trigger review, not automatic action.

·Every change is recorded with context for full traceability.

·Consistency is prioritized over aggressive optimization.

·No cultivation data leaves the ranch operation.

·Low-confidence outputs require explicit cultivator opt-in.

·Model versions are archived, never silently overwritten.

Boundaries

What We Don't Do

Defining what the system avoids is as important as defining what it does. These anti-patterns are explicitly blocked in the operational framework.

×

Auto-adjusting feed systems without human review

×

Chasing peak THC numbers at the expense of profile balance

×

Training on external datasets from different growing environments

×

Overriding cultivator decisions with higher-confidence model outputs

×

Optimizing for speed when the plant needs time

×

Treating sensor readings as ground truth without manual verification

Outcome

Cleaner, Repeatable Quality

The target is not synthetic uniformity. The target is dependable craft: the same clean expression, run after run, with minimal variance between harvests while preserving the natural character of each strain.

Cure Stability

More consistent moisture and terpene retention across batches

Batch Repeatability

Tighter variance in cannabinoid and terpene expression

Reduced Guesswork

Data-backed timing replaces calendar-based scheduling

Faster Diagnosis

Issues caught in data before they're visible in the canopy

The system improves with each completed cycle. Performance metrics reflect current model state and will shift as additional seasons are logged and validated.