Lifecycle tool, mockup

Overview

This week, across every journey

Agent-drafted, for human review

This week's read: winback-2026 is paused mid-ramp while the sending domain finishes warming, and sms-drip-2-4 is built and held with nothing sent. Three touches in winback-2026 are approved and ready; six open decisions remain in the journey file, down from eight. The figures in this card and the outcome bar below are an illustrative mock of what a weekly agent read will surface once send history exists; they are not measured.

winback-2026 paused mid-ramp, domain still warmingsms-drip-2-4 built, held, nothing sent yet

This week, in numbers

Live journeys

of 7 defined

+1 vs last week *

Gate 1 audience

150

winback-2026, pinned

+0 vs last pull *

Touches approved

3 of 3

winback-2026.messages.yaml

2 approved this week *

Open decisions

winback-2026.yaml comments

2 resolved this week *

Figures marked * are illustrative: there is no send history yet to compare against, so the delta line is a mock of the shape, not a measurement. The values above the delta line are read from the journey, message and audience files this builder already loads.

Request outcomes illustrative

sent: 72%held: 20%refused: 8%

No journey has sent yet (0 in flight across the board), so this bar is a mock of the shape the tool will show once winback-2026 resumes, not a real send outcome.

Quick Actions

Only the verbs this tool allows. There is no "new journey" button here, or anywhere in this tool: every journey began as a clone.

Activity feed illustrative

This tool has no activity log wired yet; these rows mock the shape.

pausedwinback-2026 paused2 hr ago

clonereconversion-2026 cloned from reconversionyesterday

approvetouch-3 copy approved by Njuiyesterday

holdsms-drip-2-4 built, held: nothing sent2 days ago

gatefrequency cap warned on SMS, 7d window3 days ago

Outbound, Apollo shared, read only

The two Apollo sequences are shown on the Journeys screen, read only. This tool never controls them: open the outbound console to pause, resume or watch one.

Open in outbound console ↗

Journeys

7 defined, 3 live, 1 paused

Control is per row: pause, resume, drain. There is no button here that starts a journey from nothing: every row on this screen began as a clone of another row. Only rows with a Definition file are rendered from real data; the rest are illustrative catalogue rows and are labelled as such so they cannot be mistaken for built journeys.

Journey	Name	State	Audience	Channel	In flight	Note	Definition
winback-2026	Dormant win-back	paused	150	email	0	ok, domain verified, warming up	`campaigns/lifecycle/winback-2026.yaml`
reconversion	Reconversion	live	live query	email+sms	unknown	ok	no definition file yet
nurture-product	Product nurture	live	22 lists	email	unknown	ok	no definition file yet
welcome-sms	Welcome SMS	live	list 68	sms	unknown	ok, Brevo automation 55	no definition file yet
dist-receipt	Distributor receipt	built	on upload	email	0	ok	no definition file yet
sms-drip-2-4	SMS drip 2 to 4	built	non-converters	sms	0	held, nothing sent	no definition file yet
c13-tradeshow	Trade show re-engage	draft	not defined	email	0	no audience	no definition file yet

Outbound, Apollo shared, read only

Every journey above is ours to pause, resume and drain. These two rows are not: they are Apollo sequences, shown here so nothing is invisible, and the only control on either is a link out. Sequence control, including launching and pausing one, lives in the outbound console, never here.

Journey	Name	State	Audience	Channel	In flight	Note	Definition	Actions
Jim Intro Sequence	-	Apollo, read only	-	Apollo email	-	illustrative, not yet read live	no definition file here	Open in outbound console ↗
Industry Intro, Parks & Rec	-	Apollo, read only	-	Apollo email	-	illustrative, not yet read live	no definition file here	Open in outbound console ↗

Clone from template: naming is validated here, inline

Every journey clone, node tag, audience, message, module and list name is checked against a pattern THE MOMENT it is typed or cloned, not on a separate screen nobody opens before naming something.

