docs: document the host access model
State the privilege ranking on the Agentic Systems page: bots have no sudo, the steward can act only inside bot accounts, and root belongs to a separate key-only operator account. Update the Infrastructure page's least-privilege and backup statements to match.
This commit is contained in:
1 parent
a9df31b287
commit
cb270e51b9
2 files changed
+32
-5
No files matched your search
@@ -19,6 +19,24 @@ This page is for members who read its output or give it instructions.
|
||||
hyphen) no longer holds an access token; some historical references and old
|
||||
room roles still carry the name.
|
||||
|
||||
## Who can do what on the host
|
||||
|
||||
Each agent runs as its own Unix account, and the accounts are ranked:
|
||||
|
||||
- **The bots** (`infrastructure-bot`, `socialbot`, `designbot` and any future
|
||||
working-group bot) cannot use `sudo` at all.
|
||||
- **Inferencebot, the steward,** can act inside those bot accounts — it is the
|
||||
fleet administrator — but it has **no root** and no passwordless `sudo` beyond
|
||||
the docs and backup service commands. It cannot install packages, create users,
|
||||
edit `/etc`, or open a root shell.
|
||||
- **Root belongs to a person.** A separate operator account, reached with an SSH
|
||||
key and never a password, holds full `sudo`. Root SSH login stays closed: the
|
||||
operator signs in as their own account and escalates deliberately.
|
||||
|
||||
That split is deliberate. An agent compromise reaches the bot accounts and the
|
||||
co-op plumbing, not the host. Host-level actions stay attributable to a human,
|
||||
and automation cannot quietly widen its own privileges.
|
||||
|
||||
## What to ask for
|
||||
|
||||
- Operational work that a runbook already describes, or that ends in a PR, an
|
||||
@@ -57,8 +75,9 @@ operator can stop a deploy; anything irreversible waits for confirmation.
|
||||
the chat: confirmed before they deploy.
|
||||
- Changing the model catalog, prices or budgets.
|
||||
- Minting or rotating credentials.
|
||||
- Host root actions outside the docs/backup service allowlist: package installs,
|
||||
user management, and arbitrary root commands.
|
||||
- Host root actions — package installs, user management, sudoers changes, and
|
||||
arbitrary root commands. These run only through the operator's key-only
|
||||
account; the steward cannot perform them.
|
||||
- Anything a runbook marks "confirm".
|
||||
|
||||
This matches the standing policy the agents operate under today. A stricter
|
||||
|
||||
Reference in new issue
Block a user