Lifecycle
In plain words: Cultivator: growth cycles
How Cultivator reviews development and recurring seasons for annuals, perennials and fungi without forcing universal stages.
- 1Fungi don't inherit plant stages.
- 2Calendar dates alone cannot advance a stage.
- 3Missing reports prove neither health nor death.
Words on this page, decoded click one for its card
A perennial can enter another growing season without becoming a new subject. Cycle reviews retain both the recurring season and the longer history that preceded it.
Development and recurring cycles
cultivator.review_cycle@1 produces CultivatorCycle@1, linking a culture,
its reviewed profile revision, evidence, and cycle history. Development, recurring
season, placement, and completed work are independent dimensions.
Annual, perennial, and cultivated fungi profiles may describe different cycles. Fungi must not inherit botanically false plant stages. A perennial's recurring season does not reset its identity or erase earlier development. Profile-qualified states and transitions require evidence; calendar dates alone cannot advance a stage.
A newly reviewed profile does not silently rewrite earlier state claims. Record the revision and evidence supporting each change, including corrections and unresolved interpretations.
Review boundaries
An observed symptom is distinct from an interpretation or expert finding. Missing reports establish neither health nor death. Users may record suggestions and professional guidance with their source; the composition claims no diagnostic, pesticide approval, or food safety authority.
End each review with an evidence-supported change, refusal, infeasibility, or unknown outcome. The growing season and a perennial's longer history continue as durable records across those completed reviews, rather than keeping a RunJob Record open indefinitely. Tending completion and harvest receipts can inform the next review, but neither automatically proves a developmental transition or the end of the culture's life.
Return to Cultivator.