Thing	Pattern	Example
Journey	`<program>-<year>`	`winback-2026`
Node tag	`<journey>.<node>`	`winback-2026.touch-1`
Audience	`aud.<program>.<cut>`	`aud.winback.gate1-pilot`
Message	`msg.<program>.<role>`	`msg.cart.abandoned`
Module	`<role>, never client-prefixed`	`hero-2`
Brevo list	`<program>.<segment>`	`nurture.boat-lifts`

Inline check, live as you type

Typed name	Result	Why
`winback-2027`	✓ valid	lowercase, program-year, matches the journey pattern
`Winback_2027`	✗ invalid	uppercase and an underscore; pattern is lowercase, hyphens only
`hero-2`	✓ valid	module role name, no client prefix (correct, it is shared across clients)
`dockblocks-hero-2`	✗ invalid	module names are never client-prefixed; this breaks sharing with every other client

A clone inherits the template's exits, suppression and gates. There is no blank canvas: a journey that did not come from a clone does not exist in this tool.

winback-2026

paused, 150 in audience, 0 in flight

Activate requires approval: it produces a diff against the journey file (see below) and a named human approves it before it is live. Save draft never does.

Node graph: entry, message, wait, decision, branch, exit

Editing a cloned journey, not blank authoring. Drag a block onto the canvas to edit an existing step; there is no way to start a journey from here, only to change the one already cloned from a template.

Triggers

Activity

Segment entry

Actions

SMS

Conditions

Decision

Branch

Flow controls

Wait

Rendered from campaigns/lifecycle/winback-2026.yaml, not a hand-copied approximation.

entryentry

winback-2026.entry

audience: aud.winback.gate1_pilot; when: gate1b_dormant_365d; reentry: never; limit: 150

suppressionsuppression

winback-2026.suppression

stops: replied, unsubscribed, converted, stop_status; shared with: brevo, mailtrap

touch-1message

approved

winback-2026.touch-1

content: msg.winback-touch-1 (approved); if absent: abort

GATE: suppression

wait-1wait

winback-2026.wait-1

for 4d

touch-2message

approved

winback-2026.touch-2

content: msg.winback-touch-2 (approved); if absent: abort

GATE: suppression

wait-2wait

winback-2026.wait-2

for 4d

touch-3message

approved

winback-2026.touch-3

content: msg.winback-touch-3 (approved); if absent: abort

GATE: suppression

doneexit

winback-2026.done

Selected node (static preview)

idtouch-1

kindmessage

channelemail

tagwinback-2026.touch-1

gatesuppression

detailcontent: msg.winback-touch-1 (approved); if absent: abort

A real build wires this panel to whichever node is clicked on the canvas. Here it shows touch-1 as a fixed example of the shape.

Decisions in this file

open #1Sending domain. OPEN: RECOMMENDED, not decided (Alecia 2026-10-03: "meant it as a question"). Recommendation: m.dock-blocks.com via Mailtrap, because a dormant audience carries the highest unsubscribe risk and must stay off the Brevo account (strike two) and off the root domain (Matt's mail and Shopify transactional). DNS VERIFIED COMPLETE, read live 2026-10-03: all five Mailtrap records exist. mt75.m is the domain-verification/return-path CNAME, pointing at smtp.mailtrap.live, which publishes Mailtrap's SPF, so SPF passes on the return path and aligns under the root's adkim=r/aspf=r; Mailtrap's own docs say domain verification covers SPF and a separate SPF record should not be added. rwmt1/rwmt2._domainkey.m are the DKIM records, mt-link.m is the tracking record, and _dmarc.m exists with p=none. A PREVIOUS version of this line said SPF was MISSING; that was WRONG and is corrected here. The one oddity left, not to be changed: _dmarc.m's rua/ruf point at smtp-staging.mailtrap.net. The domain has never sent, so the 150-person pilot is also its warm-up.

decided #2The open/no-open fork and the "did not open" message (msg.winback-touch-2b) are RESOLVED 2026-10-03, Alecia's decision: dropped. Win-back is a straight line of three touches, matching Njui's approved campaign copy (gate1b, touches n=1/2/3). Everyone gets all three unless the suppression gate refuses them, or they reply or unsubscribe. There is no touch-2a/touch-2b distinction and no decision node; this is the permanent design, not a placeholder.

