> 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/documentation/development/weekly-engineering-review.md). # Weekly Engineering Review Create one review record per week. ## Status * Week and meeting date * Attendees and workstream owners * Completed deliverables with links * Planned versus actual progress * Active pull requests and releases * Simulation and test status * Hardware inventory and blockers ## Safety and quality * New or changed hazards * Safety-scenario failures * Reliability, security, or privacy findings * Interface changes * Unresolved critical/high defects * Documentation gaps ## Decisions Record decision, alternatives, evidence, owner, due date, and whether an ADR or Go/No-Go review is required. ## Next week Assign each task an owner, measurable output, acceptance evidence, dependency, and target date. Carry overdue items explicitly rather than silently resetting them. --- # 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/documentation/development/weekly-engineering-review.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.