> For the complete documentation index, see [llms.txt](https://opsmanual.studentrobotics.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://opsmanual.studentrobotics.org/v4/miscellaneous/change-log.md). # Change Log {% hint style="info" %} Each release of the Operations Manual has an entry on this page. Within this entry changes are broken down into 'Added', 'Changed', 'Removed' and 'Minor Fix'. The first three categories cover modifications that affect the function of the document, whereas the last one includes modifications that do not, for example corrections to typos and formatting. Each entry also includes the date on which it took effect. {% endhint %} ## Version 4 (2018-08-30) ### Added * Change Log page to document modifications between releases. * Instructions in the [Making Changes](/v4/miscellaneous.md#making-changes-to-this-document) section to ensure that the Trustees have approved the release of a new Operations Manual, the decision to release is recorded, the Change Log is updated with the modifications made and the new version number and date of release is entered into the Change Log. * Clarification to [Safeguarding](/v4/about-the-charity/safeguarding.md) that it is only young people who are participating in Student Robotics activities that volunteers must not meet outside of the supervised environment. * Examples of who 'those who participate in our community' are in [Purpose](/v4/about-the-charity/code-of-conduct.md#1-purpose) section of Code of Conduct. * Instructions to [Reporting Guidelines](/v4/about-the-charity/code-of-conduct.md#6-reporting-guidelines) in Code of Conduct detailing what information to include in a report, how the report is handled and how corner cases, such as the person being accused being one of the people who normally deals with reports, are dealt with. * Clarification to [Core Team's Expectations of the Trustees](/v4/annual-robotics-competition/core-team.md#core-teams-expectations-of-the-trustees) number 6 that only Trustees have direct access to volunteer dataset and that the Core Team will have to work with the Trustees to make use of it. * Clarification to [Budgeting Requirements](/v4/annual-robotics-competition/money-matters.md#budgeting-requirements) number 5 to remove ambiguity around what the '£1000' is referring to. ### Changed * Only store geographical region, instead of full postal address, in [volunteer register](/v4/annual-robotics-competition/volunteers.md). * Soften 'expected' to 'will ideally' in Core Team [Defining Features](/v4/annual-robotics-competition/core-team.md#defining-features) section. * Make Core Team [Defining Feature](/v4/annual-robotics-competition/core-team.md#defining-features) number 2 more all-encompassing. * Shift dates of Core Team convening and disbanding one month earlier in the year (now convene in June and disband in May). This is to better align with the school year. * Expect Core Team to run a Competition Program, rather than an explicit annual robotics competition, in [Trustees' Expectations of the Core Team](/v4/annual-robotics-competition/core-team.md#trustees-expectations-of-the-core-team) number 4. ### Removed * Pre-selection of 10 people to invite to the meeting to form the Core Team in the [Core Team Formation](/v4/annual-robotics-competition/core-team.md#formation) section. * Sentence explaining why more than eight people are invited to the meeting to form the Core Team in the [Core Team Formation](/v4/annual-robotics-competition/core-team.md#formation) section. * Explicit list of volunteer details recorded from [Core Team's Expectations of the Trustees](/v4/annual-robotics-competition/core-team.md#core-teams-expectations-of-the-trustees) number 6. (This information is already defined on the [Volunteers](/v4/annual-robotics-competition/volunteers.md) page). * Reference to not giving refunds to paid events from [Consequences of Unacceptable Behaviour](/v4/about-the-charity/code-of-conduct.md#5-consequences-of-unacceptable-behaviour) section of Code of Conduct. We don't run paid events, so it isn't relevant. ### Minor Fix * Make release procedure in [Making Changes to this Document](/v4/miscellaneous.md#making-changes-to-this-document) section into a numbered list. * Make points under [Trustees' Expectations of the Core Team](/v4/annual-robotics-competition/core-team.md#trustees-expectations-of-the-core-team) number 8 (be self-organising) into a numbered list. * Expand 'SR' into 'Student Robotics' in [Safeguarding](/v4/about-the-charity/safeguarding.md). * Reference Trustees' email address in a more readable manner in [Safeguarding](/v4/about-the-charity/safeguarding.md) and [Code of Conduct](/v4/about-the-charity/code-of-conduct.md). ## Version 3 (2018-07-09) The whole Operations Manual has been completely rewritten and bears little resemblance to Version 2, therefore it would not be sensible to try and enumerate all of the changes. Version 3 effectively represents a completely new direction for the Operations Manual and should be viewed as a completely new work. --- # 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://opsmanual.studentrobotics.org/v4/miscellaneous/change-log.md?ask=&goal= ``` `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.