Canonical launch-boundary demonstration
Synthetic campaign launch preparation
Three fixed synthetic envelopes are passed to the canonical preparation boundary. This is read-only demonstration evidence, not a merchant workflow or approval screen.
Synthetic launch preparation — no campaign is scheduled or sent
This boundary validates only the supplied envelope's shape and fail-closed facts. Trusted regional transaction code must still authenticate the actor, establish authorization identity, scope, and freshness, calculate and independently verify inputs, persist the immutable snapshot and audit event, mutate lifecycle state, create queue/outbox records, recheck time-sensitive controls, and dispatch through an approved regional provider.
No campaign, customer, contact, template, schedule, queue/outbox item, message, database row, audit event, production evidence, or provider request is created.
Fixed canonical decisions
Scenario 1 of 3
Allowed immediate
Allowed- Allowed state
- Allowed
- Canonical command
- launch
- Target lifecycle state
- active
- Idempotency key
- 22222222-2222-4222-8222-222222222222
- Schedule mode
- immediate
- Scheduled time
- Not scheduled
- Eligible count
- 12
- Excluded count
- 3
- Cost and currency
- 4.25000000 USD
- Configuration hash
- aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa
- Approving actor identifier
- 11111111-1111-4111-8111-111111111111
- Snapshot schema version
- 1
Canonical violations
None produced.
Scenario 2 of 3
Allowed scheduled
Allowed- Allowed state
- Allowed
- Canonical command
- schedule
- Target lifecycle state
- scheduled
- Idempotency key
- 33333333-3333-4333-8333-333333333333
- Schedule mode
- scheduled
- Scheduled time
- 2026-07-20T08:00:00.000Z
- Eligible count
- 12
- Excluded count
- 3
- Cost and currency
- 4.25000000 USD
- Configuration hash
- aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa
- Approving actor identifier
- 11111111-1111-4111-8111-111111111111
- Snapshot schema version
- 1
Canonical violations
None produced.
Scenario 3 of 3
Blocked fail-closed
Blocked- Allowed state
- Blocked
- Canonical command
- Not produced
- Target lifecycle state
- Not produced
- Idempotency key
- Not produced
- Schedule mode
- Not produced
- Scheduled time
- Not scheduled
- Eligible count
- Not produced
- Excluded count
- Not produced
- Cost and currency
- Not produced
- Configuration hash
- Not produced
- Approving actor identifier
- Not produced
- Snapshot schema version
- Not produced
Canonical violations
PERMISSION_BLOCKEDCONSENT_OR_SUPPRESSION_BLOCKEDPREFLIGHT_BLOCKERS_REMAINEXPLICIT_CONFIRMATION_MISSING