Tending

In plain words: Cultivator: watering and tending

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

How Cultivator plans watering, repotting and pruning with safe bounds, requests supplies, and records what work actually happened.

Why read it: Read when building tending plans, supply requests or work logs.
  1. 1Stale or unknown evidence cannot satisfy safety bounds.
  2. 2Partial work records both the result and the remainder.
  3. 3A lost acknowledgement means unknown; no blind retry.

Words on this page, decoded click one for its card

The original text Underlined words open their plain-English card.

A bed needs water, but the latest tank reading is stale. Tending must preserve the need and the resource uncertainty together until a reviewed plan can name feasible work.

Assessed work

cultivator.plan_tending@1 produces CultivatorTendingPlan@1 and CultivatorSupplyNeed@1. A coherent assessed plan links subjects, placement, source evidence, and reviewed profile revision to watering, resource, substrate, repotting, or pruning work.

Each action carries its own safe bounds, due window, expiry, stop conditions, and expected evidence. Unknown or stale evidence cannot silently satisfy those bounds. Planning may refuse an action or record infeasibility rather than manufacture care advice.

A supply need binds its originating owner and revision and records minimum necessary quantity, unit, product traits, constraints, purpose, validity/expiry, privacy class, and unknowns. Homestead stores may return an exact SupplySnapshot@1, while Provision returns ProvisionResult@1. These establish stock or availability, not biological suitability or completed use. A material substitution returns for Cultivator review before changing the plan or submitting an order; availability cannot weaken the reviewed culture requirements.

Execution and results

After work, use cultivator.record_work@1 to produce CultivatorWorkEvent@1 and CultivatorWorkResult@1. Record what actually happened: action, actor, effective and recorded times, quantity and unit uncertainty, evidence, plan reference, and outcome. If only part was done, retain both the actual result and unresolved remainder. Reconcile and deduplicate stock use by that event; neither a plan nor a provision receipt establishes consumption.

When Homestead supplies water, its actual resource limits remain decisive. Automatic actuation requires a separately admitted owner, current evidence, and applicable vetoes. A missing acknowledgment means unknown execution; do not retry an action merely because its reply was lost.

Any exact Legion request passes through the commissioned owner with a fenced task, zone, resources, expiry, and stop conditions. The body retains a fresh veto. Such a request grants no general robot authority.

Finite recovery

Settle a work attempt as completed, refused, infeasible, partial, unknown, or interrupted, as applicable. On restart, use event identity, owner evidence, and acknowledgments to establish what occurred before deciding further work. Cancellation closes only that admitted work and preserves any effect already performed. Disable future schedule Occurrences separately. Cross-owner live recovery follows the Suite boundary; settled receipt exchange alone does not require aan SuiteApp Bundle.

Return to Cultivator.