Context. Layer 7 § Open Questions: "Per-instance identity in fleets: should sub-agents be identifiable individually?"
When one operator runs 500 identical worker agents, do they share one DID, or does each get its own? This affects reputation, revocation blast-radius, and spend-limit accounting.
Your task. Weigh the two models:
- Shared DID: simple, but one compromised worker taints all; no per-worker reputation.
- Per-instance DID: isolation + granular revocation, but key-management overhead at scale.
- Is there a middle path (e.g. a fleet DID that delegates to per-instance keys via
did:web paths)?
Done = a comment or PR with your recommendation and the reasoning.
Context. Layer 7 § Open Questions: "Per-instance identity in fleets: should sub-agents be identifiable individually?"
When one operator runs 500 identical worker agents, do they share one DID, or does each get its own? This affects reputation, revocation blast-radius, and spend-limit accounting.
Your task. Weigh the two models:
did:webpaths)?Done = a comment or PR with your recommendation and the reasoning.