Files
Assistant/architecture/adrs/ADR-0015-human-response-continuation-semantics.md
m 8b9b841645
CI / test (push) Successful in 21s
CI / test (pull_request) Successful in 16s
DEV-000066 human response continuation semantics
2026-08-17 17:02:33 +03:00

3.0 KiB

ADR-0015 — Human Response and Continuation Semantics V1

Status: Accepted

Task: DEV-000066

Context

DEV-000065 made Domovoy present beyond an HTTP request: reminders can become due, produce Continuity-owned Attention, and deliver a governed notification. The next step is not a reminder command set; it is a general way to interpret a human response to an existing context.

Examples include: a reminder after notification, waiting work requiring a decision, a future email thread, or a future capability gap/acquisition context. V1 implements reminders as the first real target while preserving extensible typed target references for future owners.

Decision

  1. Continuity owns HumanResponse and ResponseTargetResolution V1 because they continue durable waits/attention and may mutate Continuity-owned future obligation state.
  2. Interaction remains the owner of the original HumanUtterance and OriginalHumanIntent; Continuity stores references to those records, not copies of their authority.
  3. V1 response operations are typed but extensible: ACKNOWLEDGE, COMPLETE, SNOOZE, CANCEL, DISMISS, CONTINUE, REJECT, plus UNKNOWN for fail-closed interpretation.
  4. V1 target references are typed: ATTENTION_ITEM, PROSPECTIVE_ITEM, WORK_TASK, CAPABILITY_GAP, INTERACTION_CONTEXT, and UNKNOWN. DEV-000066 implements only Continuity-owned reminder/attention mutations.
  5. Obvious deterministic responses may execute without cognition. Ambiguous responses must ask for clarification and record an append-only response record without mutating the target.
  6. A human response is not automatic verified world truth. For reminder completion, V1 records USER_REPORTED_COMPLETE; this satisfies the reminder according to policy but does not create a verified external-world fact.
  7. UI buttons, if present, must post the same semantic response text/API path as natural chat. They are projections, not a separate command system.

Boundaries

  • Continuity writes only Continuity-owned response, attention, and prospective state.
  • Interaction writes conversations/utterances/intents before Continuity response handling.
  • No external mutation or Commit/Executor operation is introduced in DEV-000066.
  • No model output directly mutates canonical state.
  • Future Codex/mail/capability-gap continuations are representable by typed references, but not implemented.

Non-goals

  • No Codex Bridge, Gmail, MCP, voice, mobile, browser automation, self-extension loop, or generalized orchestration.
  • No universal object ontology.
  • No reminder-specific parallel subsystem.

Consequences

  • “Готово”, “Отложи”, “Отмени” can continue the latest obvious reminder/attention context without internal IDs.
  • Snooze re-arms the same ProspectiveItem with a new due time, preserving audit history.
  • Cancel suppresses the future obligation so the due scanner will not deliver it.
  • Today/Attention can show active, snoozed, completed, and cancelled human-readable states.