Rules Change
Change Risk Story
Rules change
An activity is updated
A task is added
The update is not acknowledged
Later, something goes wrong
The question is simple
Which version applied at the time?
The risk is old versions being used
Version Update Acknowledgement
When an activity changes, Cushi creates a new version
Previous versions remain recorded
Before tasks can be completed, the new version must be acknowledged
Cushi records the activity, version, user, and time
Version history and acknowledgement screen
Version Governance
Without version control
Different people follow different steps
Old instructions remain in use
With version control
One current activity is visible
Changes are traceable
Acknowledgement is tied to the correct version
Cushi records acknowledgement before execution.
It does not manage compliance.
Enterprise Control Lens
In larger organisations
Activities change often
Controls are updated
Records must remain traceable
Compliance assessment remains the responsibility of the organisation
Start
Control the version
Require acknowledgement
Keep the record
Hostile Audit – Rules Change
No compliance guarantees
Activity → tasks structure preserved
Version control described factually
No duplicated permanence statements
Clear boundary language
Word count reduced without weakening thesis