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

an archetype flow can be customized for one agent

Browse source
This commit is contained in:
atlas 2026-11-11 21:40:51 +01:00 • committed by mara
commit 5443c1c9ba
1 changed files with 153 additions and 34 deletions
Download patch file Download diff file Expand all files Collapse all files

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

@ -162,10 +162,19 @@ 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.
- **customize** next to an agent opens the new-flow editor on a copy of the flow
for that agent alone: its recipient is the agent, and its name ends with the
agent's name. Saving it adds the agent's switch-off to the list in the same
write, so the agent gets its copy and not both, while the archetype's flow
keeps updating for everyone else. Deleting the copy later leaves the agent's
switch off; switch it on again to give the agent the archetype's flow.
- 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 customized copy is a custom flow addressed to the agent's name. It survives
the destroy like any custom flow, so delete it by hand if you reuse the name;
otherwise the new agent gets the copy and the archetype's flow.
- 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