ADR-0071: PM-facing surfaces should read in English

Date: 2026-06-29 Status: Phase 1 — Accepted; Phase 2 — Proposed

Context

PM-facing notification emails and UI surfaces (tour confirmations, team alerts, prospect notes) must be readable by property managers who may not speak the contact's language. When Clara conducts a leasing conversation in Spanish (or any non-English language), free-text params such as notes on save_prospect / schedule_tour and message on notify_leasing_team carry the contact-language text directly into PM inboxes and dashboards. Incident: Rodolfo Parra (2026-06-29) — a "Tour Confirmed" email arrived with Notes in Spanish, and a "Prospect can't find the office" alert body was also in Spanish.

Decision

Phase 1 (this PR — Accepted): Add a prompt-level instruction to each affected tool-parameter description field requiring Clara to write notes and message values in English for the PM team, even when the conversation is in another language. Applies to: save_prospect, update_prospect, schedule_tour, reschedule_tour (notes), and notify_leasing_team (message) in both the voice-agent config (leasing.config.json) and the text-agent tool schema (tools-leasing.ts).

This is a soft constraint: Clara follows the instruction reliably but it is not a hard translation guarantee.

Phase 2 (Proposed — separate PR): Implement server-side translation of non-English content before it reaches PM surfaces, with an original-language badge and a per-property toggle (opt-in to original language). Phase 2 supersedes Phase 1 once shipped.

Consequences

• PM-facing emails and notes will be in English in the common case immediately after this PR.
• No change to tenant-facing conversation language.
• No new infrastructure cost.
• Phase 2 is required to cover edge cases (model non-compliance, long notes with mixed language).