Clarify veterinary as open decision with GBP Pets bucket size.

Note ~59-leaf Pets neighborhood separate from Health & Medical so
the healthcare vs own-call choice is explicit if vets are in scope.

docs/SELF_SERVE_AI_DISCOVERABILITY_CONCEPT.md

@@ -100,7 +100,7 @@ We are proposing **eight top-level clusters** plus one cross-cutting flag as a s
 
 **Hospitality and tourism** (hotel, surf rental, tour): destination and amenity truth, seasonal hours, and conflicts between the business’s own facts and big travel sites; recommendability is trip-intent fit (“family,” “near the break,” pet-friendly) and seasonal availability. This stays a **rubric parent even though GBP will not hand it to us as one bucket** — lodging leaves (hotel, motel, B&B) group fairly cleanly; tourism activity scatters across Sports, Education, Arts, and related leaves. Our audits still need one trip-intent rubric.
 
-**Healthcare / regulated** (only if we take them on — including dentist and medical spa): higher bar for accurate categories and careful claims. **Veterinary** is an open decision: GBP treats pets/vets as their own industry neighborhood; decide later whether vets ride with healthcare or get a separate call.
+**Healthcare / regulated** (only if we take them on — including dentist and medical spa): higher bar for accurate categories and careful claims. **Veterinary** is an open decision: in the GBP research dump, pets/vets sit in a separate Pets neighborhood (~59 leaves), not inside Health & Medical — decide whether vets ride with healthcare/regulated or get their own call if they are in scope.
 
 **Hybrid / multi-mode is not a ninth parent.** It is a **cross-cutting flag** that can sit on any cluster (dine-in plus delivery on food service; showroom plus install on retail or destination workshop). Presence and recommendability apply the relevant mode slices; the query tells you which mode matters. Google encodes many of these as specific leaves (delivery restaurant, mobile caterer), not as a top-level grouping.
 
@@ -132,7 +132,7 @@ Once Phase 0 is clear, work can run in parallel streams: promise and wedge langu
 
 ## Decisions still open
 
-Ty still needs to lock: which cluster pack we ship first; whether version one is web-only or also embeds in a chatbot; which providers feed the Presence score; how we measure Recommendability without overclaiming (simple heuristics versus live checks inside assistants); where the “email on file” for verification comes from; free versus paid; what never goes to a human versus when escalation is allowed; and whether **veterinary** rides with healthcare/regulated or gets its own decision (GBP keeps a Pets neighborhood separate from Health & Medical).
+Ty still needs to lock: which cluster pack we ship first; whether version one is web-only or also embeds in a chatbot; which providers feed the Presence score; how we measure Recommendability without overclaiming (simple heuristics versus live checks inside assistants); where the “email on file” for verification comes from; free versus paid; what never goes to a human versus when escalation is allowed; and whether **veterinary** rides with healthcare/regulated or gets its own call if in scope (GBP research dump: separate Pets bucket, ~59 leaves, not folded into Health & Medical).
 
 ---