> For the complete documentation index, see [llms.txt](https://docs.nxcframework.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nxcframework.net/configuring/history.md). # History and audit > **Available.** Values are versioned rather than overwritten, so history and rollback both work. Reading the history currently means querying the database; the interface arrives with `nxc_devtools`. ## What is recorded Every publication records: | Field | Detail | | --------------- | --------------------------------------- | | Who | The actor account and character | | What capability | Which capability authorized it | | When | Timestamp | | What changed | Field, scope, before value, after value | | Correlation ID | Linking to any related operation | | Reason | Where the workflow requires one | ## Why values are versioned rather than overwritten Configuration values are recorded **per publication**. A publication does not overwrite the previous value; it supersedes it. This is what makes rollback a first-class operation rather than a manual redo — restoring a prior state means selecting a prior publication, not re-typing what someone remembers the old value being. It also answers the question that actually gets asked after an incident: *what was this set to at 9pm last Tuesday, and who changed it?* ## Sensitive values in the audit A field marked sensitive is audited as changed, with the actor and time, **without recording the value itself**. The audit answers who changed what and when. It is not a second store of the values. ## Retention Publication history is retained. The retention period and archival strategy are not yet decided — audit table growth is a real consideration for a long-running server. ## Reading the history Filterable by resource, field, scope, actor, and time range. An operator investigating a behavior change starts here. --- # 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://docs.nxcframework.net/configuring/history.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.