Concurrent social topology spike with unique Discord identities #84
Description
Context
ADR-016 distinguishes runtime conformance spikes (sequential, shared identity) from social topology spikes (concurrent, unique identities). The rollcall spike has been correctly recast as sequential conformance, but no true concurrent topology spike exists.
What's needed
- A spike fixture with multiple concurrently active services, each with a unique Discord bot identity
- Validates bot-to-bot conversation, peer mentions, handle discovery, and generated
CLAW_HANDLE_*contact data - Requires provisioning additional Discord bot credentials
This is operationally expensive (multiple real Discord bots) and lower priority than the governance vertical.
References
- ADR:
docs/decisions/016-canonical-social-identity-and-conformance-spikes.md(Milestone 2) - Current rollcall spike:
cmd/claw/spike_rollcall_test.go