What “one page per pet” fixes
At intake, lead with legal name, nicknames, and species in the header; park microchip, insurer flags, major surgery dates in body—not buried in chat display names.
Multiple same-species pets use semantic suffixes—year band or pattern—not “pet #2,” which ages poorly.
Life-stage labels (juvenile/adult/senior) with manual override answer “how old” fast while supporting phase-based thinking.
High-value remarks
Prioritize three lines: active med summary, hard contraindications, handling triggers. Save personality essays to notes; keep remarks scannable.
Cross-clinic care: remarks cite latest lab date + clinic shorthand; full PDFs stay under lab entries.
Accounts, devices, and boundaries
Cloud-backed profiles need a household rule on who edits identity fields vs who only appends logs—arguments spike at renames or adoptions.
Avoid public dumps of full profiles; redact identifiers when asking for help online.
Fixing mistakes cheaply
On mix-ups, freeze writes, annotate bad fields, copy salient summary to the correct profile, move last 30 days—stop stacking errors first.
Legal renames: keep a six-month former-name line so legacy labs still reconcile.
Limits
Profiles organize care facts; they don’t appraise pedigree, price pets, or diagnose—urgent cases belong in-clinic.
Field-level UI notes live on `/official/p/features`; species nuance stays in columns and guides.