← Q3 journey review packs
Q3 journey review packs · Council assessment · Journey 6
Journey 6 council assessment (Recent winner: habit and advocacy, GRW-04/09/28/29)
Who it's for: Sheran (Gate-1 ruling) and the orchestrator consolidating the ten packs.
The one takeaway: the spine is the right shape and survives challenge; the council's material fixes were realigning the M39_E position to the cross-journey synthesis (DL-002) and surfacing that the journey's own entry event does not exist (JD6-16). Both are applied; the pack rebuilt and validated PASS.
How to read: verdict first, then strongest points, then the changes applied (seven-field format), working assumptions, what genuinely needs approval, and evidence gaps. Provenance: one consolidated council view, agent-derived; Sheran gates everything.
Verdict
Ready for team review (process step 5), DESIGN-STAGE. RECOMMENDATION: take the pack to the team and put six rulings on the Gate-1 agenda (below). The journey is not buildable today and does not claim to be: two launch-blocking data builds (positive_trip D1, savings traits D2) and the entry event (D11, interim adopted) gate any build. The advocacy sequencing rule is correctly encoded as the AND-gate and was held inviolate throughout; the pack's re-gate of the cards' OR trigger (verified in cards_v4: "2nd_win or post-positive-trip") stands.
Strongest points (unchanged by the council)
- The single arbitrated T+24h slot instead of four stacked sends: it operationalises the sequencing rule (advocacy > review > tracker) and closes the post-trip 48h pile-up named in the cross-journey review.
- The disruption FULL SUPPRESS as the experience, evidenced (disruption 64.2% negative, 12,359 tickets, confirmed), with positive_trip as a fire-time gate on every send.
- The personal-cadence trait as ONE shared build with Journey 8 (D3), on confirmed evidence that persona never sets cadence.
- Honest AS-IS: the void is real but M39_E is not pretended away, and every figure carries its label and source.
Changes applied (each: what · why/evidence · who affected · where · capability required · outcome improved · action needed)
- M39_E realigned to the DL-002 synthesis. The pack recommended REWORK IN PLACE; the consolidated log's synthesis (and the clash register's own recommendation) is Journey 1's IN ADDITION shape, and J6 was the only artefact still carrying the conflicting shape · all post-trip customers who also receive the +1d survey · the T+24h slot across brief, map, matrix, T&L, walkthrough email mock · the slot email becomes J6's OWN trip-anchored master; M39_E stays at purchase +1d as pure feedback, weekly cap not episode cap, same-day collision shifts the slot email to T+48h, new guardrail: M39_E survey completes must not fall · removes the sharpest inter-pack contradiction and protects an active attributed asset pre-Gate-1 · Sheran confirms DL-002 once, for J1 and J6 together.
- Entry-event gap surfaced and bridged (JD6-16, new pin D11). trip_completed does not exist (dbt R4 gap, confirmed, J1-D08); the draft presented it as available, and J1's departure+1d proxy cannot time a T+90min send · every entrant · entry trigger, map, brief, Eng actions · working assumption: schedule-derived arrival timestamp times the reflection push, Eng validates; fallback launches without the T+90min push · keeps the pack's readiness claim honest and gives Eng a single briefed build shared with J1's travel-completion floor · Eng feasibility check at validation.
- Fourteen-field personalisation and contact completeness table added to the brief tab. The standard requires all fourteen stated explicitly; the pack carried them implicitly across matrix, ladder and pins · reviewers · Campaign brief tab, before the Analytics brief · no new capability; consent/preferences (7), history (8) and response-adaptation (12) now have explicit single-line statements · faster, checkable review · none.
- Episode-cap case restated (JD6-10 / DL-096). The 3-send cap was partly justified by the survey rework, which DL-002 removed; the case now rests on job distinctness alone, and M39_E's cap interactions are stated (outside episode cap, inside weekly cap, same-day separation) · post-trip customers' total contact load · contact rules in brief, map rules, reference tab · backbone dials · keeps the ratification ask honest · Sheran ratifies the deviation as before.
- Boundary and shared-moment wording aligned to the consolidated log. JD6-02 is upheld by the cross-journey review, which also recommends deleting J1's stale interim D+30 no-send rule (DL-039) in the same ruling; GRW-09/J10 now carries DL-015's merged shape (J6 owns moment, outbound legs, timing, measurement; J10 renders the in-app leg under a rendering contract) · first-trip winners and returning customers · cross-journey notes, map exits, process tab · journey_state + the home framework · one owner per customer, no dual-send window · Sheran rules DL-089 and DL-039 together.
- Four decisions closed as working assumptions (escalation discipline). DL-094 (J8 hand-off restatement: pure ruling-4 alignment), DL-098 (persona correction: applying confirmed evidence), DL-099 (review frequency caps: no material risk), DL-100 (canonical M0-to-M1 figure: hygiene, moved to the validation plan) · none of these need formal authority; closing them trims the Gate-1 agenda to what genuinely does.
Working assumptions adopted (labelled in the pack)
- DL-002 synthesis: M39_E kept at +1d; J6's slot email is its own asset; same-day separation; completes guardrail.
- JD6-16: schedule-derived arrival anchors the journey until the real trip_completed event lands.
- DL-094/098/099/100 as closed above; DL-015 rendering contract for GRW-09; fixed 60d slip hand-off until D3/D2.
What genuinely requires approval (the Gate-1 agenda, six rulings)
- JD6-01 ratify the moment set and the spine (the pack's headline ask).
- JD6-02 / DL-089 the J1/J6 two-part boundary, ruled together with deleting DL-039's interim no-send exit.
- JD6-05 the T+24h slot arbitration order.
- DL-002 confirm the M39_E synthesis (one ruling covering J1 and J6).
- JD6-09 power users in J6 (pends D1 power definition; roster decision a).
- JD6-10 the 3-send episode cap deviation from J8's two-touch pattern.
Evidence gaps (REQUIRES VALIDATION, method and owner)
- Top gap: the journey's own denominator and baseline. 2nd-transaction cohort volume, eligible positive-trip volume out of 710,616 departures/yr, and the baseline next-transaction-within-60d rate are all TBC: Analytics (Ivi). Without them the headline holdout cannot be sized and the journey's value cannot be stated. Method: warehouse pull against the positive_trip DRAFT definition.
- positive_trip signal (D1) and savings traits (D2): do not exist; Eng/Data build, Ivi signs definitions; launch-blocking.
- M39_E trigger coverage (auction wins vs BUN only): unverified; sizes the same-day collision; Lisa + Analytics.
- T+90min timing: no post-trip dwell evidence exists; team walkthrough + Analytics; the headline test carries it.
- Referral estate: which of M16E/M17E/M18P still fire (Lisa); friend-side conversion and k-factor unmeasured (phase 2).
- Survey completes instrumentation (D8): the P0 link fix gates the review leg and trusted advocacy capture.
Pack rebuilt via build_pack.py against the frozen J8 template: VALIDATE PASS, 20 Jul 2026.