feat(feed): expand rollback post LinkedIn copy, drop version refs

content/feed/rollback-data-changes/index.md

@@ -1,6 +1,6 @@
 ---
 title: 'Oops! Now You Can Roll Back Data Changes'
-description: Despite all the checks in Data Controller for SAS®, sometimes the wrong updates get approved. Since v6.8, you can roll back to a previous version - with full audit history preserved.
+description: Despite all the checks in Data Controller for SAS®, sometimes the wrong updates get approved. You can now roll back to a previous version - with full audit history preserved.
 date: '2026-08-20 09:00:00'
 author: 'Data Controller'
 authorLink: https://www.linkedin.com/showcase/data-controller-for-sas
@@ -13,7 +13,7 @@ previewImg: './rollback-trains-meme.jpeg'
 
 Despite the MANY checks and guarantees in Data Controller for SAS®, sometimes it can happen that the wrong updates are approved and applied.
 
-Thankfully, since v6.8, it is now possible to **roll back** data changes to a previous state.
+Thankfully, it is now possible to **roll back** data changes to a previous state.
 
 ## How it works in practice
 
@@ -51,21 +51,29 @@ Full documentation is here: https://docs.datacontroller.io/rollback-data-changes
 <!--
 Source LinkedIn post:
 
-Oops!
+"Which submission introduced this value?" should never be a hard question to answer.
 
-Despite all the checks and balances in Data Controller for SAS®, sometimes the wrong edits slip through.
+Yet for many teams managing reference data, mappings, and regulatory adjustments in SAS®, a wrong approval means exactly that - an uncomfortable audit conversation, a forensic exercise, and a quiet hope that nobody upstream consumed the bad data.
 
-Since v6.8, you can roll back data changes to a previous version.
+Data Controller now lets you ROLL BACK a table to a previous state.
 
-It works by calculating every difference and submitting a new change for approval - so the rollback itself is reviewed and signed off, just like any other edit. The full audit history is preserved.
+Not by silently rewinding history - the one thing your auditor definitely does not want. Instead, the reversion is packaged as a brand NEW change that goes through the same review and approval as any other edit:
 
-Security is built in. Rollbacks respect the same access rules as edits, so not everyone can revert everything. And because every rollback creates a brand new audit trail entry, auditors can see exactly what was reverted, when, and by whom.
+- The reversion diff is calculated and staged
+- An approver reviews it before anything is applied
+- The rollback itself lands in the audit trail - who, what, when, why
+
+Nothing disappears. The original mistake, its correction, and every state in between all remain fully traceable.
+
+Access rules apply exactly as they do for edits - the same group permissions, the same restrictions. A rollback cannot be used as a shortcut around your controls.
+
+For regulated reporting data - the kind where "oops" is a reportable event, not a shrug - this closes the loop between catching an error and evidencing its correction.
 
 The underlying process is open source.
 
 Link in the comments below 👇
 
-#sas #sasviya #datamanagement
+#sas #sasviya #datagovernance #datamanagement
 -->
 
 <!-- Image prompt: