Skip to content

Revise an Approved Design

Goal: change what is approved without losing the thread of governance; the approved record stays intact, the change goes through the same gate, and the watch hands over cleanly.

1. Cut the Revision

On the approved package: Revise as New Draft. The revision carries a family ID (ACME-0012-R2) and starts from the approved content. One revision in flight per package. (Lifecycle)

2. Make the Change, Governed

Work the revision like any package: update inputs if the intent changed, re-run or edit the design. Two guards are watching on your behalf:

  • The scope guard quarantines uncited additions, so the boundary cannot grow silently while you are focused on the change.
  • The readiness board shows the boundary delta versus the approved predecessor; the approver sees cumulative growth, not just the last edit.

3. Through the Gate Again

Assurance re-scores, reviewers judge, approval locks. Nothing about being a revision skips a step; that is the point.

4. The Handoff

Approving the revision supersedes the predecessor: it remains immutable as the historical record, and the drift watch moves to the new baseline automatically. Production is now expected to match the revision; divergence from it is the new drift.

Emergency Changes

Nothing blocks editing an approved design in a genuine emergency; the platform detects rather than prevents. The discipline is what happens next: the drift finding it raises is your reminder to cut the revision and make the change official while it is fresh.