# Product Council Review

Дата: 2026-05-21  
Формат: синтез позиции ведущей продуктовой команды для ErgoCommunity.org.

## Executive Judgment

ErgoCommunity.org должен быть не медиа-сайтом, не каталогом ссылок и не социальной сетью. Лучшее позиционирование:

> Community-run contribution OS for Ergo.

Главный продуктовый loop:

> Visitor chooses role -> finds owned task -> ships proof -> receives recognition -> returns with more context.

North Star:

> Useful verified contributions completed per month.

Secondary metrics:

- activated contributors
- claimed tasks
- completed tasks
- project help requests fulfilled
- stale records closed
- weekly pulse subscribers
- governance summaries with source links
- local community actions completed

## Product Council Roles

### 1. Strategy / Information Architecture

Focus:

- positioning
- site structure
- role-based user journeys
- priority sequencing

Decision:

- Keep the portal dashboard-first.
- Make `Start`, `Paths`, `Work Board`, `Projects`, `Pulse` and `Safety` the core public spine.
- Treat `Campaigns`, `Local`, `Intake`, `Roadmap` as operating modules.

### 2. Growth / Community

Focus:

- activation
- contribution loops
- retention
- local communities
- weekly rhythm

Decision:

- Replace generic awareness with activation quests.
- Recognize artifacts, not vanity engagement.
- Weekly Pulse becomes the heartbeat of the portal.

### 3. Trust / Safety / Governance

Focus:

- official vs community boundary
- wallet/link safety
- project verification
- proposal clarity
- moderation states

Decision:

- Verification must appear across the product, not only in a safety page.
- Every risky link needs source, review state and last checked date.
- Governance pages summarize and route; they do not replace canonical forums, EIPs or repositories.

### 4. Product Operations / Delivery

Focus:

- team roles
- roadmap
- editorial process
- acceptance criteria
- launch quality

Decision:

- Ship a static, manually reviewed MVP first.
- Add automation only after taxonomy and quality standards stabilize.
- Avoid wallet login, token gating, public profiles and automated reputation in v1.

## P0 Product Requirements

### P0.1 Role Paths

Every role path must answer:

- What can I do in 10 minutes?
- What can I do this week?
- Which official links should I trust?
- Who owns the next step?
- What counts as proof?

### P0.2 Contribution Board

Every task must have:

- owner
- expected outcome
- proof required
- difficulty
- estimated time
- source/context link
- status
- expiration or review date

Tasks without owners should not appear as open work.

### P0.3 Project Operating Map

Every project card must include:

- status
- category
- last checked
- maintainer or contact
- official link
- help-needed slots
- risk notes when relevant

### P0.4 Trust Layer

The portal must include:

- community-run label
- official domains link
- no seed/private key collection
- risky-link review state
- stale content state
- safety escalation path

### P0.5 Weekly Pulse

Weekly Pulse must publish:

- shipped work
- needs help now
- governance watch
- project updates
- docs/education
- local communities
- safety notes
- contributor spotlight

## P1 Product Requirements

### P1.1 Contributor Recognition

Recognize:

- merged PRs
- published guides
- translations
- event recaps
- verified support answers
- project testing reports
- governance summaries

Do not optimize for likes, posting volume or social noise.

### P1.2 Governance Control Room

Each proposal needs:

- plain-language summary
- problem statement
- options
- affected groups
- risk and rollback plan
- current ask
- canonical links

### P1.3 Local Community Program

Each local page needs:

- language
- local lead/contact
- starter resources
- translation needs
- event kit
- open tasks
- safety links

### P1.4 Campaign Studio

Campaign materials need:

- approved claims
- source links
- short post
- long post
- visual brief
- translation notes
- forbidden claims
- reporting format

## P2 Product Requirements

Consider only after MVP has real activity:

- user profiles
- contribution attestations
- AI assistant
- project health scoring
- reputation levels
- public leaderboards
- automated GitHub/forum imports

## Best-In-Class Principles

1. A portal is best-in-class when it reduces coordination cost.
2. Every page needs an action, owner or decision.
3. Every risky claim needs a source.
4. Every project needs freshness state.
5. Every contributor needs a first win.
6. Recognition follows shipped artifacts.
7. Automation follows stable editorial process.
8. Safety is part of the product surface.

## Anti-Roadmap

Do not start with:

- wallet login
- token rewards
- token-gated pages
- social feed
- broad chat
- price dashboards
- public rankings
- automated AI answers over unapproved sources

These features create moderation, safety and trust problems before the portal has proven basic contribution throughput.

## Strategic Source Notes

- ErgoDocs describes Ergo as an ecosystem with miners, nodes, maintainers, wallets, infrastructure operators, channel owners and community leads, which supports a role-based portal architecture: https://docs.ergoplatform.com/contribute/how-ergo-works/
- ErgoDocs frames change as both technical and social, with prototypes, tests, rollback plans, stakeholder mapping and public signals. The governance module should mirror this: https://docs.ergoplatform.com/contribute/how-ergo-works/
- Ergo Foundation scope emphasizes community-driven outreach and cautions that project highlighting does not equal endorsement. The portal needs visible community/official boundaries and risk states: https://docs.ergoplatform.com/ef/ef-scope/
- Gitcoin's contribution guide shows the value of explicit quality bars, accepted content types, review stages and attribution. The portal should apply similar standards to tasks and campaign submissions: https://gitcoin.co/contribute
- Discourse trust levels show a useful pattern: new participants start with low-risk reading and earn more capability through sustained behavior. The portal can borrow the staged-permission idea later without adding reputation too early: https://meta.discourse.org/t/discourse-trust-levels-a-detailed-explanation/396792