Skip to main content

Crate domain

Crate domain 

Source
Expand description

Typed domain contracts for NVA Pet Resorts labor-cost automation.

The crate is the code-derived source of truth for a 170-location pet-resort operating model: customers, pets, reservations, source-system provenance, safety policies, payment/deposit states, documents, messages, workflow events, and audit evidence. Types in this crate describe what an agent or adapter may know and what must remain draft/review-gated before any live staff, customer, payment, medical, or capacity action.

Crosswalk navigation for docs readers: start with the entity index and contract crosswalks before treating a type as operational authority. domain is where provider/staff evidence is normalized into semantic values; workflow use, persistence, runtime exposure, and tests are linked from docs/entity-atlas/contract-crosswalk/{surface-inventory,source-provider-flows,workflow-packets,storage-persistence,runtime-exposure}.md.

Modules§

agent
Agent prompt and packet contracts for review-gated operating workflows.
analytics
Analytics contracts for labor, revenue, occupancy, and exception reporting. Analytics read models for resort operations after source validation.
audit
Audit contracts that preserve evidence for source facts and automation decisions. Audit identifiers for traceable pet-resort automation events.
boarding
Boarding contracts for accommodation, deposits, handoffs, housekeeping, and upsells. Boarding service-line rules for capacity, stay policy, care handoffs, and upsells.
care
Care-profile contracts for feeding, medication, handling, and pet-safety notes. Care-plan and medical-instruction value objects for safe resort workflows.
customer
Customer identity/contact value contracts for portal and messaging workflows. Customer identity and contact values used by reservation and messaging workflows.
daily_brief
Manager daily-briefing contracts for occupancy, staffing, risk, and action summaries. Manager-facing daily brief values for cross-service resort operations.
data_quality
Data-quality contracts for repairing uncertain source records before automation uses them. Data-quality findings that guard the source-fact → domain → workflow chain.
daycare
Daycare contracts for eligibility, attendance, yard assignment, coverage, and throughput. Daycare service rules for front-desk throughput, safe play, and package review.
document
Document intake, verification, storage, and retention contracts. Document intake, safety review, storage, and retention values.
entities
Normalized core entity contracts for locations, customers, pets, reservations, and records. Core pet-resort entities and operational records.
grooming
Grooming contracts for appointments, services, estimates, rebooking, and history. Grooming service-line rules for pet-resort scheduling, no-show, rebooking, reminder, and review queues.
incident
Incident contracts for safety events, evidence, escalation, and follow-up. Incident categories and review states for pet-safety workflows.
lead
Lead intake and follow-up contracts for prospective customer conversion workflows. Cross-service lead conversion triage for resort sales follow-up.
location
Location contracts that scope local resort capability, policy, and timezone facts. Resort-location values used to scope policies, schedules, labor, and source data.
message
Message contracts for draft, approval, queueing, delivery, and suppression state. Customer and staff message delivery state.
money
Money contracts for typed resort charges and deposits.
operations
Operations contracts for service offerings, capacity, labor, and location execution. Portfolio and cross-service operating values for pet-resort automation.
payment
Payment contracts for deposits, references, collection, waiver, and refund state. Payment-domain values for deposits, references, and review-safe money movement state.
pet
Pet identity and care-label contracts used across reservations and safety workflows. Pet identity values shared by reservations, care notes, and safety checks.
policy
Policy contracts that decide what is safe to automate and what must be reviewed. Policy gates that decide what automation may do safely.
portal
Portal account contracts for provider/customer access boundaries. Customer-portal identifiers imported from external systems such as Gingr.
reputation
Reputation contracts for review monitoring, response drafting, and escalation workflows. Reputation-review triage for customer-trust, safety-theme, and response workflows.
reservation
Reservation contracts for age rules, add-ons, transitions, and service eligibility. Reservation support facts used by booking triage and checkout handoff workflows.
retail
Retail contracts for POS, inventory, recommendations, vendors, and reorder signals. Retail service-line models for POS sale eligibility, inventory position, reorder workflows, vendor partnerships, and care-safe product recommendations.
source
Source-system provenance contracts for Gingr/import facts and normalization assumptions. Source-system provenance and record references for app-owned operational facts.
staff
Staff contracts for scheduling, roles, training, and shift/labor context. Staff tasking decisions for resort labor assignment and closeout.
temperament
Temperament contracts for group-play safety and behavior review evidence. Temperament and behavior-observation contracts for daycare and care safety.
training
Training contracts for programs, progress, trainer availability, and upsell workflows. Training service-line rules for enrollment readiness, trainer capacity, curriculum progress, package sessions, and parent-facing follow-up.
vaccine
Vaccine contracts for compliance, proof, expiry, and review requirements. Vaccination-document review states for compliance-gated resort workflows.
workflow
Workflow contracts for tasks, events, reviews, and recommended actions. Workflow events and outcomes for reviewable resort operations.