Cultivator

In plain words: App: Cultivator (plants and fungi)

Designed 2 min read 4 glossary terms 15 connected pages
The short version written for the Snayu team

Cultivator records the life of plants and cultivated fungi: identity, growing space, cycles, tending and harvests, for ornament, food, seed or propagation.

Why read it: Read before working on plant, garden or fungi features.
  1. 1Six workflows: cultures, space, cycle, tending, work records, harvest.
  2. 2Works with manual records; automation needs the controls' owner.
  3. 3No pesticide, diagnosis or food-safety authority.

Words on this page, decoded click one for its card

In this section 5 pages

Culture records Cultivator: plant records How Cultivator identifies a plant, batch or fungi culture, tracks lineage through cuttings and splits, pins a growing profile and records observations. open → Growing space Cultivator: pots and beds How Cultivator records containers, substrate and placement, and sends reviewed environment needs to Homestead. open → Lifecycle Cultivator: growth cycles How Cultivator reviews development and recurring seasons for annuals, perennials and fungi without forcing universal stages. open → Tending Cultivator: watering and tending How Cultivator plans watering, repotting and pruning with safe bounds, requests supplies, and records what work actually happened. open → Harvest Cultivator: harvest records How Cultivator records each harvest as a receipt and hands it to Homestead stores, keeping collection and store acceptance separate. open →
The original text Underlined words open their plain-English card.

A plant changes pots; a bed produces several partial harvests. Cultivator keeps the growing subject, its conditions, and the work behind each result connected across those changes. The Native Reference CompositionApp identity is cultivator.cultivation, revision 1. It covers plants and cultivated fungi for ornament, food, seed, or propagation; purpose is independent of taxonomy and place.

Contract and map

The record and PatternWorkflow catalogue follows persistence law and workflow law.

Work and PatternWorkflow Durable records
Identify the culture and record observations
cultivator.record_culture@1		 CultivatorCulture@1, CultivatorObservation@1, CultivatorGrowingProfile@1
Assess its growing space and placement
cultivator.assess_space@1		 CultivatorGrowingSpace@1, CultivatorPlacement@1, CultivatorEnvironmentNeed@1
Review its changing cycle
cultivator.review_cycle@1		 CultivatorCycle@1
Plan tending and request supplies
cultivator.plan_tending@1		 CultivatorTendingPlan@1, CultivatorSupplyNeed@1
Record work and its result
cultivator.record_work@1		 CultivatorWorkEvent@1, CultivatorWorkResult@1
Confirm a collected harvest
cultivator.record_harvest@1		 CultivatorHarvestReceipt@1

These six PatternsWorkflows are independently invocable. Enter through a culture's identity, its growing space or lifecycle, the tending work due, or a collected harvest.

Boundaries and admission

Keeper owns animals and colonies; Cultivator owns plants and cultivated fungi. Homestead retains infrastructure, stores, and utilities. Cultivator owns the cultivation capability extracted into its new identity; retired homestead.tend_land@1 is neither an alias nor reinterpreted history.

Admission fixes the responsible grower and permissions, exact culture/placement/profile revisions, requested observe/advise/record work, source evidence, hazards, resource limits, and permitted disclosure. Missing identity may permit an uncertain observation while blocking a specific action.

Manual evidence and human work remain valid without Homestead. Automation requires separate admission by the owner of the actual controls. Deterministic safety checks cannot establish biological appropriateness. Diagnostic authority, pesticide approval, agricultural treatment permits, and food-safety certification remain outside this contract.

Use a Suite only for live start, await, retry, cancel, or recovery across multiple owners. Settled references and receipts alone need no SuiteApp Bundle.

Privacy and recovery

Records remain local, Composition-owned PostgreSQL records under persistence law; these logical contracts define record meaning and links, not physical tables or migrations. Sharing selects exact records and purposes; there is no ambient database sharing. Media references carry retention purpose because images can expose people and locations.

Each InvocationJob Request ends with the applicable result: a proposed plan, recorded completion, refusal, infeasibility, partial, unknown, or interrupted outcome. During recovery, reconcile the exact events and acknowledgments before taking new action.

Export keeps identifiers, corrections, evidence references, and custody metadata while care continues. Deletion or an explicitly admitted custody migration requires more: close affected schedules and resolve or hand off outstanding care and effect custody under the retention and owner contracts. Closing a record does not remove a plant or dismantle its environment.

First proof

The acceptance fixture must preserve a synthetic ornamental plant through repotting and movement; split a seed batch into bed cohorts; refuse watering on unknown sensor or reserve evidence; reconcile repeated partial harvest, duplicate import, and a correction; exercise a perennial or fungi profile without universal stages; and recover lost action acknowledgment after restart. Export must leave care active; deletion must close affected schedules and settle or hand off custody.

Return to Compositions.