Kernel corrects important mistakes by recording a new authorized fact rather than editing immutable history. The correction identifies what changed, why, when it should be effective, and when the correction was recorded.
Effective truth and recorded history
Suppose an Engagement actually became active before the system existed. An authorized backfill can record the historical effective activation time today. The effective time describes the relationship; the recording time proves when the system learned and accepted it.
If that effective time is later found to be wrong, a correction event supplies the corrected value. It does not mutate the original activation event, reactivate the Engagement, or infer a lifecycle transition from the date.
Not every typo requires an event-sourcing model. The adopted architecture uses transactional canonical state plus appropriate immutable domain and audit events, with stronger replay guarantees only where they are explicitly designed and tested.