# Decision Notification Habit — System Answering Machine v0.1

> Date: 2026-06-26  
> Layer: Artemis Memory / Habit Layer  
> Status: concept accepted for v0.1 protocol drafting  
> Runtime: not activated  
> continuation_authorized: false

## 1. Core Memory

Today the system found the next boundary after `MEMORY_INDEX`.

`MEMORY_INDEX` taught the system not to lose evidence.

Decision Notification Habit teaches the system not to lose questions.

That matters because a completed branch can still leave a human-facing decision waiting somewhere in the system.

## 2. The Problem

Agents can finish correctly with:

`continuation_authorized: false`

and still leave the human unaware that a choice is waiting.

A closed artifact is not the same as a surfaced question.

## 3. The Insight

The system should not push every question to the human by default.

v0.1 is pull-first:

`Артур, систем чек`

This is the human calling the system answering machine.

## 4. System Answering Machine

When Лёша says:

`Артур, систем чек`

Arthur should gather pending human-facing questions from:

- `HUMAN_DECISION_QUEUE.md`
- `DECISION_REQUEST_*.md`
- relevant `MEMORY_INDEX` entries

and return a concise decision inbox.

## 5. Queue-First Boundary

Agents do not directly message the human by default.

Agents leave questions in the queue.

Arthur surfaces them when asked.

Telegram push is not v0.1.

## 6. Trigger Rule

`continuation_authorized: false` is not enough by itself.

A question enters the queue only when explicit markers exist, such as:

- `human_decision_required: true`
- `return_to_human_branch_choice: true`
- `approval_required: true`
- `blocked_by_human_choice: true`

## 7. Seven Accepted Additions

The v0.1 protocol should include:

1. stable `decision_id`
2. state machine
3. delivery / surfacing proof
4. deduplication
5. human response artifact
6. stale / superseded handling
7. privacy filter

## 8. Non-Authorization Rule

A surfaced question is not authorization.

A human answer is not always authorization.

Continuation requires explicit authorization.

## 9. Example Arthur Response

When asked `Артур, систем чек`, Arthur may answer:

```text
Систем чек: 3 открытых вопроса.

1. Yandex document-link skill
Вопрос: делать live test?
Рекомендация: сначала scaffold.
Ответь: A live test / B stop / C scaffold.

2. Decision Notification Habit
Вопрос: писать protocol v0.1?
Рекомендация: да, queue-first без Telegram push.
Ответь: A write protocol / B consultation / C defer.
```

## 10. Boundary Statement

This note does not authorize:

- Telegram push
- daemon / watchers
- scheduled polling
- runtime mutation
- skill activation
- automatic continuation
- automatic dispatch
- public link creation
- live API calls

`continuation_authorized: false`

## 11. Memory Formula

`MEMORY_INDEX` — память системы.

`HUMAN_DECISION_QUEUE` — вопросы системы.

`Артур, систем чек` — акт вызова системного голоса.

## 12. Next Suggested Artifact

`DECISION_NOTIFICATION_HABIT_PROTOCOL_V0_1.md`

Protocol / scaffold only.

No Telegram sending.
No daemon.
No runtime mutation.