Blocking condition
Post-approval changes invalidate the previous approval and require a new review.
TRUSTED FACTORYFLOW
Approved recipe change and rollback
CHANGE-120 proposes changing RECIPE-R7 to R8.
REFERENCE JOURNEY · SAMPLE DATA
CHANGE-120 → RECIPE-R8 → RELEASE-120
Trigger and responsibility
| Aspect | Detail |
|---|---|
| Trigger | CHANGE-120 proposes changing RECIPE-R7 to R8. |
| Accountability | Change author · Independent approver · Cell engineer |
Sequence and progression conditions
-
Review parameter and program diffs, assess impact and prepare rollback.
-
An independent approver authorizes R8; sign the final record only if required.
-
Publish within the allowed window and wait for the active cell job before changing configuration.
-
Verify a trial job and QC; retain R8 or roll back to R7 under a traced decision.
Blocking and recovery
Reconciled recovery
Trial job fails: block new work, restore compatible R7 and verify controller state.
Outcome and evidence
Labels explain the journey; they do not replace each service state machine.
| Item | Result |
|---|---|
| Journey states | DRAFT → REVIEWED → APPROVED → PUBLISHED → VERIFIED / ROLLED_BACK |
| Evidence | Diff, approval chain, signed digest if applicable, deployed revision and trial or rollback results. |
Related contracts
Only actions with a relevant reference contract are linked. Other steps describe business coordination.
Task/mission APIs do not represent this journey. Dedicated integration follows the relevant service and project contract.