> For the complete documentation index, see [llms.txt](https://www.build3.network/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.build3.network/researchers/use-cases/record-of-work.md). # Record of Work ## Qualitative Productivity as a Quantitive Measure The quality and throughput have never been reliably measured. It works for specific talents and personality types. What we are talking about is a more true and revealing method of calculating what someone has contributed to their work. This allows for traditionally ignored traits of a worker can be made visible to the network. The same protocols implemented in the [engineering supervision](/researchers/use-cases/proof-of-supervision-with-blockchain.md) use case also provide a more general-purpose proof of work for all players in the network. Any kind of work can be documented with this protocol. ### The Players There are three humans in this interaction. * **Worker -** The person that performs to the standard of care. * **Reviewer -** The person that reviews the work against the standard of care. * **Authenticity Validator -** The person that affirms both parties acted with good faith. ### Staking (Gamifying Quality Control) {% content-ref url="/spaces/3UKO6MPPEQpqMJk5aWx1/pages/zDUALdhqMobjanSQjbFB" %} [Staking](/developers/notes-about-substrate/prebuilt-pallets/staking.md) {% endcontent-ref %} #### Rewards a Function of n Reviews The review checks the work against the claimed standard of care. If approved on * Passes First Review: 10 tokens awarded to the worker * Second Review: 2 tokens awarded to the worker * Third Review: The total stake is lost and split between the network and burned * Reviewer is paid 1 token per review * The Authenticity Validator must affirm the authenticity of the transaction. If they reject the transaction, all parties lose rewards and stake. --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://www.build3.network/researchers/use-cases/record-of-work.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.