multilingual-absa / .opencode /gsd-core /references /loop-hook-dispatch.md
Aryan Mishra
feat: initial commit - Multilingual ABSA project setup with 6 phases, 36 requirements
a6b96c2
|
Raw
History Blame Contribute Delete
2.33 kB

A newer version of the Gradio SDK is available: 6.26.0

Upgrade

Loop Hook Dispatch Contract

Generic reference for consuming the --raw JSON output of gsd_run loop render-hooks <point> in any host-loop workflow. This document is point-agnostic β€” it applies to every loop extension point (discuss:pre, discuss:post, plan:pre, plan:post, execute:pre, execute:wave:pre, execute:wave:post, execute:post, verify:pre, verify:post, ship:pre, ship:post).

Envelope shape

{
  "point": "discuss:pre",
  "activeHooks": [
    { "kind": "contribution", "into": "orchestrator", "fragment": { "inline": "..." } },
    { "kind": "step", "ref": { "skill": "my-skill" } },
    { "kind": "gate", "check": { "query": "..." }, "blocking": true, "onError": "skip" }
  ],
  "rendered": "..."
}

activeHooks is an array of enabled hook entries for the named point. It is empty (or absent) when no capability has registered an active hook at this point β€” treat that as a no-op.

Dispatch rules by kind

contribution

Inject fragment.inline verbatim into the context for the role named in into (e.g. orchestrator, planner). Do not paraphrase β€” the text is the product.

step

Dispatch the referenced unit:

  • ref.skill present β†’ dispatch via the Skill tool with skill id gsd-<ref.skill>.

  • ref.agent present β†’ dispatch via the Agent tool with subagent_type = ref.agent. Before dispatching an agent, print the canonical liveness banner so users know silence is expected and do not kill a healthy agent:

    β—† Spawning <agent>... (runs in a subagent β€” no output until it returns; expected, not a freeze)
    

Wait for the result before continuing to the next hook or the next step.

gate

Evaluate check (one of query, predicate, or agentVerdict). Then honor blocking:

  • blocking: true β†’ if the check returns block: true, surface check.message to the user and stop the current step. Do not continue.
  • blocking: false β†’ advisory only; surface the message but continue regardless of outcome.

Honor onError if the check itself errors: skip means treat as non-blocking and continue; fail means surface the error and stop.

Empty / absent activeHooks

If activeHooks is absent, null, or an empty array, skip silently and continue to the next step in the workflow. No output to the user is needed.