swarm: subagent-status KV bucket, the run state of each subagent
One key per subagent (<agent>.<subagent>) holding running/finished, since, exit, model, effort and the publish time. The controller creates the bucket, and the agent credential may publish its own keys. Nothing reads or writes it yet; the daemon publisher and the controller list follow.
This commit is contained in:
parent
c9c2e75091
commit
c7d7f0df55
1 changed files with 214 additions and 0 deletions
|
|
@ -200,6 +200,11 @@ pub mod wanted;
|
|||
/// merge, are in `swarm_wire::agent_status`.
|
||||
pub mod agent_status;
|
||||
|
||||
/// Opening the bucket each agent's subagent daemon publishes the run state of
|
||||
/// its subagents into: one key per subagent. The name, keys and value are
|
||||
/// `swarm_wire::subagent_status`; opening the bucket needs `kv`.
|
||||
pub mod subagent_status;
|
||||
|
||||
/// Opening the bucket agent icons are published into: one key per agent, with
|
||||
/// no hive in it, unlike [`agent_status`]. The name, media type and subject,
|
||||
/// and why the placement stays out of the key, are in `swarm_wire::agent_icon`.
|
||||
|
|
|
|||
Loading…
Reference in a new issue