Skip to content
d3 Wiki
01.03

Communication standards

The right conversation in the right place, findable later.

Updated
Oct 3, 2026
On this page

Purpose

The right conversation in the right place, findable later.

The standard

  • Decisions and anything you'd want to find in six months → GitHub issue or PR, or an ADR. Chat is not a record.

  • Daily coordination → [TEAM: chat tool] channel #dev. Threads, not new messages, for replies.

  • Tool support requests from outside the team → #tool-support (or the intake form, 13.01). Never DM a developer for support.

  • Response expectation: acknowledge within one working day; blocking issues same day.

  • Status: async written update every [TEAM: Friday] — shipped, in progress, blocked.

  • Meetings have an agenda in the invite and notes in the shared doc; no agenda, no meeting.

Anti-patterns

Screenshots of code in chat (link the line on GitHub); decisions made in DMs.

Owner: [TEAM] · Last reviewed: 2026-09