II.
Term JSON
Structured · liveterm:unified-hook-result
Unified Hook Result json
Inspect the normalized record payload exactly as the atlas UI reads it.
{
"id": "term:unified-hook-result",
"_kind": "Term",
"_file": "terminology/terms/terms-articles-and-refs.yaml",
"_cluster": "terminology",
"attributes": {
"displayName": "Unified Hook Result",
"kind": "concept",
"description": "Hook handler return value in agent-mux's unified hook system —\n`{ decision: allow|deny|modify, message?, modifiedInput?, stdout?,\nexitCode? }`. `deny` maps to exit code 2, the convention shared by\nmost harnesses. Source: docs/agent-mux/reference/15-hooks.md.\n"
},
"outgoingEdges": [
{
"from": "term:unified-hook-result",
"to": "term:hook-registration",
"kind": "related_to",
"attributes": {}
}
],
"incomingEdges": []
}