> For the complete documentation index, see [llms.txt](https://snet-ambassadors.gitbook.io/home/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/home/workgroups-space/video-workgroup/roles-and-their-kpis/meeting-documentation.md).

# Meeting Documentation

Meeting documentation involves the following:

* Attending the weekly meeting of the video workgroup on time, anything above the first 15 mins of the call the role will be assigned to someone else.
* Taking notes or recording all details mentioned or discussed in the meeting.
* Filling the information in the archival summary[ platform](https://archive-oracle.netlify.app/submit-meeting-summary?workgroup=30e3c903-eb5a-42bb-9a01-8c5223415ae0). Exporting your submission as a PDF.
* Submit the summary PDF to the workgroup for feedback and corrections.
* Once all corrections have been made and edited on the summary tool, submit the corrected PDF on Dework to the task created for this.
* Keep a record of your activities as subtasks on Dework.


---

# 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://snet-ambassadors.gitbook.io/home/workgroups-space/video-workgroup/roles-and-their-kpis/meeting-documentation.md?ask=<question>&goal=<endgoal>
```

`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.