Community
The framework gets sharper in public. Discord is where that happens — proposals are debated, decisions are recorded, the next release is shaped.
Channels evolve as the community grows.
This is the topic landscape we plan to cluster conversations around — not a fixed list of pre-built channels. The actual room layout adjusts as practitioners arrive and bring their own questions.
Philosophy and language. Where the manifesto and vision get sharpened.
Pillar boundaries, principle clarifications, edge cases.
Spec template iteration, ICS rubric edge cases, ceremony design.
The Spec Lab, scorers, linters, dashboards. Builds in progress.
Adoption logs, retros, case-study drafts before they become docs.
Drift cases, kill-switch protocols, escalation patterns. Real incidents, anonymised.
Migration questions from teams coming off Scrum, Kanban, or SAFe.
New practitioner questions. No question is too small at Stage 1.
From conversation to spec change.
No closed-door rule-making. Every framework change has a public trail.
- 1A discussion starts
Someone names a gap, a friction, or a question — in a relevant channel. Anyone can start one.
- 2It crystallises into a proposal
A short write-up: what to change, what stays, what is at stake. Always written, never just argued.
- 3A maintainer drafts the change
A PR against the framework repo with the proposal as the spec. The PR description follows our own spec template.
- 4Review is open
Anyone in the community can comment. The maintainer responds in writing. Consensus is sought, but a named decision-maker calls it when needed.
- 5It lands or it does not
Either way, the rationale is recorded. Future readers can see what changed and why.
Four small things.
- ▸ Write to be re-read. Channels are searchable; threads outlive their authors.
- ▸ Disagree in writing. Disagreement is data — capture it so the next reader sees the trade-off.
- ▸ Name your stakes. "I think X" is fine; "I think X because I built one and it broke this way" is better.
- ▸ Be kind by being clear. Vagueness wastes everyone's time. Specificity is respect.
The room is unlocked.
No application. No waitlist. Bring questions, bring opinions, bring proof of what works and what doesn't.
The framework is real.
The community is forming now.
DoCoDeGo is in Alpha. The framework is documented, the practices are battle-tested at small scale, and the next release is being shaped in public.
If it produces anything, it should produce engineers and teams who think more clearly about what they are building and why.
Discord is where specs are debated, the framework gets sharper, and decisions land in writing. The conversation is the artefact.