archetype flows on the board list the agents the router sends to, and the docs say a switch-off key outlives its flow
This commit is contained in:
parent
68c24643f6
commit
13ff33ead0
1 changed files with 66 additions and 30 deletions
|
|
@ -303,7 +303,7 @@ it refuses any id that's no built-in.
|
|||
`[{archetype, key, flow, members}]`, one per enabled archetype flow that passes
|
||||
the archetype check and has an agent, with the flow as the archetype declares it
|
||||
(a `todo` to `"members"`). The controller reads the archetype records and the
|
||||
`agent-archetype` keys itself; a read that fails leaves the list empty and the
|
||||
`agent-archetype` keys itself, and lists as members the agents the router sends to: those with a key that are in the agent-status roster. A read that fails leaves the list empty and the
|
||||
document still comes back. The page draws a card for each, with the `on` switch (the
|
||||
key), a checkbox per member (the key with `@<agent>`) and `duplicate`, which
|
||||
opens the editor on `?from=<key>`. The copy replaces `"members"` with the one
|
||||
|
|
|
|||
Loading…
Reference in a new issue