# MVP Product Specification

Дата: 2026-05-21  
Scope: first public release of ErgoCommunity.org as a community-run contribution OS.

## Product Promise

In five minutes, a visitor can choose a role, find a useful action, verify the safety boundary and understand how to prove completion.

## Primary User Journeys

### Journey 1: New Contributor

1. Lands on homepage.
2. Sees community-run and verification message.
3. Chooses role.
4. Opens matching tasks.
5. Selects starter task.
6. Reads owner, scope, time estimate and proof required.
7. Follows source link or contact path.

Success:

- User claims or starts a task.

### Journey 2: Project Lead

1. Opens ecosystem map.
2. Reviews project profile standards.
3. Opens project intake.
4. Submits project card with help-needed slots.
5. Receives review state.
6. Project appears with last checked date.

Success:

- Project has a verified card and at least one actionable request.

### Journey 3: Weekly Editor

1. Opens Weekly Pulse template.
2. Pulls shipped work, open needs, proposal updates and safety notes.
3. Checks sources.
4. Publishes digest.
5. Adds contributor spotlight.

Success:

- Pulse is published without engineering support.

### Journey 4: Governance Watch Reader

1. Opens Governance Watch.
2. Reads proposal summary.
3. Checks affected groups, risks and current ask.
4. Opens canonical discussion link.
5. Adds informed feedback.

Success:

- Reader understands proposal state before joining debate.

### Journey 5: Safety-Conscious User

1. Sees safety strip.
2. Opens Trust and Safety.
3. Verifies official domains.
4. Checks warning before wallet/bridge/DeFi action.

Success:

- User uses verified resources and avoids unsafe support flows.

## MVP Screens

### Homepage

Required:

- community-run label
- role selection
- priority tasks
- weekly pulse preview
- verified links strip
- trust card

### Paths

Required:

- at least 8 role cards
- first actions
- matching task CTA

### Contribute

Required:

- search
- filters
- task cards
- selected task brief
- owner, time, proof and first step

### Projects

Required:

- project cards
- status labels
- last checked date
- help-needed slots
- verification model

### Governance

Required:

- proposal cards
- stage indicator
- summary
- current ask

### Campaigns

Required:

- launch kit
- education pack
- proof log

### Roadmap

Required:

- 30/60/90 day plan
- phase success criteria

### Intake

Required:

- project profile template
- task template
- governance summary template
- campaign kit template

### Safety

Required:

- no seed/private key warning
- official link guidance
- community-content boundary
- stale data explanation

## MVP Data Requirements

Minimum launch inventory:

- 8 role paths
- 20 contribution tasks
- 20 project cards
- 3 governance summaries
- 4 local community stubs
- 1 weekly pulse issue
- 1 campaign kit
- 1 safety page

## MVP Acceptance Criteria

- Every task has owner, proof required and status.
- Every project card has last checked date.
- Every risky link has review state.
- Every role path has a matching CTA.
- The portal can be updated by content editors.
- No wallet connection exists.
- No page asks for recovery data.
- Weekly Pulse can be published without code changes.

## MVP Quality Bar

The MVP is not complete if:

- it is mostly a list of links
- task cards lack owners
- project cards lack freshness
- official/community boundary is unclear
- safety content is buried
- contributor recognition is missing
- homepage does not lead to action