Explain the work behind a score
A contribution needs a purpose, evidence and a review outcome. Counts alone are not proof that the work was accepted or useful.
Pro Route / Founding team
Participation & reputation
PonzinomicsGive participation a visible trail.
A separate product direction for community engagement and reputation. Make the contribution, evidence and review understandable before turning them into a signal.
Overview
Ponzinomics is a supporting product for engagement and reputation concepts. Its proposed role is to help people discover useful communities and understand participation.
A distinct product, a shared language
Use the same definitions for people, communities and accepted evidence. Sapphire is the proposed visual direction; Pro Route remains the public product home.
User journey
The proposed contribution loop starts with an understandable task.
Choose a contribution
See the community, requested work, evidence and example reward before starting.
Prepare evidence
Write a useful explanation or attach an appropriate reference. Opening a social link does not prove completion.
Review and revise
A reviewer accepts evidence or requests a change. The preview simulates that decision explicitly.
Understand recognition
Accepted contribution signals can support a profile or discovery surface. Rewards and reputation need separately defined rules.
Concepts & rights
Recognition should not be mistaken for money or control.
XP and revenue stay separate
Contribution points describe participation. The Pro Route revenue league concerns app and Agent revenue. A quest completion must not silently increase revenue.
Reputation is a signal
A reputation score can inform discovery and review. It cannot independently authorize treasury spending, governance execution or wallet access.
Collection packs are a separate configuration
Pack concepts need explicit contents, eligibility, distribution, duplicates and rights. A sample reveal is not a purchase, guaranteed reward or permission to withdraw treasury assets.
Evidence needs context
Keep who contributed, which community requested the work, what was reviewed and whether recognition was claimed distinct. Provider clicks and browser state are not trusted proof.
Preview status
The integration is proposed. No external activity is verified by this guide.
Separate local development
Ponzinomics is developed separately. Its public documentation here does not deploy its application or connect it to Pro Route.
Pro Route demonstration
The community preview uses fictional tasks and explicit review simulation. Example XP is temporary and has no cash value.
No provider or reward connection
No X or GitHub verification, reputation feed, financial reward distribution, referral payout or external account authorization is active.
Integration boundaries
Exchange accepted evidence through a defined contract, not a shared browser assumption.
Future evidence adapter
A proposed connection needs stable contribution identifiers, review outcomes, attribution, reversals and duplicate protection. No production API or SDK is published here.
Community-owned policies
Task eligibility, reviewer roles, disputes and reward rules need explicit community configuration. An external score cannot override Pro Route’s permissions.
Provider boundaries
X, GitHub and wallet checks require their own reviewed authentication and verification contracts. Supporting networks remain a roadmap choice, not a current integration.
Validation checklist
A useful participation loop is understandable and reversible.
Explain each score
A visitor can find what was measured, the applicable period and whether the result is an example or accepted evidence.
Review the entire state sequence
Show submission, changes requested, approval and recognition. Prevent a repeat claim from adding the same contribution twice.
Keep rights separate
A badge, pack, ranking or quest reward never silently grants ownership, governance power or access to depositor funds.
Make failure understandable
Missing evidence, unavailable ownership checks and rejected work must remain distinguishable from successful verification.
Changelog
Proposed product direction and documentation changes.
16 September 2026 · Shared guide
Added a common documentation structure and clearly separated participation signals from revenue and asset authority.
16 September 2026 · Visual proposal
Introduced a sapphire documentation palette while keeping the product and evidence integration separate from the public Pro Route app.
Keep exploring
See the ideas in context.
Continue through the shared product library. The application and its live integrations remain separate work.