> For the complete documentation index, see [llms.txt](https://carec.gitbook.io/carec-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://carec.gitbook.io/carec-docs/changelog/readme.md). # Changelog Follow material project changes, releases, milestones, and documentation updates. {% updates format="full" %} {% update date="2026-08-26" tags="documentation,foundation" %} ## CAREC documentation foundation The first public CAREC documentation structure is now available. ### Added * Getting Started and contributor-without-hardware guidance * Architecture and operating-mode foundations * Autonomous Mobility and Simulation sections * Hardware and Software documentation * Safety principles, hazard analysis, alerts, safe states, and validation * Development and Contributor Guide sections * Research, Roadmap, Reference, and troubleshooting foundations * SenseCAP Watcher W1A firmware programming guide ### Status CAREC remains a development-stage project. The immediate focus is a reproducible simulation baseline and reviewed safety requirements before unoccupied hardware integration. Explore the documentation {% endupdate %} {% endupdates %} --- # 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://carec.gitbook.io/carec-docs/changelog/readme.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.