[EPIC] Community Program — public docs repo as enhancement hub + artifacts library

[temalo]

Community Program — turn corpusiq-docs into a public artifacts + enhancement-requests hub

Background

Ben proposed (Sat 2026-05-30) using this public docs repo as the surface where users submit enhancement requests and access community artifacts beyond raw documentation. Goal: give customers and prospects a structured, transparent way to request connectors and features, see what's prioritized, share workflows, and contribute recipes — without standing up new infrastructure.

The three jobs this repo will do

1. Inbound enhancement requests — structured issue templates capture connector and feature asks. Public so other users can upvote / +1 instead of refiling.
2. Public roadmap visibility — a Project v2 board ("Now / Next / Later / Shipped") backed by labeled issues. Replaces ad-hoc roadmap markdown that goes stale.
3. Public artifacts hub — recipes/ directory for community-contributed how-tos, examples/ for runnable code, Wiki for the contribution model itself.

Why this repo (not a new one)

• Already public under the CorpusIQ org
• Already has Issues enabled, Wiki enabled
• Brand is right (no engineering exposure)
• Discussions not yet enabled (separate task — see #TBD)

Comms boundary (important)

Per the standing comms split:

• Marin owns customer-facing voice. Any broadcast announcement of the program ("CorpusIQ docs is now your home for connector requests!") is Marin's to write and send.
• Hermes/dev@ handles the plumbing and reactive comms (templates, labels, automation, internal Telegram alerts, drafts that Marin approves).
• Exception worth confirming with Marin: technical Q&A replies on Discussions (developer-to-developer, not broadcast) could go out under dev@/Hermes voice — same justification as the support@ pattern. Get Marin's explicit yes before shipping that part.

Scope checklist

See child issues for each work item. Sequenced for easy parallelization where possible.

• Issue templates (enhancement, bug, question→discussion) — [community] Issue templates: enhancement, bug, question→discussion #8
• Label taxonomy + per-connector labels — [community] Label taxonomy + per-connector labels #9
• CONTRIBUTING.md + Wiki seed pages — [community] CONTRIBUTING.md + Wiki seed pages #10 (drafts → Marin review)
• Enable Discussions, seed categories — [community] Enable Discussions, seed initial categories #11 (manual GitHub UI by an org admin)
• Create Project v2 board, wire issues to it — [community] Create Project v2 board, wire enhancement issues to it #12
• recipes/ directory + template + first 2-3 recipes — [community] recipes/ directory + template + first 3 recipes #13
• examples/ directory + first runnable sample — [community] examples/ directory + first runnable code sample #14
• GitHub webhook → Hermes Telegram alert on issue-opened — [community] GitHub webhook → Hermes Telegram alert on issue-opened #15
• Auto-ack cron for new enhancement issues (with Marin approval workflow) — [community] Auto-ack cron for new enhancement issues #16
• Marketing site CTA ("Request a connector") pointing at this flow — [community] Marketing site CTA: 'Request a connector' pointing at this flow #17
• Marin coordination: outreach plan, announcement copy, target audiences — [community] Marin coordination: outreach plan + announcement copy #18

Out of scope (for now)

• Bounties or paid recipe contributions
• A separate domain (community.corpusiq.io etc.)
• Migrating to a different platform (Discord / Discourse) — GitHub-native is the constraint
• Multi-org Discussions federation

Decision log

• 2026-05-30 — Ben proposed the idea, Ted accepted, agent filed initial planning issues.
• 2026-05-30 — Marketing site CTA, Discussions enablement, and outreach copy all gated on Marin's input. Filed as dependencies under [community] CONTRIBUTING.md + Wiki seed pages #10, [community] Enable Discussions, seed initial categories #11, [community] Auto-ack cron for new enhancement issues #16, [community] Marketing site CTA: 'Request a connector' pointing at this flow #17, [community] Marin coordination: outreach plan + announcement copy #18.