# Creative And Product Council

Date: 2026-05-21  
Scope: high-level creative and product direction for strengthening ErgoCommunity.org.

## Council Composition

This review combines the perspectives of:

- Chief Product Officer
- Executive Creative Director
- Head of Community Growth
- Head of Trust, Governance and Ecosystem Integrity
- Product Operations Lead

## Executive Direction

The portal should not feel like another crypto landing page, social feed or link directory. It should feel like a working room for people who want to help Ergo become more legible, safer and more useful.

Public promise:

> Find your role, claim useful work, prove contribution and make progress visible.

Internal creative platform:

> From spectators to operators.

## Strategic Upgrade

The strongest version of ErgoCommunity.org is built around repeatable rituals:

1. A newcomer chooses a role and claims a starter contribution.
2. A project lead publishes three help-needed slots.
3. A creator uses approved claims and sources before posting.
4. A local organizer launches a safe local cell.
5. A governance reader understands risks before joining a debate.
6. A safety reviewer keeps sensitive links and reports moving.
7. Weekly Pulse turns all of this into visible progress.

## Killer Bets

### 1. Contribution Receipts

Every accepted contribution should generate a small receipt:

- artifact URL
- contributor handle
- reviewer
- project or area helped
- impact note
- next suggested task

Why it matters:

Recognition becomes factual, portable and resistant to vanity metrics.

### 2. Weekly Pulse As Routing Engine

Pulse should not be a newsletter that summarizes the past. It should route the next week of work:

- 3 wins
- 3 asks
- 3 people to recognize
- 1 safety note
- 1 local action

Why it matters:

It converts attention back into claimable tasks.

### 3. Project Help Desk

Every active project gets a consistent help-needed surface:

- testers
- docs
- translation
- UX feedback
- security review
- issue triage
- launch support

Why it matters:

Projects stop being static catalog entries and become participation surfaces.

### 4. Verified Creator Kits

Creators should not start from a blank page. They need:

- approved claims
- source links
- forbidden claims
- translation notes
- required disclaimers
- proof log

Why it matters:

The community can promote Ergo without accuracy drift or hype language.

### 5. Trust As Interface

Trust should be visible wherever users act:

- link review state
- project risk state
- source type
- last checked date
- safety-sensitive warnings
- report path

Why it matters:

The portal earns credibility by showing uncertainty and risk clearly.

## Creative System

### Platform

Useful work, visibly proven.

Public line:

> Find useful work. Verify the path. Ship visible proof.

Core elements:

- Enemy: hype, stale links, vague tasks and unsafe support flows.
- Promise: anyone can find a safe next contribution in five minutes.
- Proof: every contribution leaves an artifact, owner, source and review date.
- Behavior: community-run, source-backed, safety-aware.
- Ritual: Weekly Pulse turns useful work into community memory.

### Tone

- direct
- grounded
- precise
- builder-friendly
- calm under risk
- welcoming without hype

### Avoid

- price narratives
- "official support" wording
- exaggerated safety claims
- generic Web3 slogans
- vague "join the community" CTAs
- social leaderboard dynamics in v1

### Use

- "Claim useful work"
- "Submit proof"
- "Reviewed by"
- "Last checked"
- "Community summary"
- "Not official decision"
- "Sensitive link"
- "Source-backed"

## Signature Moments

### Contribution Loop Rail

Show the participant story:

1. I arrived curious.
2. I found my path.
3. I claimed useful work.
4. I shipped proof.
5. I was recognized in Pulse.

### First Useful Action

The first meaningful moment is not account creation. It is opening a task that has owner, source, proof and next step.

### Claim Flow

The flow should feel like a handoff:

`Claim -> Discuss scope -> Submit proof -> Reviewed -> Recognized`

### Recognition Moment

Recognition should happen in Weekly Pulse and on relevant project pages, tied to artifacts.

### Safety Moment

When users touch wallet, bridge, DeFi, support or private-invite content, the portal should slow them down with a clear safety state.

### Local Moment

A local community should be able to launch with one page, one lead, one event kit and one translation queue.

## Semantic Color System

- Orange: action, claims, active contribution.
- Green/teal: verified, accepted, reviewed.
- Amber: caution, needs source, needs review.
- Red: high-risk, blocked, safety-sensitive.
- Neutral: informational, pending, operational metadata.

## Experience Bets

### V1

- Work Board with lifecycle and proof.
- Projects needing help with risk and freshness state.
- Weekly Pulse routing engine.
- Verified link registry.
- Signature programs section.

### V2

- Contribution receipts.
- Project pages showing fulfilled help-needed slots.
- Local cell maturity levels.
- Campaign proof log.
- Governance summary history.

### V3

- Optional contributor profiles.
- Attestations.
- AI source assistant.
- Program dashboards.
- Matching recommendations.

## External Pattern Notes

- GitHub community health files standardize contribution, support, governance and security guidance across repositories, which supports a Git-backed operating model for the portal: https://docs.github.com/en/communities/setting-up-your-project-for-healthy-contributions/creating-a-default-community-health-file
- Discourse trust levels show a staged participation model where users gain more capability through sustained behavior, which argues for staged contribution permissions later rather than instant public reputation: https://meta.discourse.org/t/discourse-trust-levels-a-detailed-explanation/396792
- Gitcoin Grants demonstrates that public goods communities compound through visible participation and community-backed recognition, not only funding mechanics: https://www.gitcoin.co/program
- Community Health Toolkit contributor docs show a mature first-time contributor path with forum discussion, issue claiming, setup, tests and maintainer review: https://docs.communityhealthtoolkit.org/community/contributing/code/