# Repository and Version Control Standards ### Purpose Repository standards ensure that code, configuration, documentation, and evidence are controlled. ### Repository Requirements Repositories should include: * README * contribution guidance * branching strategy * code owners where appropriate * licence or IP notice * setup instructions * test instructions * deployment instructions * security notes * changelog ### Branching Branching strategy must be defined for the project. Typical branches include: * main * develop * feature branches * release branches * hotfix branches ### Commit Standards Commits should be: * clear * traceable * linked to work items where possible * focused on a single logical change ### Release Tags Releases should be tagged and documented. --- # Agent Instructions: 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: ``` GET https://framework.aic.io/company-operating-manual/engineering-and-technical-standards/repository-and-version-control-standards.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.