Expand description
Grooming contracts for appointments, services, estimates, rebooking, and history. Grooming service-line contracts for pet-resort labor planning, rebooking, reminders, and safe customer-facing grooming automation.
This module models mini/full grooms, baths, coat/skin add-ons, groomer assignment, duration estimates, no-show consequences, service history, and reminder cadence as source-derived operational facts. AI or adapter code may draft estimates, reminders, and rebooking prompts through these types, but manager/groomer/care review gates preserve the boundary between recommendation and live scheduling or customer messaging.
Modules§
- appointment
- Appointment-owned public vocabulary for grooming service requests.
- breed_
coat - Breed/coat boundary for converting pet profile facts into labor-time estimates.
- calendar
- Groomer-calendar policy boundary for assigning grooming work without inventing availability.
- duration_
estimate - Duration-estimate decision vocabulary.
- history
- History boundary for grooming contracts.
- no_show
- No-show and late-cancel boundary for protecting groomer capacity and rebooking policy.
- rebooking
- Rebooking cadence boundary for identifying due, overdue, or history-insufficient grooming follow-up.
- reminder
- Reminder boundary for drafting appointment confirmations, prep instructions, and cadence winback messages.
Structs§
- Appointment
Minutes - Positive grooming quantity used where a zero-minute appointment or zero-length operational value would create impossible schedule math.
- Contract
- Location grooming contract tying calendar assignment, estimate policy, no-show rules, rebooking cadence, reminders, and history retention together.
- Contract
Builder - Use builder syntax to set the inputs and finish with
build(). - Duration
Estimate - Grooming duration decision with evidence, confidence, and the review gate needed before calendar use.
- Estimation
Policy - Policy object that chooses a grooming duration from pet history first, then contracted breed/coat defaults.
- Estimation
Request - Source-derived request used to estimate grooming duration before a schedule mutation is proposed.
- Estimation
Request Builder - Use builder syntax to set the inputs and finish with
build().
Enums§
- Appointment
Minutes Error - Validation failures returned by grooming domain constructors.
- Estimate
Basis - Evidence basis that explains why a grooming duration was chosen for scheduling review.
- Estimate
Confidence - Confidence level assigned to a grooming duration estimate.
- History
Requirement - Service-history retention requirement that protects rebooking quality and safe handling across visits.
- Review
Requirement - Review lane that determines whether a grooming estimate may be used for calendar execution.
- Service
- Grooming services and add-ons that drive groomer calendar load, checkout upsells, duration estimates, and follow-up reminders.