DasPoschi/hermes-webui
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

fix(runtime): clarify goal adapter seam semantics

Browse Source
This commit is contained in:
Michael Lam
2026-05-18 12:10:17 -07:00
parent b23fb6ccaa
commit 6a68bab114
5 changed files with 119 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

10
docs/rfcs/hermes-run-adapter-contract.md
View File

@@ -357,7 +357,15 @@ class RuntimeAdapter:
`queue_message` is named for the legacy `/api/session/queue` payload: it
accepts follow-up chat text rather than arbitrary runtime input. The method name
does not require the HTTP route to change; it documents the adapter-level control
semantics that a later Slice 3c implementation should preserve.
semantics that a later Slice 3c implementation should preserve. The method enters
the protocol before route wiring so queue/continue can land as a separate, small
control-routing follow-up instead of being coupled to goal routing.
For `update_goal`, the `action` argument is the bounded adapter capability label.
During the legacy-journal slice, the legacy goal parser still receives the full
`text` payload and remains authoritative for details such as the body of
`set <goal text>`. Future slices must not route goal semantics from `action`
alone; doing so would drop the goal body and change `/api/goal` behavior.
Required data classes / payload fields: