Opening an application's detail page (e.g. Hydra Console, 93941bf0-18ac-4d50-97fd-1daef540911d) shows no flows or graphs.
The graphs that orchestrate that application do exist — they live in the agentflow schema and are reachable only via Hermiq → Graphs. On this instance:
| graph |
trigger |
trigger schema |
enabled |
| Hydra Triage |
object.created |
finding |
false |
| Live check graph |
object.updated |
agent |
false |
| E2E smoke graph |
object.updated |
— |
false |
Hydra Triage is explicitly "Triage loop for the hydra pipeline", i.e. it orchestrates the Hydra Console application — but nothing on that application's own detail page surfaces it.
Expected: the app detail page carries a flows/graphs widget listing the graphs that trigger on this application's schemas, with their trigger, trigger schema and enabled state.
Current state: no such widget exists in the manifest. The only match anywhere in the repo is an unrelated "type": "start-workflow" business-rule action in lib/Settings/register.d/10-business-rules.json.
Why it matters: the flows-first direction makes graphs the control plane — an operator retunes the loop by editing a graph rather than shipping code. If the application page cannot show which graphs act on it, the control plane is invisible from the thing it controls, and the only discovery path is knowing to look in another app entirely.
Reported by the user while reviewing the hydra pipeline's flows-first port. Related: hydra#421, hermiq#83.
Opening an application's detail page (e.g. Hydra Console,
93941bf0-18ac-4d50-97fd-1daef540911d) shows no flows or graphs.The graphs that orchestrate that application do exist — they live in the
agentflowschema and are reachable only via Hermiq → Graphs. On this instance:object.createdfindingobject.updatedagentobject.updatedHydra Triageis explicitly "Triage loop for the hydra pipeline", i.e. it orchestrates the Hydra Console application — but nothing on that application's own detail page surfaces it.Expected: the app detail page carries a flows/graphs widget listing the graphs that trigger on this application's schemas, with their trigger, trigger schema and enabled state.
Current state: no such widget exists in the manifest. The only match anywhere in the repo is an unrelated
"type": "start-workflow"business-rule action inlib/Settings/register.d/10-business-rules.json.Why it matters: the flows-first direction makes graphs the control plane — an operator retunes the loop by editing a graph rather than shipping code. If the application page cannot show which graphs act on it, the control plane is invisible from the thing it controls, and the only discovery path is knowing to look in another app entirely.
Reported by the user while reviewing the hydra pipeline's flows-first port. Related: hydra#421, hermiq#83.