> For the complete documentation index, see [llms.txt](https://x.ancorasir.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://x.ancorasir.com/me303-311/2020-autumn/project-work/me303-code-of-ethics-submission-form.md).

# \[ME303] Code of Ethics Submission Form

* Review samples of the Code of Ethics
  * [By ASME](http://web.mit.edu/2.009/www/resources/mediaAndArticles/ASME_ethics.pdf)
  * [BY 2.009 from MIT](http://web.mit.edu/2.009/www/codeOfEthics/codeOfEthics.html)
* Access your team’s shared folder on Feishu
  * Locate the file “\[ME303] Code of Ethics by \[Team Red/Green/Blue/Yellow]
  * Collaborate within your team to prepare the document
* Once finished, export as a PDF and [email it to Mr. Guo Weijie](mailto:11510615@mail.sustech.edu.cn)
  * The Workshop staff will perform an on-site review of the document
  * Based on the comments from the workshop staff, revise your Code of Ethics document on Feishu
* Once finished, export as a PDF and [email it to Mr. Guo Weijie](mailto:11510615@mail.sustech.edu.cn), again
* Before class ends, all members of the team sign the printed document and submit the hardcopy to Mr. Guo Weijie


---

# 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://x.ancorasir.com/me303-311/2020-autumn/project-work/me303-code-of-ethics-submission-form.md?ask=<question>&goal=<user_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.