mara/hyperhive
mara/hyperhive
Watch
0
0
Fork
You've already forked hyperhive
 0
Code Activity

destroying an agent clears its per-agent archetype-flow switch-offs

Browse source
This commit is contained in:
atlas 2026-11-11 21:22:24 +01:00 • committed by mara
commit d8703f40dc
1 changed files with 117 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

4
docs/2-handbook/swarm/archetypes.md
View file

@ -162,6 +162,10 @@ within about 10 seconds, and the card has no `edit` button.
just one, and to nobody until you name an agent when it has more. A custom
flow can also request a review, which an archetype's flow can't. Switch the
archetype's flow off to replace it with your copy.
- Destroying an agent removes its per-agent switch-offs from the list, so
a new agent of the same name starts with every archetype flow on. If that
cleanup fails, the controller logs the agent and leaves the keys; destroying
the agent again retries it.
- A key for a flow or agent that no longer exists stays in the list and does nothing, so
editing an archetype never breaks the stored flows. The key stays
after its flow goes: a later flow with the same archetype and id comes up