> For the complete documentation index, see [llms.txt](https://docs.rainbowstandard.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.rainbowstandard.io/other/administrative-oversight.md). # Administrative Oversight Record ## Standard Advisory Board meeting notes
DateTypePublish decisions
April 27, 2023Standard Advisory Board meeting #1link
September 21, 2023Standard Advisory Board meeting #2link
February 14, 2024Standard Advisory Board meeting #3link
August 27, 2024Standard Advisory Board meeting #4link
June 4, 2025Standard Advisory Board meeting #5link
December 12, 2025Standard Advisory Board meeting #6link
## Rainbow Annual Activity Report
DateTypePublish decisions
March 4, 20242023 Annual Activity Reportlink
June 30, 20252024 Annual Activity Reportlink
April 30, 20262025 Annual Activity Reportlink
## Complaints and sanctions No complaints have been received, or sanctions applied. ## Miscellaneous
DateTypePublish decisions
May 15, 2024Mission audit statementaudit statement
July 28, 2025Registry Internal IT Auditlink
January 20, 2026Registry Internal IT Auditlink
July 20, 2026Registry Internal IT Auditlink
--- # 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://docs.rainbowstandard.io/other/administrative-oversight.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.