Where it usually breaks
And how to keep it from happening.
- An operator edits the published revision directly and the old evidence is lost.
- Two people request the same correction at once.
- A correction is made from an out-of-date copy of the asset.
Correct an executed revision by adding a successor, keeping the prior revision, its evidence and its completed steps.
Content Operator requests a documented correction for one asset and states the reason.
The request is checked for a duplicate correction, a downstream restriction and a stale input hash. Any of these stops the correction with a precise reason.
Otherwise the prior revision, its evidence and every completed step are kept, and a successor revision is added with a compensating output and refreshed derived values.
Content Reviewer approves the re-run of the successor revision before it is processed and published.
And how to keep it from happening.
Start free, then use Proto to change fields, steps and approvals before your team goes live.