Rationale allowing author to change artifacts after approval
One answer
Can someone please help me understand the rationale why RQM 3.0/4.0 allows the author of an artifact to change that artifact after it is "formally approved"? To me this is like signing a contract that's written with pencil.
It's configurable. If you go to the project properties there is a section called "Artifact State Transition Constraints". In that section there is a setting for whether you want resources in the approved state to be editable.