> For the complete documentation index, see [llms.txt](https://snet-ambassadors.gitbook.io/singularitynet-archive/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://snet-ambassadors.gitbook.io/singularitynet-archive/timeline/2022/may-2022/week-20.md). # Week 20 May 9, 2022 to May 15, 2022 ## Tuesday, 10th May 2022 ### Ambassador Program kick-off Townhall Ambassador Town Hall meeting #1 was hosted by Peter Elfrink. {% embed url="" %} #### Timestamps by Felix [0:00](https://www.youtube.com/watch?v=4g_rUNNBQjI\&t=0s) Intro [2:18](https://www.youtube.com/watch?v=4g_rUNNBQjI\&t=138s) Meeting Kick-off [2:25](https://www.youtube.com/watch?v=4g_rUNNBQjI\&t=145s) Values and Goals [4:28](https://www.youtube.com/watch?v=4g_rUNNBQjI\&t=268s) outlines Overview [6:36](https://www.youtube.com/watch?v=4g_rUNNBQjI\&t=396s) Tasks People can do as an Embassador [10:01](https://www.youtube.com/watch?v=4g_rUNNBQjI\&t=601s) Signing up as an Embassador [15:54](https://www.youtube.com/watch?v=4g_rUNNBQjI\&t=954s) Interacting with newcomers [23:19](https://www.youtube.com/watch?v=4g_rUNNBQjI\&t=1399s) Roles and Tasks [24:03](https://www.youtube.com/watch?v=4g_rUNNBQjI\&t=1443s) Amplification of Messaging [28:15](https://www.youtube.com/watch?v=4g_rUNNBQjI\&t=1695s) Tasking an Initiative [38:35](https://www.youtube.com/watch?v=4g_rUNNBQjI\&t=2315s) Work Groups Suggestions [41:24](https://www.youtube.com/watch?v=4g_rUNNBQjI\&t=2484s) Certified Embassadors [46:30](https://www.youtube.com/watch?v=4g_rUNNBQjI\&t=2790s) Quality Standards and Tasks Feedback [51:29](https://www.youtube.com/watch?v=4g_rUNNBQjI\&t=3089s) Basic Knowledge Test [56:48](https://www.youtube.com/watch?v=4g_rUNNBQjI\&t=3408s) Proof of reputation and Rewards [1:08:23](https://www.youtube.com/watch?v=4g_rUNNBQjI\&t=4103s) Feedback Surveys [1:11:05](https://www.youtube.com/watch?v=4g_rUNNBQjI\&t=4265s) Outro #### Summary #### Welcome - Intro After an introduction the meeting was kicked off by x. Values and goals were expressed. For the community, by the community. Values and Goals * Transparency, open, simple * Spreading the word on SingularityNET #### Overview An overview of outlines. * Pilot phase Q2-3 * Sign-up form - required information * Roles, tasks, workgroups * Rewards #### Roles & Tasks Tasks that people can do as an ambassador are discussed. How to sign up as an Ambassador. Interacting and onboarding newcomers. Roles and tasks. How to amplify messaging. Tasking an initiative. #### Work groups Suggestions for workgroups. #### Rewards Certified Ambassadors. Quality standards and tasks feedback. Basic knowledge test. Proof of reputation and rewards. #### Open round and conclusions Feedback survey and outro. #### Slides {% embed url="" %} #### Miro Meeting Frame
--- # 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://snet-ambassadors.gitbook.io/singularitynet-archive/timeline/2022/may-2022/week-20.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.