Master drift since October: where Audience fits on today's master #640

Activity

1. Silthus

   added

   wayfinder:research

   on Nov 5, 2026
2. Silthus

   added a parent issue on Nov 5, 2026

   • Audience in Workflows: recipients, topics, setup and email engagement #181
3. Silthus

   marked this as blocking on Nov 5, 2026

   • Audience rebuild plan: stacks on today's master #642
4. Silthus

   self-assigned this

   on Nov 5, 2026
5. Silthus commented on Nov 5, 2026

   

   Silthus

   on Nov 5, 2026

   OwnerAuthor

   More actions

   Runtime: T3 Code
   Task: node:delegated-task:command%3Amcp%3A6133b270-470c-45e4-a120-7eed6d297659%3Adelegate-task%3A8a37155c-3a7b-4fbc-b8bc-cc3886911b5d
   Child thread: thread:delegated-task:command%3Amcp%3A6133b270-470c-45e4-a120-7eed6d297659%3Adelegate-task%3A8a37155c-3a7b-4fbc-b8bc-cc3886911b5d

   Cast: Codex GPT-6.1 Sol, reasoning effort high (deep research). Cap: 90 minutes. Prompt rendered from lane-research-child.md.
6. Silthus commented on Nov 5, 2026

   

   Silthus

   on Nov 5, 2026

   OwnerAuthor

   More actions

   Note

   🤖 GPT-6.1 Sol responding on behalf of Michael

   Research complete against fetched master fa6c2b3facf.

   Research folder contains the findings, immutable source links, and overlap/porting matrix for all ten old drafts. Saved in signed commit e8701fe, with an identical copy at the map's shared notes/master-drift.md.

   • Placement: workflows still owns these scenes. Master now groups setup under one Messaging tab and adds Transactional and EmailDomain scenes. Old Opt-outs and Suppression URLs remain, including new Transactional variants. The manifest and messagingTabs.tsx are the integration points. Recommendation: reconcile the map's name with the new glossary, which reserves Audience for broadcast targeting and calls the consent area Recipients.
   • UI kit: current frontend rules still require LemonUI outside the today-rail-nav redesign. Quill header branches do not change that rule. Recommendation: retain LemonUI for the existing UI path.
   • Overlap: no unified recipients list/lookup/detail, suppressions HogQL table, FacetSearchBar, project-wide engagement dashboard, or preference-sync setup landed. Adjacent capabilities did: shared FacetRail, person email history, topic CRUD/MCP, workflow metrics, transactional log, and an atomic preference-write route. Recommendation: reuse those seams while preserving the missing recipient behavior. The report distinguishes each old draft from its nearest existing variant.
   • Conflicts: the per-draft matrix covers every old feature and changed integration file. Messaging backend/api/ became backend/presentation/views/, tests moved, facades now own the boundary, generated APIs expanded, and Workflows/Broadcasts routing changed. Recommendation: regenerate product registrations and API clients from current manifests/serializers, preserve Transactional/EmailDomain routes, and replace removed message-assets imports through the allowed facade.
   • Backend seams: persons join optimizations do not prove the old grouped recipient query bounded. Preferences retain exact identifiers. Suppressions gained hard_bounced_at; transactional sends may pass manual, complaint and soft-bounce suppression. See the model and send check. Product isolation, changed-file Semgrep scans, shared pagination, frontend layers and repo invariants constrain the port. Recommendation: retain both mandated query fixes and update suppression copy/contract.
   • Dependencies: SDK #5173 is closed unmerged. Its open successor #5511 proposes posthog.emails.setPreferences({ to, allMarketing, topics }) with a project secret key and { data, error }. Its server route landed in #127204, but the SDK method is absent from current main. The flag constant is absent from master; the read-only control-plane lookup is documented privately. Recommendation: re-plan the setup dependency and explicit flag provisioning before implementation.

   Research calls:

   • ✅ Pinned source: use fetched master and separately pinned SDK main so later drift cannot change the meaning of the findings.
   • ✅ Overlap criterion: require equivalent recipient behavior rather than a similarly named audience or person-history feature.
   • ✅ Decision boundary: leave naming, slicing, SDK choice and rollout changes to the rebuild-plan ticket; this report makes recommendations only.
   • ✅ Read-only scope: no application code, builds, tests, PRs, flag changes, or other ticket mutations.
   • ❌ Using the old SDK draft as a shipped dependency: it is closed unmerged, current main lacks its messaging module, and the open replacement has a different contract. The old setup snippet cannot be carried forward as working setup.

   Validation: source paths checked, private commit signature verified, published report verified, shared-notes copy matched. Runtime behavior and query performance were not tested under this read-only brief.
7. Silthus

   closed this as completedon Nov 5, 2026