open #3Shared suppression across Brevo and Mailtrap is written here as a target (shared_with: [brevo, mailtrap]) but is not actually enforced: Mailtrap sends bypass the eight refusals in scripts/lib/brevo_send.py. Held by Alecia with Njui (prototype doc Part 7, "the one that cannot be deferred").

decided #4Content-type classification for frequency purposes. RESOLVED 2026-10-03, Alecia's decision: EDITORIAL. brevo-sending-limits-as-built.md gates per-person frequency by content type: promo 30 days, editorial 7 days, SMS 14 days, with a 3-in-30 backstop across any kind. This journey reads as a personal check-in from the CEO or the owning rep, carrying no offer, so it is classified editorial rather than falling to the promo default.

open #5The "one send per person per 90 days" rule is RECONVERSION's rule (returning leads), not this journey's. Confirmed by checking: lifecycle-surfaces-2026-10-01.html ties that 90-day language to "returning leads / Reconversion" specifically, and nothing in the win-back sources repeats it for gate1/ gate2/gate3b. Not applied here; see #4 for the rule that actually governs win-back's own cadence.

open #6gate2 (stalled prospects) has no SQL in export_audience.py per lifecycle-surfaces-2026-10-01.html ("gate2: not exported, no SQL exists"). This file only runs gate1_pilot. A gate2 wave is a clone, not an extension of this file, and cannot be built until that audience is exported.

The gate runs before EVERY message. Not once at entry. Somebody can unsubscribe between step two and step three, so an eligibility answer from five days ago is a guess about today. Njui raised this and the vendors agree: Braze rechecks the cap at the actual send. There is no holdout node. A holdout is a branch whose path does nothing, computed as an ordinary audience in the warehouse, same as any other segment, never a special node type.

Launch preflight, re-run on every refresh

Check	Now	Read
Audience pinned	pass	150 rows
Suppression fresh	pass	18,390, read now
Consent opt-in	pass	per person
Frequency	pass	see cap panel
Domain authenticated	pass	SPF via domain verification + DKIM live, DNS verified 2026-10-03
Domain warm	fail	no history
Stranded check	missing	sensor built, needs DSN

Frequency, both cap layers

Cap layer	Window	Now	Read
Email, per channel	30d promo cap	pass	3 of 30 used
SMS, per channel	7d cap	warn	2 of 3 used
Combined, all channels	stricter cap, evaluated last	pass	4 of 6 touches in 14d

Combined is stricter than either channel alone and is evaluated last. Someone can sit inside the email cap and inside the SMS cap individually and still be over the combined cap the moment both channels have touched them this window.

Propose an edit: agents propose, a human approves

journey winback-2026 · proposed by agent:cleanup-bot · status pending approval

- entry.limit: 150
+ entry.limit: 300
- wait-1.for: 4d
+ wait-1.for: 7d

A tool edit produces a versioned artifact: a diff against the journey file. Agents propose changes as a diff and never act. A named human approves it before it is live. Approved by: (not yet)

Sample Contact

sample.contact@example.invalid

illustrative, sample person No real contact is loaded here: this is one clearly-labelled sample row showing the shape of a cross-channel person view, not a real name or a real email. The fields themselves are real: Pause until and the 90-day re-approach hold are the two per-person holds this tool's own suppression model already names, surfaced here rather than only on a journey's own suppression node.

Pause until

2026-11-02

90d re-approach hold

active to 2026-12-01

Consent

opted in

Suppressed

Rep

Sample Rep

Sends from

team@example.invalid

Journeys this person is in

Journey	Current step	Last activity
winback-2026	touch-2	sent 3d ago
welcome-sms	touch-1	sent 16d ago

Content, not control. Nothing on this screen pauses, resumes or drains a journey, and there is no send-to-this-person control: those verbs live on a journey row (Journeys screen) or in the outbound console for Apollo, never here.

Audiences

