Recognition
Recognition keeps the Flarehub loop tight: contributors see where they stand, newcomers understand what excellence looks like, and programme leads reward the behaviour that compounds network health.
Signals we track
- Shipped outcomes: links to repos, deployments, dashboards, or publications tied to a scope.
- Community leverage: mentorship hours, unblock sessions, or cross-programme coordination.
- Narrative capture: retrospectives, case studies, and learnings shared publicly.
Recognition layers
- Milestone attestations — onchain or signed proofs attached to the proof-of-work tracker when a scope clears review.
- Spotlight features — monthly forum posts and call segments surfacing tactics, dashboards, or product launches.
- Delegated authority — invitations to lead reviews, steward budgets, or represent Flarehub externally.
Nomination flow
- Contributor (or peer) submits a recognition request through the ops form with linked artefacts.
- Programme leads review evidence, optionally requesting async clarifications within 72 hours.
- The decision and supporting rationale are logged in the forum. When approved, the attestation is minted and perks update automatically.
Transparency rules
- Every recognition entry includes who verified it, what evidence was used, and how it maps to membership tiers.
- Disagreements route to the escalation channel; a steward sets expectations on timing and required artefacts.
Why it matters
- Makes work legible and discoverable for partners, investors, and future collaborators.
- Builds trust, speeding up tier progression and access to higher-scope programmes.
- Reinforces a culture of sharing playbooks so successes can be replicated across the network.