From 288d844e25bcd550f6d95c00ca9a4c7ac8dc8479 Mon Sep 17 00:00:00 2001 From: "Builder.io" Date: Mon, 10 Nov 2025 19:17:09 +0000 Subject: [PATCH] Create Space 2 Communication Protocol page cgen-5490d69c952648ada3490ce9f8a93674 --- .../internal-docs/Space2Communication.tsx | 186 ++++++++++++++++++ 1 file changed, 186 insertions(+) create mode 100644 client/pages/internal-docs/Space2Communication.tsx diff --git a/client/pages/internal-docs/Space2Communication.tsx b/client/pages/internal-docs/Space2Communication.tsx new file mode 100644 index 00000000..f1655829 --- /dev/null +++ b/client/pages/internal-docs/Space2Communication.tsx @@ -0,0 +1,186 @@ +import InternalDocsLayout from "./InternalDocsLayout"; + +export default function Space2Communication() { + return ( + +
+
+

+ Communication is how we coordinate, build trust, and move fast. This + protocol defines which tools to use when, and how to communicate + effectively across all entities. +

+
+ +
+

Tool Matrix

+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+ Tool + + Use For + + Response Time + + Who +
Discord + Real-time chat, urgent issues, team coordination + + 5 minutes + All team members
Email + Formal communication, decisions, legal records + + 24 hours + All team members
+ Meetings + + Decisions, feedback, deep work, sensitive topics + + N/A + + Required participants +
+
+
+ +
+

Discord Etiquette

+
+
+

Channels

+
    +
  • • #general - News, announcements
  • +
  • • #random - Off-topic chat
  • +
  • • #help - Technical support
  • +
  • • Team channels: #labs, #gameforge, #corp, #foundation
  • +
  • • Direct messages for private matters
  • +
+
+ +
+

⏰ Availability

+
    +
  • + • Set your status: 🟢 Available, 🟡 Away, 🔴 Do Not Disturb +
  • +
  • • Urgent? Use @mention or DM
  • +
  • • Non-urgent? Use threads to keep chat clean
  • +
  • • Don't expect immediate responses outside work hours
  • +
+
+ +
+

🚫 No-Nos

+
    +
  • • Don't spam or flood channels
  • +
  • • Don't share sensitive data in Discord
  • +
  • • Don't @ everyone unless critical
  • +
  • • Don't use Discord for major decisions
  • +
+
+
+
+ +
+

Email Protocol

+
+
+

✓ Use Email For:

+
    +
  • • Policy updates and announcements
  • +
  • • Important decisions with records
  • +
  • • Formal communication with clients
  • +
  • • Contracts, agreements, legal matters
  • +
  • • Performance reviews, feedback
  • +
+
+ +
+

Email Best Practices:

+
    +
  • + • Clear subject line (what is this email about?) +
  • +
  • • Keep it brief—use bullets when possible
  • +
  • • Call out action items in bold or separate section
  • +
  • • Reply within 24 hours
  • +
  • • BCC sensitive distribution lists
  • +
+
+
+
+ +
+

Meeting Culture

+
+
+

+ ✓ Schedule a Meeting When: +

+
    +
  • + • You need to make a decision with stakeholders +
  • +
  • • The topic is sensitive or requires nuance
  • +
  • • You need face-to-face (video) interaction
  • +
  • • Async communication has broken down
  • +
+
+ +
+

+ ✗ Don't Schedule a Meeting When: +

+
    +
  • • You can send an email instead
  • +
  • • It's just for updates (use async updates)
  • +
  • • Only 1-2 people need to attend
  • +
  • • It could be a quick Slack message
  • +
+
+
+
+ +
+

+ Golden Rule: Async-first. Assume people are in + different time zones. Default to email and Discord. Reserve meetings + for high-value interactions. +

+
+
+
+ ); +}