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.
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.mddocs/roadmap_day_by_day_execution_plan.mdDay 17 and Day 27Scope
Acceptance Criteria
Contributor Fit
Strong frontend/research bridge issue.