Step 1 of 7
Initial draft
- Lifecycle state
- Draft
- Launched at
- Not recorded
- Paused at
- Not recorded
- Completed at
- Not recorded
- Archived at
- Not recorded
Canonical lifecycle-boundary demonstration
Synthetic campaign lifecycle preview
Seven fixed source-derived lifecycle records show the bounded command transition contract without a merchant workflow or live campaign.
Synthetic campaign lifecycle — no campaign is created or sent
The lifecycle boundary accepts only a command-level boolean. It does not establish authorization identity, scope, or freshness.
This boundary does not evaluate eligibility, consent, suppression, country capability, template approval, entitlement, allowance, quiet hours, frequency caps, destination state, provider or sender readiness, or dispatch. Those remain separate current preflight inputs.
No campaign, customer, contact, template, schedule, queue item, message, database row, audit event, production evidence, or provider request is created.
Fixed canonical lifecycle steps
Draft
Step 2 of 7
Schedule
- Lifecycle state
- Scheduled
- Launched at
- Not recorded
- Paused at
- Not recorded
- Completed at
- Not recorded
- Archived at
- Not recorded
Step 3 of 7
Launch
- Lifecycle state
- Active
- Launched at
- 2026-07-20T02:00:00.000Z
- Paused at
- Not recorded
- Completed at
- Not recorded
- Archived at
- Not recorded
Step 4 of 7
Pause
- Lifecycle state
- Paused
- Launched at
- 2026-07-20T02:00:00.000Z
- Paused at
- 2026-07-20T03:00:00.000Z
- Completed at
- Not recorded
- Archived at
- Not recorded
Step 5 of 7
Resume
- Lifecycle state
- Active
- Launched at
- 2026-07-20T02:00:00.000Z
- Paused at
- Not recorded
- Completed at
- Not recorded
- Archived at
- Not recorded
Step 6 of 7
Complete
- Lifecycle state
- Completed
- Launched at
- 2026-07-20T02:00:00.000Z
- Paused at
- Not recorded
- Completed at
- 2026-07-20T05:00:00.000Z
- Archived at
- Not recorded
Step 7 of 7
Archive
- Lifecycle state
- Archived
- Launched at
- 2026-07-20T02:00:00.000Z
- Paused at
- Not recorded
- Completed at
- 2026-07-20T05:00:00.000Z
- Archived at
- 2026-07-20T06:00:00.000Z
Fail-closed invalid commands
These fixed canonical calls are rejected. The code and plain-language meaning are both shown; color is not required to understand the result.
| Fixed invalid command | Canonical rejection code | Meaning |
|---|---|---|
| Launch an active record | CAMPAIGN_COMMAND_NOT_ALLOWED | The canonical boundary does not allow this command from the current lifecycle state. |
| Resume a paused record with false | CAMPAIGN_AUTHORIZATION_REQUIRED | The canonical boundary requires an affirmative authorization input for this command. |
| Pause an active record before its launch time | CAMPAIGN_COMMAND_TIME_REGRESSION | The canonical boundary rejects an occurrence time earlier than recorded lifecycle history. |