6 defined

Filter by channel: All channelsEmailSMS

Audience	Size	Channel	Computed	Used by	Note
aud.winback.gate1-pilot	150	email	02:30 today	winback-2026	pinned
aud.winback.gate1-rest	1,648	email	02:30 today	wave 2	not released
aud.winback.gate2	no size	email	never	nothing	no SQL exists
aud.reconversion.returning	live query	email+sms	on trigger	reconversion	90d rule
aud.nurture.by-product	7 to 38 each	email	unknown	nurture-product	22 lists
aud.welcome.sms-opted-in	221	sms	on lead create	welcome-sms	Brevo list 68

Segments are computed in the warehouse, nightly, and the tool only selects them. Not defined in Brevo, not defined twice. Two definitions of dormant that disagree is the documented failure, and we already have three rival eligibility functions.

Compose · Messages

3 from winback-2026.messages.yaml, 3 illustrative

Compose is content, not control. Nothing on this screen pauses, resumes or drains anything: those verbs live on the journeys that use these messages, not here. The msg.winback-* rows are loaded from campaigns/lifecycle/winback-2026.messages.yaml: three touches, all status approved, sourced from Njui's approved campaign copy. The open/no-open fork and its unapproved msg.winback-touch-2b are RESOLVED (2026-10-03, Alecia's decision) and no longer exist in this registry.

Message	Stage	Blocks	Channel	Needs	If absent	Variants
msg.winback-touch-1	approved	none	email	2 attrs	abort	1
msg.winback-touch-2	approved	none	email	2 attrs	abort	1
msg.winback-touch-3	approved	none	email	2 attrs	abort	1
msg.cart.abandoned	draft	7 blocks	email	3 attrs	omit	6
msg.ambassador.invite	draft	6 blocks	email	2 attrs	refuse	2
msg.seasonal.roundup	not started	list shape	email	unknown	omit	unknown

Variants is the column that earns this screen. An attribute-driven message is a different body per person, so the defect that ships is in the variant nobody rendered. Six defects passed every automated check on Labor Day and were caught by eye.

Compose · Email builder

Email Welcome Template 101 · view only: marketers view, engineering authors

Engineering owns the gate, adapters, schema, validator and block authoring. Marketers view a block's rendered role and absent-handling and where it is used; editing a block is a code change and a review, same as the gate. These are the 8 blocks in the library, as tiles.

mastheadview only

header

Navy band, wordmark left, one line of context.

if absent: n/a

greetingview only

greeting

Hi {first_name}, falling back to 'Hi there'.

if absent: default

bodyview only

body copy

One idea per block. Paragraphs, no headings.

if absent: abort

item_rowview only

product line

One record or product. Repeats, omits itself if empty.

if absent: omit

ctaview only

call to action

One button. Builds its own tracked URL from the slug.

if absent: abort

dividerview only

rule

Hairline rule. Never an <hr>, which Outlook sizes unpredictably.

if absent: n/a

signoffview only

sign-off

Named human, their words. No title block, no logo.

if absent: refuse

footerview only

footer

Address and unsubscribe. CAN-SPAM, so it cannot be omitted.

if absent: refuse

Recipients for this message come from an audience computed in the warehouse. The builder selects one; it does not define one.

Audience	Size	Channel	Used by
aud.winback.gate1-pilot	150	email	winback-2026
aud.winback.gate1-rest	1,648	email	wave 2
aud.winback.gate2	no size	email	nothing
aud.reconversion.returning	live query	email+sms	reconversion
aud.nurture.by-product	7 to 38 each	email	nurture-product
aud.welcome.sms-opted-in	221	sms	welcome-sms

Merge fields render as chips in the preview, not raw placeholder syntax, so a marketer can see which parts of the body are per-person before anything sends.

Images and files referenced by the blocks above.

Asset	Type	Used by
masthead-logo.png	image	masthead block
brand-signoff.png	image	signoff block
product-roundup-hero.jpg	image	msg.seasonal.roundup (not started)

Preview

Welcome to {{company}}, {{first_name}}

