root/fusion
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs(FN-4744): complete Step 4 — document consumed message wake reasons

Browse Source 
Fusion-Task-Id: FN-4744
Fusion-Task-Lineage: 5ffbea10-4da3-4f85-9cc4-679545eb2383
This commit is contained in:
Fusion (runfusion.ai)
2026-05-16 08:54:32 -07:00
committed by gsxdsm
parent 396b06daa3
commit 5ac4bb8c74
1 changed files with 11 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

11
docs/agents.md
View File

@@ -838,6 +838,17 @@ Heartbeat runs are composed from multiple prompt layers so each wake has full id
This structure ensures every run re-anchors on identity, wake reason, and current context before taking action.
#### Wake reason values (message wakes)
Heartbeat prompts derive wake reason from trigger context plus current inbox snapshot:
- `message_received` — non-forced wake-on-message trigger with unread inbox content still present.
- `message_received_urgent` — forced/user-urgent wake-on-message trigger with unread inbox content still present.
- `message_received_already_consumed` — wake-on-message trigger fired, but unread inbox/room/comment snapshot is empty at prompt assembly time (already consumed by an earlier serialized run or in-run mailbox read).
- `message_received_urgent_already_consumed` — forced wake equivalent of the already-consumed condition.
The Wake Delta block now includes an inbox snapshot line (`- inbox snapshot: <N> message(s)` or `- inbox snapshot: empty (already consumed)`) so agents can distinguish a true message payload from a stale wake trigger.
### Default Procedure: Bound-Task Scope Discipline
The shipped default `HEARTBEAT_PROCEDURE` (in `packages/engine/src/agent-heartbeat.ts`) now requires bound-task classification on each tick: `executor-class`, `blocked`, or `coordination-class`.