Add comprehensive technical decisions to PRDs documenting architecture choices for community handles and moderator record storage. PRD_COMMUNITIES.md: - Add technical decision: Single handle field (2025-10-11) - Update lexicon summary to reflect DNS-valid handle approach - Add DNS infrastructure checklist items (wildcard setup, well-known endpoint) - Document that !name@instance format is client-side display only PRD_GOVERNANCE.md: - Add technical decision: Moderator records storage location (2025-10-11) - Document security analysis comparing user repo vs community repo - Explain attack vector for malicious self-hosted instances - Rationale: Community repo provides better security and federation Key decisions documented: 1. Single handle field matches Bluesky pattern (app.bsky.actor.profile) 2. Separation of concerns: protocol (DNS handle) vs presentation (!prefix) 3. Moderator records in community repo prevents forgery attacks 4. DNS wildcard required for *.communities.coves.social resolution Infrastructure requirements added: - [ ] DNS Wildcard Setup: Configure *.communities.coves.social - [ ] Well-Known Endpoint: Implement .well-known/atproto-did handler 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>