Hi {{first_name}}, we've put together a quick intro to {{company}}'s products.

Test and Preview

Preview on devices

Spam score not run · placeholder

Preview renders a file for review. There is no send-test control here: a preview is a file, not a send. See feedback_preview_not_test_sends.md.

Architecture

LimeJourney's published backend components, mapped to ours

Boxes and labelled arrows, the shape of LimeJourney's own backend diagram: event sources into webhook intake, into the warehouse (bronze, silver, gold, where segments are computed), into the DBOS journey engine, through the send-time GATE before every send, out to Brevo and Mailtrap. Dashed boxes are GAPs: nothing is invented to fill them.

The table below is evidence under the diagram, not the view: each row traces to the repo doc or code line that verified it.

Web client / SDK

Event sources: Zoho CRM, Shopify, Brevo + Apollo, GA4 / Ads / Aircall

docs/planning/lifecycle-inventory-reconciled-2026-10-01.md source list (1)-(4); LIFECYCLE_COMMS_MAP.md system column

REST API

Webhook intake: scripts/webhooks/zoho_to_brevo.py, scripts/webhooks/shopify_to_zoho.py

scripts/webhooks/zoho_to_brevo.py, scripts/webhooks/shopify_to_zoho.py (code read)

Kafka event queue

GAP GAP: no event queue. Nightly batch via Dagster is right-sized for one client.

scripts/deliverables/build_lifecycle_surfaces.py: "No Kafka, one client, nightly batch is right-sized"

Postgres

DBOS system tables (durability) plus the warehouse Postgres (medallion bronze/silver/gold)

scripts/monitoring/dbos_version_drift.py DBOS_SYSTEM_DB_URL; build_lifecycle_surfaces.py warehouse box

Journey Engine (orchestrator + Temporal)

DBOS Transact: durable per-person execution, replacing Temporal

docs/architecture/eventcatalog-catalog-as-built.md:55 "DBOS callback"; docs/planning/lifecycle-inventory-reconciled-2026-10-01.md dormant-winback-2026.yaml executed by DBOS

Redis journey/trigger map

GAP GAP: no Redis. Nothing in this estate needs a sub-second lookup.

scripts/deliverables/build_lifecycle_surfaces.py: "No Redis, nothing needs sub-second lookup"

ClickHouse

GAP GAP: no ClickHouse. The gold layer (person_lifecycle, consent_state) answers these questions nightly, not in real time.

scripts/deliverables/build_lifecycle_surfaces.py: "No ClickHouse, gold already answers these questions"

Segmentation Engine

Warehouse gold layer, computed nightly by Dagster; the tool only SELECTS a segment, it never defines one

docs/planning/lifecycle-inventory-reconciled-2026-10-01.md: "Segments are computed in the warehouse and the tool only selects them"

External action (email / push)

Brevo (lifecycle email + SMS) and Mailtrap (volume sends, e.g. dormant win-back)

docs/planning/lifecycle-inventory-reconciled-2026-10-01.md: "DBOS via Mailtrap, sender matt@m.dock-blocks.com"

The send-time gate (ours; no LimeJourney equivalent in their published diagram)

Re-checked before every message: suppression, consent, frequency, ramp

docs/workflows/lifecycle-comms-senders-as-built.md gate logic traced in zoho_to_brevo.py; every message node in the Orchestrate canvas carries this as a GATE badge

Lifecycle tool, mockup

Overview

This week, in numbers

Request outcomes illustrative

Quick Actions

Activity feed illustrative

Outbound, Apollo shared, read only

Journeys

Outbound, Apollo shared, read only

Clone from template: naming is validated here, inline

Inline check, live as you type

winback-2026

Node graph: entry, message, wait, decision, branch, exit

Decisions in this file

Launch preflight, re-run on every refresh

Frequency, both cap layers

Propose an edit: agents propose, a human approves

Sample Contact

Journeys this person is in

Audiences

Compose · Messages

Compose · Email builder

Preview

Test and Preview

Architecture

Naming, applied where a name is typed