1. Say what your corpus looks like
Ten thousand support tickets and two hundred legal contracts need different answers. Size, format and update rate change everything.
2. Report retrieval quality separately
Recall@k before answer quality. Most "the model hallucinated" reports are retrieval failures wearing a costume.
3. Name your components
Embedding model, vector store, chunk size, re-ranker. A pipeline described in adjectives can't be compared to anything.
4. Access control is part of the design
If you post an architecture, say how it stops a retriever returning a document the asker shouldn't see.
5. Stay on topic
Posts should relate to rag. Off-topic posts get moved, not deleted — there's probably a better room for it.
6. Be respectful
No harassment or spam. Self-promotion is fine if it's genuinely useful and you disclose the connection.