For: Sheran, ahead of the Journey 10 scoping session. The one takeaway: the pack's re-scope is right (J10 is the lifecycle-state home framework, not a tenth comms journey) and survives challenge; the council corrected one materially stale figure, reconciled the pack to the consolidated Decisions Log, made all fourteen personalisation checklist fields explicit, and closed one decision as a working assumption. How to read: verdict, strongest points, changes applied (seven-field format), working assumptions adopted, what genuinely requires approval, evidence gaps.
STATUS: council review, 20 Jul 2026, agent-consolidated. Applied per the apply-directly rule; pack rebuilt and validated (PASS).
APPROVE the pack as the scoping-session input, with the corrections below applied. The framework thesis holds under every lens that matters here: the CTO/Architect view (one shared capability beats nine per-journey Home hacks; the cross-journey review independently sequences it as build order 4), the Product Manager view (the DEFINE gate is real: nothing builds before Sheran + Product rule scope, and the pack stages rather than pre-empts), the Design view (suppression-as-treatment, designed fallbacks, no guessed personas), and the Analytics view (the session-vanity trap is named, the primary metric is transaction-rate-vs-holdout, sessions are demoted to guardrail, and the unreadable-surface gate DL-013 is launch-blocking). The pack correctly owns almost nothing: one moment (ACT-12 returning treatment), a slot map, and a governance rule; everything else is a rendering contract.
1. Retired the stale ~44% Unclassified figure. What: every ~44% reference replaced with 1.7% unclassified (Ivi persona model, 3 Jul, confirmed; ~44% labelled stale caveat, superseded), plus the honest nuance that low-confidence reads also render the neutral card (threshold TBC: CRM + Analytics). Why: CROSS-JOURNEY-REVIEW figure clash 15 directs the J10 author to adopt the supersession; J6 already retired the caveat (JD6-12). Who: the returning-transactor cohort's neutral-card branch. Where: brief-tab quant grid + matrix row, walkthrough persona (Alex), Reference personalisation table, TO-BE map D3 pin, strategy.md E4/3c/6. Requires: BRZ-83 persona sync (D3) plus a confidence-threshold rule. Improves: design and copy effort land on the real cohort shape; the fallback becomes the safety net, not the main state. Action: Analytics confirms the 1.7% at scoping; no approval needed (figure correction).
2. Reconciled the pack to the consolidated Decisions and Approvals Log. What: D-J10 items now carry their DL ids; DL-001 references updated to DL-029; REC-21 and GRW-09 statuses upgraded from "ownership ruling open" to "DL-014: three packs agree (J7, J9, J10)" and "DL-015: both packs concur", ratification open. Why: the log is the source of truth post-consolidation; presenting agreed items as fully open overstates the scoping session's load. Who: the review group and the session attendees. Where: TO-BE map decision list + rendering contracts, brief tab, AS-IS tab, process tab, strategy.md section 5/6. Requires: nothing. Improves: a sharper agenda: six items to rule, three ratifications of cross-pack agreement, one label closed. Action: Sheran ratifies DL-014/DL-015 (already framed as easy ratifications).
3. Closed DL-119 (objective label) as a working assumption. What: O3 (habit loop) primary, O4 (re-entry) secondary, adopted; flagged veto-able at scoping; roster + portfolio rows to update. Why: escalation discipline: a labelling decision the pack already answers (the candidate metric is a habit metric); the hub walk already carried O3 as the working assumption. Who: reporting only. Where: exec summary, Objective and KPI, T&L table, TO-BE decision list. Requires: nothing. Improves: one fewer open decision; the test ladders cleanly. Action: none unless Sheran vetoes.
4. Made the fourteen-field personalisation and contact completeness checklist explicit. What: a new Reference-tab table stating all fourteen fields with pointers, filling the one genuine gap: field 12 (adaptation to response) now carries the working assumption that repeated impressions without a tap trigger eligibility rotation and a rest period (values TBC: CRM at build; the 9 Jul ruling already requires eligibility rotation). Why: COUNCIL-STANDARD requires all fourteen stated; twelve were implicit, one absent. Who: all rendered cohorts. Where: Reference tab. Requires: card impression events (DL-013 fix) to enforce rotation. Improves: review completeness; no reviewer has to reverse-engineer the contact logic. Action: none; the rotation values are a build-stage CRM call.
5. Tightened the measurement frame: KPI definition precedes sizing. What: added to the Analytics "Decide with us" block and the process-tab Analytics actions: define return-session to transaction rate precisely (which bid/booking window counts against a returning session) BEFORE sizing; added the persona-confidence threshold as a second decide-with-us item. Why: an undefined KPI cannot be sized or powered; the pack asked for sizing without the definition. Who: the holdout read. Where: brief tab Analytics section, process tab. Requires: Analytics (Ivi). Improves: a falsifiable, powered read; protects against post-hoc metric choice. Action: Analytics work item, no approval.
6. Anchored the shared-capability build order and decision dates. What: brief tab now states the framework's place (build order 4) with upstream dependencies (journey_state NOW, app_open + lifecycle-state event NOW ER, DL-013 fix) and consumers; process tab row 0 now carries the urgency chain (DL-029 walkthrough recommended 22 Jul, scoping by 24 Jul per DL-114, J8 ships 31 Jul). Why: CROSS-JOURNEY-REVIEW build order 4 and the DL dates existed but the pack did not carry them; a scoping session without a date drifts. Who: sequencing for all ten journeys. Where: brief + process tabs, strategy.md section 5. Requires: nothing. Improves: the session lands before J8's landing decision needs it. Action: Sheran schedules.