This is a project-wide snapshot, not an assessment of your business or a live connection to any provider. It contains no account or customer records.
Fictional rehearsals do not verify real permissions, sender readiness, appointments, payments or operating coverage. Proposed roles below are not confirmed assignments.
Evidence baseline: the FYB-98 fictional release, 22 October 2026. Changes require a new review; this page does not monitor live state.
FIRST DECISIONS
Define the pilot before building its live path.
Confirm the country and use case, privacy review and agreements, provider and sender, staff coverage, commercial limits and data-lifecycle rules. The business owner and operator need named responsibilities for these decisions.
Build and review the private quarantine, authorization and safe parsing path.
Test redaction, mapping, confirmation, interruption recovery and approved cleanup rules with isolated data before any real upload.
Production acceptance: not verified
Next action
Design the upload path only after the privacy and operating decisions are recorded; keep the real file gate closed.
Production requirement: Build and review the production upload path: private quarantine, safe file validation/parsing, mapping, redacted preview, explicit confirmation and cleanup.
04
Uncleared production gate
Recipient eligibility and lasting suppression
Build needed
Implementation leadProposed lead · named owner unassigned
Review evidence and next action for Recipient eligibility and lasting suppression
What exists in the build
Build or fictional evidence only
A fixed fictional audience review records exclusions and a setup handoff. The STOP behavior is modeled with synthetic scenarios.
Implement and test real permission, freshness, deduplication and shared-number checks.
Verify suppression remains enforced after reimport and is not cleared by review closure.
Production acceptance: not verified
Next action
Define the evidence and exclusion rules with the operator, then test them in an isolated production-path implementation.
Production requirement: Verify real recipient eligibility, consent freshness, deduplication, shared-number handling and suppression that survives reimport.
05
Uncleared production gate
Messaging provider and registered sender
Decision needed
Business ownerProposed lead · named owner unassigned
Review evidence and next action for Messaging provider and registered sender
What exists in the build
Build or fictional evidence only
Twilio-first is the proposed build direction. The dispatch simulator makes no provider requests and does not validate sender registration or delivery.
Authorize the provider account, sender choice and required registration for the approved use case.
Name controlled staff test numbers and approve a bounded provider test before it runs.
Production acceptance: not verified
Next action
Record the provider/sender decision and test boundaries. This register cannot connect a provider or send a staff test.
Production requirement: Select and authorize the messaging provider, registered sender and controlled staff-number testing.
06
Uncleared production gate
Named staff coverage and operating controls
Decision needed
Rebook Repeat operatorProposed lead · named owner unassigned
Review evidence and next action for Named staff coverage and operating controls
What exists in the build
Build or fictional evidence only
The fictional inbox supports role assignment, resolution and reopening. These are rehearsal labels; no real staff membership or notification is created.
Assign actual coverage, escalation ownership and response boundaries.
Implement and verify real assignments, operator MFA, monitoring and the emergency send stop.
Production acceptance: not verified
Next action
Name an operating lead and staff coverage before implementing live assignment delivery.
Production requirement: Establish named staff coverage, secure actual assignments, escalation, operator MFA, monitoring and emergency send stop.
07
Uncleared production gate
Durable jobs, webhooks and recovery
Build needed
Implementation leadProposed lead · named owner unassigned
Review evidence and next action for Durable jobs, webhooks and recovery
What exists in the build
Build or fictional evidence only
Six fixed fictional dispatch scenarios cover pause, replies, STOP, expiry, duplicates and uncertain acceptance. Model success is not production webhook or worker validation.
Build the durable production event/job path and verify signed webhook ingress.
Test forged, repeated and out-of-order events, recovery, bounded retries and owned uncertainty without blind resubmission.
Production acceptance: not verified
Next action
Define the production event contracts and recovery ownership, then test the isolated implementation against the recorded scenarios.
Production requirement: Implement durable outbox/inbox and worker recovery; verify signed webhooks, duplicate/forged/out-of-order events, bounded retries, owned exceptions and uncertain-acceptance reconciliation.
08
Uncleared production gate
Current approval and final send checks
Build needed
Implementation leadProposed lead · named owner unassigned
Review evidence and next action for Current approval and final send checks
What exists in the build
Build or fictional evidence only
Immutable fictional campaign versions, exact-version decisions and prerequisite invalidation are implemented. A saved rehearsal does not create a live send job.
Implement the authoritative production checks at both scheduling and final submission.
Verify changes to approval, permission, sender, holds, windows, limits and entitlement stop queued work.
Production acceptance: not verified
Next action
Write the production gate contract and tests before adding any scheduling or provider submission path.
Production requirement: Enforce all current send gates at scheduling and immediately before submission: exact live approval, privacy/consent, sender, holds, local send windows, quota/spend limits and entitlement.
09
Uncleared production gate
Live trial start and exact expiry
Build needed
Implementation leadProposed lead · named owner unassigned
Review evidence and next action for Live trial start and exact expiry
What exists in the build
Build or fictional evidence only
Account foundation and fictional responses keep the trial at NOT_STARTED. Expiry behavior is modeled; no approved live provider acceptance has been tested.
Implement an atomic, once-only start from the approved live acceptance event.
Test exact UTC expiry, accepted-versus-delivered behavior and expiry enforcement during orchestration failure.
Production acceptance: not verified
Next action
Implement and verify the isolated entitlement state machine after the owner approves the trial rules; do not start a trial.
Production requirement: Verify live trial behavior separately: starts once on first approved live provider acceptance, accepted differs from delivered, exact 14 × 24-hour UTC expiry blocks new outreach independently of orchestration.
10
Uncleared production gate
Paid continuation and cancellation
Decision needed
Business ownerProposed lead · named owner unassigned
Review evidence and next action for Paid continuation and cancellation
What exists in the build
Build or fictional evidence only
Signup requests no card. Pricing and trial explanations do not establish approved billing terms or a working paid entitlement integration.
Approve the price, usage allowance, cancellation terms and billing provider.
Build hosted checkout and verified payment/subscription reconciliation; test failure and cancellation before granting paid entitlement.
Production acceptance: not verified
Next action
Record the commercial decision first. No payment, checkout or subscription can be initiated from this register.
Production requirement: Implement paid continuation only after approved terms, explicit hosted checkout and verified billing-provider state; handle failure and cancellation without unintended entitlement.
11
Uncleared production gate
Export, offboarding and data lifecycle
Decision needed
Business ownerProposed lead · named owner unassigned
Review evidence and next action for Export, offboarding and data lifecycle
What exists in the build
Build or fictional evidence only
Fictional booking history distinguishes requests, confirmations and visit outcomes. It does not verify real bookings, revenue, private export or restore procedures.
Approve retention, deletion, minimum suppression and open-reply handoff rules.
Implement authorized exports and offboarding; verify access, safe export values, backup and restore in an isolated rehearsal.
Production acceptance: not verified
Next action
Name the data-lifecycle owner and approve the policy before implementing retention or deletion jobs.
Production requirement: Approve and test export/offboarding, open-reply handoff, retention/deletion, minimum suppression records, backup and restore.
12
Uncleared production gate
Production security and release acceptance
Verification needed
Rebook Repeat operatorProposed lead · named owner unassigned
Review evidence and next action for Production security and release acceptance
What exists in the build
Build or fictional evidence only
The previous fictional release passed 63 application tests plus isolated SQL checks. Desktop/mobile browser checks and anonymous live access checks were recorded; that evidence is limited to the fictional build.
Complete production security, tenant isolation, operating and physical-device acceptance against the real implementation.
Collect provider/data-path evidence and explicit owner authorization for the separately defined live pilot. No production gate is cleared by this page.
Production acceptance: not verified
Next action
Plan the acceptance matrix and assign its reviewers. Keep authorization and actual activation separate from this read-only register.
Production requirement: Complete production security, tenant-isolation and device acceptance review, then obtain explicit authorization for any real upload, messaging, launch or trial activation.
What this register cannot establish.
It cannot clear a production gate or authorize an upload, provider test, payment, live send or trial start. Real-data, real-provider, production security and physical-device acceptance remain outstanding. Any future activation needs separately recorded evidence and explicit authorization.
Existing records are preserved. This page makes no account, database or provider requests and saves no changes.
