Community operating lane

From repo users to operator contributors.

This is the active operating motion for Meridian community growth: where to start, where to report runtime issues, and how to join weekly operator review loops.

Weekly community cadence

Tuesday

01Publish runtime changelog and acceptance lane results.

02Tag good-first governance tasks in issues.

Thursday

01Hold operator office hour with live proof dashboard.

02Review adapter health, fallback incidents, and remediation outcomes.

Community channels

GitHub Discussions

Architecture questions, migration feedback, and operator runbooks.

Open discussions →

GitHub Issues

Runtime bugs, acceptance failures, and security-hardening proposals.

Open issues →

Discord launch track

Use the runbook to open and moderate Discord without breaking governance boundaries.

Open runbook →

Discord/community motion is active as an operating lane, not as vanity surface. The initial public channels stay GitHub-first until moderation, incident routing, and operator handoff are all in place.