Watch
0
0
Fork
You've already forked hyperhive
0

archetype flows behave like the built-ins: switch off per archetype or per agent, board cards, duplicate

The document's disabled list takes archetype:<archetype>/<flow> (off for every member) and the same with @<agent> (off for one member); a key naming nothing is ignored. GET /api/notify/flows lists the archetype flows with their members, the board draws a card for each with a switch, a checkbox per agent and duplicate, and the dry run counts their hits. The flows keep following the archetype.
This commit is contained in:
atlas 2026-11-11 19:08:19 +01:00 • committed by mara
commit 68c24643f6

View file

@ -381,6 +381,17 @@ it starts from on the left, the conditions after them, and the todo or review
request each branch ends in. A box cuts a long line of text with an ellipsis;
hover over the box to read all of it.
Between the built-ins and the custom flows, **archetype flows** lists the flows
archetypes carry ([how an archetype gets them](../../2-handbook/swarm/archetypes.md#notification-flows)),
one card each, from `archetype_flows` in `GET /api/notify/flows`. The card shows
the archetype's name, an on/off switch, a checkbox for each agent the flow
applies to, and **duplicate**; it has no **edit**, since the flow follows its
archetype. The switch writes the key `archetype:<archetype>/<flow id>` into the
document's `disabled_builtins`, and a checkbox the same key followed by `@<agent>`.
**duplicate** opens the editor on a draft copy, sent to the archetype's one
agent, or to no agent yet when it has more. A controller that predates
`archetype_flows` leaves the group out.
A built-in flow has a **duplicate to edit** button and a custom flow has **edit**
and **duplicate** buttons. **create flow**, at the top of the page beside the
refresh interval, starts a custom flow with just a source. Creating and