> 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/software/logging-and-configuration.md). # Logging and Configuration A CAREC run must be reproducible from its configuration and diagnosable from its logs. ## Configuration record * Code and package versions * Configuration schema/version and checksum * Robot model and hardware/simulator identifiers * Sensor calibration versions * Mobility mode and operating-domain selection * Speed, acceleration, clearance, timeout, and confidence limits * Map, route, world, and scenario identifiers ## Event record Log mode transitions, command source and arbitration, safety interventions, E-stop, takeover, sensor health, localization confidence, planner recovery, drive feedback, power state, software restarts, and configuration changes. ## Logging requirements * Monotonic and wall-clock timestamps with documented synchronization * Sequence numbers and component identifiers * Machine-readable reason codes * Severity and operator-facing message * Bounded storage and retention * Replay compatibility * No secrets or unnecessary child, medical, image, audio, or location data Every test artifact should link the log bundle, configuration, expected result, actual result, and analysis. --- # 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/software/logging-and-configuration.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.