Skip to content

Frontend: Reputation and contribution dashboard #53

Description

@Abiorh001

Parent: #29
Depends on: #40, #42, #44, #50

Why

The Workstream needs visible contribution proof: shipped work, review quality, reputation events, ledger evidence, and public-output links. Workstream also needs reputation visibility for workers and reviewers.

Roadmap Source

  • docs/operations_payment_reputation.md
  • contributor onboarding context: reports, ledger expectations, public portfolio development
  • docs/roadmap_day_by_day_execution_plan.md Day 17 and Day 27

Scope

  • Worker reputation event view.
  • Reviewer reputation/quality event view.
  • Skill-tag contribution summaries.
  • Contribution proof panel linking issues, PRs, reports, public writing/media, and demo artifacts.
  • Metrics suitable for weekly/monthly report review.

Acceptance Criteria

  • Reputation events are shown with source records, not as unexplained scores.
  • Contribution panel supports maintainer review of shipping, research maturity, reliability, quality, and public contribution.
  • Dashboard does not overclaim portability or settlement features not implemented in v0.1.

Contributor Fit

Strong frontend/research bridge issue.

Metadata

Metadata

Assignees

No one assigned

    Labels

    area/frontendFrontend UI or demo/dashboard surfacearea/opsOperations, pilot setup, onboarding, reportingarea/reputationWorker/reviewer reputation events and metricsfocus/v0.1Current Workstream v0.1 roadmap focus; open to contributors unless explicitly assignedpriority/P1Important after the core loop works

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions