> For the complete documentation index, see [llms.txt](https://nsysusa.gitbook.io/nsysusa/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://nsysusa.gitbook.io/nsysusa/information-disclosure-area.md). # 學生議會資訊公開專區由國立中山大學學生議會第十七屆更新（中華民國 113 年 6 月） #### 學生會官網：[https://nsysusa.org](#xue-sheng-hui-guan-wang-httpsnsysusa.org) #### 學生會粉絲專頁： #### 學生議會粉絲專頁： #### 選舉委員會官網： #### 選舉委員會粉絲專頁： #### 學生自治組織電子信箱： * 學生議會： * 行政中心： * 國立中山大學17學生會： * 評議委員會： * 選舉委員會： * 宿舍自治委員會： --- # 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://nsysusa.gitbook.io/nsysusa/information-disclosure-area.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.