Ideas for best approach to "Content Management" approach to editing records

[expertexley]

Hello,

I'm building an App in AES.  I have a custom table that I'd like to maintain some basic "Content Management" with.  

Currently, I have a simple workflow that triggers whenever a record is created or edited (with some additional parameters), which will change its State (one of the Choice fields in the record) indicating it needs review, as well as firing off a Request and a Task.  

I was going to modify this approach and convert this workflow to have actual Stages, but here's a concern: the records within this table, once they are "active" and/or "published", are valid and can be used and reported against.  If that record is modified, I would prefer to use/report on the record state that was available when it was "active" and/or "published" - that is, I don't want to see the changes made to the record until they've gone through the mini Content Management workflow to be built.  I'm curious to see the community's approaches to this.

The only thing I could come up with was to have a new table (I assume best approach would be make the original table extensible?), that we would, via workflow, copy the record values to once a record meets the appropriate criteria ("published").  Modifications to the original table will go through the normal Content Management workflow, but view and reporting of Published records would be done against the extended table.

Any alternative, hopefully better options?