network: R3 kinship mirror research — community identification

[4444J99]

Context

The kinship lens maps ORGANVM to communities with philosophical alignment. discover.py has 11 seed communities, but the full ORGANVM surface area (8 organs, 113 repos) connects to many more.

Tasks

• Map each organ to its natural kinship communities
• ORGAN-I: philosophy of technology, systems theory, epistemology networks
• ORGAN-II: creative coding, new media art, performance tech, sound art
• ORGAN-III: indie hacker, solo SaaS, micro-ISV communities
• ORGAN-IV: DevOps, platform engineering, infrastructure-as-code
• ORGAN-V: digital journalism, open publishing, POSSE advocacy
• ORGAN-VI: learning communities, book clubs, educational technology
• Identify Discord servers, forums, mailing lists, meetup groups
• Add to discover.py:KINSHIP_COMMUNITIES
• Human review and confirmation of each entry

Labels

mirror-protocol, research, horizon-2

[4444J99]

Handoff Research (S28, 2026-03-21)

Current State

This issue asks for R3 kinship mirror research — mapping each organ to its natural kinship communities (Discord servers, forums, mailing lists, meetup groups).

S28 substantially addressed this issue. Commit 1027b8f — feat(network): expand parallel mirrors to 127 + kinship to 61 entries (#65, #66) expanded the KINSHIP_COMMUNITIES list in network/discover.py from 11 seed entries to 61 curated communities, organized by organ.

The current KINSHIP_COMMUNITIES list at discover.py line 302 covers all organs:

• Cross-organ/system-wide (4): indieweb, small-tech-foundation, open-source-sustainability, cooperatives-tech
• ORGAN-I Theoria (8): tools-for-thought, digital-humanities, santa-fe-institute, cybernetics-society, long-now-foundation, nlab-community, internet-archive, philosophy-of-computer-science
• ORGAN-II Poiesis (11): sfpc, gray-area, eyebeam, creative-coding-community, lines-community, processing-foundation, toplap, ars-electronica, creative-applications-network, tidalcycles, supercollider-community
• ORGAN-III Ergon (7): indie-hackers, microconf, hackernews, product-hunt, wip-chat, calm-company-fund, saastr
• ORGAN-IV Taxis (7): cncf, platform-engineering, devops-community, cd-foundation, github-actions-community, internal-developer-platform, opentofu
• ORGAN-V Logos (7): write-as, ghost-foundation, substack-writers, webmention-community, are-na, creative-commons, journalism-tools
• ORGAN-VI Koinonia (7): recurse-center, coding-train, freeCodeCamp, open-education-network, reading-groups-community, p2pu, edx-open-source
• ORGAN-VII Kerygma (6): fediverse-community, mastodon, bluesky-community, micropub-community, bridgy, ifttt-maker-community
• META/Governance (4): todo-group, chaoss, innersource-commons, open-source-initiative

Each entry has: project name, platform type, relevance description, URL (mostly), tags, and organ affiliation.

suggest_kinship_mirrors() function (line 853) matches against these communities by tag overlap and organ context.

What Was Done in S28

Commit 1027b8f:

• Expanded from 11 to 61 kinship community entries
• Organized by organ with clear section headers
• Added organ tag arrays to each entry
• All 8 organs are covered with 4-11 communities each
• Also expanded PARALLEL_PROJECTS to 127 entries across domains

What Remains

The issue's checklist is largely complete but some items remain:

1. Human review and confirmation — The issue says "Human review and confirmation of each entry." The 61 entries are curated but not human-confirmed. Each community should be verified as active and aligned.
2. Discord servers — The issue specifically asks for Discord servers. Most entries are communities/forums/wikis. Only creative-coding-community has a Discord URL. More Discord-specific entries could be added (e.g., many of the creative coding and devops communities have Discord servers).
3. Mailing lists — No mailing list entries. Academic communities (ORGAN-I, V) often use mailing lists.
4. Meetup groups — No local meetup entries. Could add regional creative coding meetups, DevOps meetups, etc.
5. Platform field specificity — Most entries use "community" as platform. Could be more specific: "discord", "forum", "mailing-list", "meetup", "wiki", "slack".

Approach

1. Review the 61 entries for accuracy (human task — visit URLs, verify active)
2. Add Discord-specific entries where communities have Discord presence
3. Add mailing list entries for academic communities
4. Refine platform field from generic "community" to specific platform types
5. Mark entries as confirmed after human review

Key Files

• /Users/4jp/Workspace/meta-organvm/organvm-engine/src/organvm_engine/network/discover.py lines 302-799 — KINSHIP_COMMUNITIES list (61 entries)
• /Users/4jp/Workspace/meta-organvm/organvm-engine/src/organvm_engine/network/discover.py lines 853-899 — suggest_kinship_mirrors() function

Prerequisites / Blockers

• Human review of each community for accuracy and relevance
• Some communities may have shut down or changed focus since curation

Estimated Effort

S (1-2 hours) — The bulk of the research is done (61 entries). Remaining work is human verification, adding Discord/mailing-list specifics, and refining platform types. Could be done incrementally.

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 14 days if no further activity occurs.

[4444J99]

Backlog engagement 2026-07-19 — disposition: evolving.

Verified current main: src/organvm_engine/network/discover.py has the existing network discovery surface, but the requested R3 kinship/community expansion is still in red PRs #131/#127. This remains research work, not a closeable stale item: consolidate the community taxonomy, add tests for organ-to-community mapping, and get the test matrix green.