# TODO: bounded first response and later completed diagnosis

Status: deferred design only. This change does not implement two-stage output,
start a 25-minute production deadline, or change the current
[dual-message contract](../DUAL_MESSAGE_CONTRACT.md).

The requested future direction is a useful first response within 25 minutes,
followed by the truly completed diagnosis and any necessary correction. Slow
Provider execution or extended diagnosis should not force a choice between
silence and presenting an unfinished result as final.

Design questions to resolve in a separate task:

- Which supported facts and explicit uncertainties make the initial response
  useful, and how is unfinished diagnosis distinguished from a final outcome?
- How are the later answer version, fingerprint, evaluation, and human feedback
  bound without silently replacing the meaning of the earlier version?
- Does the later result update the stable internal Jira note or create a
  linked update, and when should users be notified of a material correction?
- Who owns the still-running work, recovery after interruption, and treatment
  of new customer comments or changed incident scope before finalization?

The two proposed **time phases** are not the two existing **audiences**.
`customerReplyMarkdown` and `internalHandoffMarkdown` remain one canonical
answer pair. Any future phased design must preserve their audience meanings,
internal-only automation authority, Scenario Router diagnosis ownership, and
Final Response wording ownership. No new active schema, API, publication
behavior, or acceptance gate is introduced by this TODO.