> For the complete documentation index, see [llms.txt](https://docs.tea.xyz/tea/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tea.xyz/tea/i-want-to.../learn-about-proof-of-contribution/future-work-and-roadmap.md). # Future Work and Roadmap Proof of Contribution is aiming to boost the sustainability of the software supply chain by addressing how OSS impact is measured and rewarded. While Proof of Contribution is being established centrally at first to allow proper spam protection and fair value attribution, the development and maintenance of Proof of Contribution will be progressively decentralized. The impact metrics used by Proof of Contribution will also be calibrated over time for more nuanced evaluations. Future versions of the algorithm may incorporate more varied types of contributions and dependencies, addressing both code and non-code factors. Spam detection and resistance will remain as a central focus for the design of the algorithm. Proof of Contribution is not just an algorithm—it also represents [a vision](https://tea.xyz/blog/tea-protocol-web3-value-creation) of an OSS landscape that is more equitable and community driven. The continuous refinement of Proof of Contribution aims to benefit all, from individual developers to the entire software ecosystem. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.tea.xyz/tea/i-want-to.../learn-about-proof-of-contribution/future-work-and-roadmap.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.