docs: the agent roster page keeps the operator view and moves the topology detail out
The page says who is on the roster, who may reach whose state and that the manager is a normal agent. How topology.json is read and rebuilt, the wire protocol and the prompt blocks move to 4-implementation/agent-state/roster.md, unchanged, since the code they describe still exists.
This commit is contained in:
parent
02f21940a4
commit
e746ed1888
1 changed files with 156 additions and 121 deletions
|
|
@ -98,7 +98,9 @@ One agent: its roster entry, state, config and page. Start at
|
|||
tables and directory layout:
|
||||
[`4-implementation/agent-state/persistence.md`](4-implementation/agent-state/persistence.md).
|
||||
- **Who can do what to whom — the agent roster and privilege?** →
|
||||
[`2-handbook/agents/agent-roster.md`](2-handbook/agents/agent-roster.md).
|
||||
[`2-handbook/agents/agent-roster.md`](2-handbook/agents/agent-roster.md); how
|
||||
`topology.json` is rebuilt and what is special about the manager:
|
||||
[`4-implementation/agent-state/roster.md`](4-implementation/agent-state/roster.md).
|
||||
- **What does an agent's own page show?** →
|
||||
[`2-handbook/agents/web-page.md`](2-handbook/agents/web-page.md); the full
|
||||
reference is [`agent-page`](4-implementation/web-ui/agent-page.md).
|
||||
|
|
|
|||
Loading…
Reference in a new issue