The revisionHistory field keeps a structured trail of how a ComplianceReport changed as it moved through its lifecycle. This is especially valuable when a report cycles through REVISION_REQUESTED and back to SUBMITTED, because it preserves what was changed and when across each round of agency review. Stored as JSON rather than free text, it can hold a list of revision entries that the application reads and displays, complementing the human-written notes field with a machine-readable change log for audit and accountability.
Technical section
Data model, API, and internals — visible to developers.