From 50dbdbf83a7719f9db3f51b35e290df2d57f4837 Mon Sep 17 00:00:00 2001
From: limen <limen@local>
Date: Thu, 18 Jun 2026 16:27:51 -0400
Subject: [PATCH] Enable GitHub Discussions for community interaction

limen task GH-organvm-v-logos-github-21
---
 .github/ISSUE_TEMPLATE/config.yml |  3 +++
 CONTRIBUTING.md                   |  5 +++--
 README.md                         |  9 +++++++++
 profile/README.md                 | 20 ++++++++++++++++++++
 4 files changed, 35 insertions(+), 2 deletions(-)

diff --git a/.github/ISSUE_TEMPLATE/config.yml b/.github/ISSUE_TEMPLATE/config.yml
index e5932cb..a4b9d12 100644
--- a/.github/ISSUE_TEMPLATE/config.yml
+++ b/.github/ISSUE_TEMPLATE/config.yml
@@ -1,5 +1,8 @@
 blank_issues_enabled: true
 contact_links:
+  - name: 💬 Community Discussions
+    url: https://github.com/organvm-v-logos/.github/discussions
+    about: "Ask questions, share ideas, and talk with the community — for anything that isn't a concrete bug or feature request"
   - name: ORGAN System Documentation
     url: https://github.com/meta-organvm/organvm-corpvs-testamentvm
     about: "Full system documentation and governance corpus"
\ No newline at end of file
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index e506267..f22b612 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -33,7 +33,7 @@ This organization covers: Essays, process documentation, methodology writing.
 - Documentation improvements
 - Performance optimizations
 - Security patches (see [SECURITY.md](SECURITY.md))
-- Feature proposals via Issues (discuss before implementing)
+- Feature proposals — float the idea in [Discussions](https://github.com/organvm-v-logos/.github/discussions) first, then open an Issue once there's a concrete plan
 
 ### What Requires Discussion First
 
@@ -53,7 +53,8 @@ Essay contributions must include YAML frontmatter (title, author, date, tags, ca
 
 ## Getting Help
 
-- Open an Issue for questions
+- Start a thread in [GitHub Discussions](https://github.com/organvm-v-logos/.github/discussions) for questions, ideas, or open-ended conversation
+- Open an Issue only for concrete bugs or actionable feature requests
 - Check existing documentation in each repo's README
 
 ## Review Service Targets
diff --git a/README.md b/README.md
index d414be0..a500c8f 100644
--- a/README.md
+++ b/README.md
@@ -7,3 +7,12 @@ Organization profile and community health files
 - Organization-level workflows
 - [Branch protection baseline](BRANCH_PROTECTION_BASELINE.md)
 - [README standards](README_STANDARDS.md)
+
+## Community
+
+Have a question, idea, or just want to talk shop? Join the conversation in
+**[GitHub Discussions](https://github.com/organvm-v-logos/.github/discussions)**.
+
+Discussions is the home for open-ended community interaction — questions, ideas,
+show-and-tell, and feedback on the public-process essays. Use [Issues](https://github.com/organvm-v-logos/.github/issues)
+for concrete bugs and feature requests, and Discussions for everything else.
diff --git a/profile/README.md b/profile/README.md
index 3234e9e..610d9bc 100644
--- a/profile/README.md
+++ b/profile/README.md
@@ -12,6 +12,10 @@ _Essays, case studies, and methodology documentation_
 
 **6 repositories · 40 published essays · ~130K words · [Read the essays →](https://organvm-v-logos.github.io/public-process/)**
 
+[![Join the Discussion](https://img.shields.io/badge/💬_Community-Discussions-0d47a1?style=flat-square)](https://github.com/organvm-v-logos/.github/discussions)
+
+_Building in public is a two-way street — **[join the conversation in Discussions →](https://github.com/organvm-v-logos/.github/discussions)**_
+
 </div>
 
 ---
@@ -50,6 +54,22 @@ This is not performative openness. ORGAN-V publishes because the process of buil
 
 The `public-process` repository is the primary venue for ORGAN-V content. It houses 40 long-form essays (2,000-5,000 words each, ~130K words total), organized by category (meta-system, case study, retrospective, guide). Its Jekyll site with RSS is live at **[organvm-v-logos.github.io/public-process](https://organvm-v-logos.github.io/public-process/)**. The four supporting repos provide autonomous essay pipeline automation (`essay-pipeline`), privacy-first engagement analytics (`analytics-engine`), editorial governance (`editorial-standards`), and curated intellectual context (`reading-observatory`).
 
+## Join the Conversation
+
+ORGAN-V publishes in the open, and the conversation around that work belongs in the
+open too. **[GitHub Discussions](https://github.com/organvm-v-logos/.github/discussions)**
+is the community square for the organization:
+
+- **💡 Ideas** — propose essay topics, methodology experiments, or system directions
+- **🙋 Q&A** — ask about the architecture, the essays, or how to contribute
+- **📣 Show & tell** — share what you're building or how the work influenced yours
+- **💬 General** — open-ended conversation about building in public
+
+Discussions complements — rather than replaces — the existing channels: use
+[Issues](https://github.com/organvm-v-logos/.github/issues) for concrete bugs and
+feature requests, and Discussions for everything open-ended. This is the place to
+talk back; the project is no longer broadcast-only.
+
 ## How ORGAN-V Fits the System
 
 The organvm system distributes creative and institutional work across eight specialized organs — 81 repositories, ~320K words of documentation. ORGAN-V occupies a unique position: it is the organ that **observes and narrates** the work of all the others.