Changes
The solution's change history: every change to records, acceptance criteria, relations, work, knowledge, tests and code links, with who made it, what changed and why. It cannot be edited.
What is recorded
- Who: a person, an AI agent, an integration (GitHub, GitLab) or CI.
- What: the item, the action and each changed field with its old and new value; acceptance criteria show the lines removed and added.
- Why: changing an Authority record requires a reason, kept with the change. Other edits can carry one too.
Bulk change proposals: when one decision or one change in a regulation reaches many records, an agent proposes the change to all of them with one reason (propose_bulk_change). The batch page (Changes → the CHB-… code) shows every difference; accept or reject them together, or open a record to decide it alone. Each change is accepted under its record's own rules, so a person may be able to decide only some of them; a record changed since the proposal can only be rejected.
Redact (workspace owners and admins): if a password or personal data was written into a record, correcting the record leaves the old value in the history. Redact replaces that value with [redacted]; the redaction and its reason are kept in the history.
Where to see it
Each record, work item, knowledge item and test case has a History section. This page shows the whole solution, filtered by period, kind, who and code.
Coding agents call get_changes at the start of a session to see what changed since their last check, and get_work_context lists recent changes to the item and its requirements. Automation can read GET /api/changes with a solution token.