Scenario 1
blocked-dirty
Copy: blockedPublished embed: not verified
Admin widget lifecycle
Saved vs applied embed policy
F040 makes dirty, validated, preview-saved, persisted-saved, applied and published states explicit so copy-code cannot silently drift from the current draft.
Scenario 2
blocked-not-validated
Copy: blockedPublished embed: not verified
Scenario 3
allowed-preview-only
Copy: allowedPublished embed: not verified
Scenario 4
allowed-persisted-applied
Copy: allowedPublished embed: verified
F040 · saved/applied lifecycle
Lifecycle policy matrix
The Builder may copy preview-safe embed code after the applied draft is backend-validated. A production published embed remains blocked until an audited persisted save and backend published/applied timestamp are verified.
blocked-dirtychecked 6:33:08 AM
DirtyValidatedPreview save pendingPersistence blockedNot published
- Draft is newer than the applied/validated config. Apply + validate again before copy or save.
- No audited persisted save has been verified in this frontend session.
- Published/applied backend policy is not verified yet; embed code remains preview-gated.
blocked-not-validatedchecked 6:33:08 AM
Applied draftValidation requiredPreview save pendingPersistence blockedNot published
- Backend preview validation has not accepted the applied config yet.
- No audited persisted save has been verified in this frontend session.
- Published/applied backend policy is not verified yet; embed code remains preview-gated.
allowed-preview-onlychecked 6:33:08 AM
Applied draftValidatedPreview-savedPersistence blockedNot published
- No audited persisted save has been verified in this frontend session.
- Published/applied backend policy is not verified yet; embed code remains preview-gated.
allowed-persisted-appliedchecked 6:33:08 AM
Applied draftValidatedPreview-savedPersisted-savedPublished