Keeper feeding
Food removed from storage is not proof that an animal consumed it. keeper.plan_feeding@1
produces a proposed KeeperFeedingPlan@1 and any KeeperSupplyNeed@1, preserving that distinction.
Propose from reviewed requirements
Tie a plan to its subjects, current life-state evidence, source-reviewed care profile, revision, and review window. Keep quantities, units, uncertainties, and exclusions explicit. These contracts prescribe no generic food or clinical diet. Missing applicable evidence can block the plan; a proposed substitution requires Keeper review before changing it.
Check stock and availability through exact Homestead SupplySnapshot@1 and ProvisionResult@1
references. When supplies are needed, bind the request to its originating owner and revision and
include only necessary product traits, quantity and units, exclusions, purpose, validity/expiry,
privacy class, and unknowns. Raw husbandry histories and veterinary journals stay out of that
request. Keeper must still judge suitability; an available product is not thereby suitable.
Reconcile distinct evidence
Record offered or delivered quantities separately from observed consumption, leftovers, and disposal. Each has its own source, time, units, and uncertainty; unknown consumption stays unknown. Confirmed feeding work is recorded through care.
Use exact supply-use event identifiers to reconcile stock changes. Repeated delivery must resolve to the same event and must not remove stock twice or create a second feeding. The stock change still does not establish consumption. If an acknowledgment is lost, reconcile before repeating physical work; correcting the ledger alone cannot establish whether feeding occurred.
Finish with a proposed plan
Return a plan and bounded supply needs, or a partial, refused, blocked, or infeasible result. Execution needs human confirmation or a separately admitted owner. Close the invocation when its result is recorded; the plan's review window does not keep it open.