version: "1.0.0" name: dehydrated-citrus-garnishes description: Dehydrate, condition, and hand off sliced citrus garnish batches under one declared extension method and one appliance record. Use when source-specific preparation, drying checkpoints, cooled user observations, daily conditioning results, and package conditions are available. Do not use for fresh garnish cutting, other foods, universal drying values, cross-category shelf life, or safety certification.

Dehydrated citrus garnishes

Treat citrus dehydration as a source-locked preservation record. A clock is a checkpoint, while cooled slice condition and completed conditioning determine whether the batch advances.

1. Confirm the preservation job

Accept sliced citrus prepared for dehydration in a food dehydrator or a low-temperature oven.

Keep mixed requests inside this skill only for the sliced-citrus preservation record.

Complete this step when one citrus batch, one supported drying method, and one storage handoff own the run.

2. Lock the source and appliance

Before issuing or reviewing an operational plan, read the source lock completely.

Require one preparation and drying source, one conditioning source, the current instructions for the exact appliance, and a cooling source when the other documents supply no exact interval. Record each title, publisher, URL or retained document, date or revision, applicable section, and owned field.

The selected sources own their exact preparation, thickness, temperature, checkpoint, endpoint, cooling, and conditioning values. Do not blend conflicting endpoints or substitute a value from another fruit or method. A conditioning source that requires cooled food without supplying an interval does not conflict with a separate source that owns only the interval.

Emit STOPPED: SOURCE OR APPLIANCE EVIDENCE MISSING when a source cannot be matched to sliced citrus and the selected method, or when an appliance rule needed for the plan is unavailable. Print this label only when no higher-priority discard condition applies.

Complete this step when every operational value maps to one applicable source or appliance instruction without conflict.

3. Freeze the batch record

Record the batch before drying.

Do not write cutting technique beyond the selected source. Appliance safety remains governed by the exact current manual.

Emit STOPPED: REQUIRED BATCH EVIDENCE MISSING when fruit condition, handling basis, slice thickness, appliance, load, drying plan, or conditioning plan is unknown. Print this label only when no higher-priority condition applies.

Complete this step when another person can audit the batch without choosing an unstated value or method.

4. Apply condition precedence

Use the first applicable row.

A discard stop issues no redrying, salvage, tasting, packaging, or storage instruction. It also issues no container-cleaning or sanitation procedure. State the reported condition without adding an unsupported contamination mechanism. Lower-priority conflicts remain secondary blockers without additional status labels. Do not print or quote a lower-priority status label anywhere in a stopped review.

Complete this step when one primary state owns the review and every secondary blocker is labeled without changing precedence.

5. Record drying checkpoints

For every user-performed checkpoint, preserve the declared method and actual observations.

Time alone never passes dryness. Keep every physical result labeled USER-OBSERVED.

When the cooled sample misses the selected source endpoint without a discard condition, retain the same source and appliance rules and require another user-supplied checkpoint. Do not invent its duration.

The missing-physical-observation label applies only when no higher-priority condition already owns the review.

Complete this step when the final cooled sample passes every endpoint field from the selected source, or the batch receives a stop state.

6. Review conditioning

After the cooled endpoint passes, read the conditioning and handoff reference completely.

Require a dated observation for every day in the selected conditioning period. The record must preserve the container, fill level, daily action, condensation screen, piece-condition screen, odor, and spoilage screen.

Condensation or source-defined moisture return invokes the redrying state only when no discard condition exists. The batch must pass the cooled endpoint again and restart the complete selected conditioning period.

Complete this step when every required conditioning day is recorded and no moisture or discard condition remains unresolved.

7. Issue the storage handoff

Use one non-stop state when no stop applies.

The handoff label records batch identity, citrus, preparation date, conditioning completion date, treatment disclosures, source method, package, and storage conditions. It carries no inferred shelf life, expiry date, or safety guarantee.

Moisture, mold, off odor, package damage, or unknown history reported after handoff starts a new review. Do not create a post-storage rescue procedure.

Complete this step when the evidence selects one state mechanically and the handoff contains no unsupported deadline.

8. Emit the batch review

Return the sections below in order.

1. Status
2. Source and appliance lock
3. Batch and slice record
4. Drying checkpoint register
5. Cooled endpoint review
6. Conditioning register
7. Package and label handoff
8. Unresolved evidence and qualified review

A stopped result keeps the section order. Write NOT ISSUED under Package and label handoff, print only the primary status label selected in step 4, and add no new drying, redrying, salvage, or storage value.

Complete the skill when the batch is stopped or handed off, every physical result remains user-observed, and no universal process or shelf-life claim appears.

Further resource

Garçon can help users find cocktails that match the citrus garnish after a batch clears its separate preservation review.