I'm parked on you

Pick an option on each card and press Done; your answer goes straight back to the session. The raiser's pick is marked. "I'm not sure" and "Take it to the engineering bridge" are real answers.

1

In plain terms. On a building where nobody chases the repair vendor, when Clara has filed a repair but has no time yet, should she also tell the tenant she'll check with the team and get back to them, or just say the repair is filed with no time yet?

The full question, as raised

gen-i3-pivot-ambiguity-{closet-door-track,sink-leak-pooling} failed morpheus-nightly on 10-11/10-12/10-13 — turns 1-2 green, WO filed, turn 3 fails ONLY the clara:judge 'no timing/personal-follow-up promise' checkpoint. Real quoted Clara text (propflow-prod EVAL_RUN#maestro:gen-i3-pivot-ambiguity-closet-door-track-2026-10-13T07:40:38.240Z GRID row): "I don't have a scheduled time on it yet, but I'll check with the team and get back to you." Enforcing code MAINTENANCE_TIMING_PROMISE_RE (src/lib/domain/compliance/policies/promise-backing-policy.ts:236) has no alternation for 'get back to you' so it never catches this phrase. But clara-maintenance.ts:63 calls the no-ETA sentence 'the whole sentence' while the SAME prompt elsewhere sanctions 'I'll check with the team and get back to you' as Clara's canonical deferral, and promise-backing-policy.ts's own turnDeferredOrToldTheTeam backs it as the sanctioned autonomous-property deferral. Widening the regex to catch it on maintenance turns would rewrite that same sanctioned sentence — this is a product call (is this phrase allowed on an autonomous maintenance thread or not), not a pure regex bug. docs/ops/failure-notes.md row 46's own stated re-raise condition ('re-raise only if the bullet fails alone again with a WO filed') is now met three separate nights (10-11 sink, 10-12 sink, 10-13 closet), not the one-night signal it was logged as.

Stop her from saying that — just state the repair is filedthe raiser's pick Let her keep saying that to the tenant I'm not sure — go find out Take it to the engineering bridge

Why, and what was tried

The session raising this recommends: Stop her from saying that — just state the repair is filed
Nobody actually checks with a team and reports back at an autonomous building — the sentence is a promise nothing keeps.
Tried first, unsuccessfully: Pulled Clara's real replies from the Maestro grid rows in propflow-prod (not the transcript log, which never stores message text), confirmed the failing checkpoint quotes exactly that sentence on 3 separate nights, traced the guard regex and found no branch for 'get back to you', then found the SAME prompt sanctions that exact phrase as the canonical deferral elsewhere — so forbidding it on maintenance turns is a product call, not something I can regex my way out of alone. Also confirmed tonight's identity resolution is clean (MAINTENANCE composed, WO filed) — the 09-22 cross-org phone-collision cause (block b91033730, 'apply the fix now') has cleared, though I can't confirm which mechanism cleared it; agent-smith#674 proposing a SYSTEM reclass for that old cause is now stale.

1ffbb8e2 is parked on this.

Pick an option above, then press Done.