AdvisorListen — How It Interacts With Everything

How to read it. One expanded pool — AdvisorListen — holds the two systems that do the work: the nightly Intelligence Pipeline on the Mac Mini and the Production Edge on Hetzner. Everything else is a collapsed pool exchanging messages with it. Solid lines are sequence flow inside the pool; dashed lines are messages crossing to a participant, drawn light so they sit behind the main flow.

1. Produce — at 00:30 CT the pipeline scrapes the sources, Claude Haiku 4.5 classifies each post, and the corpus is written to Postgres.
2. Compose — Claude Sonnet 4.6 (and weekly Opus 4.7) generate the briefs and HNW desks; the audio is voiced with OpenAI tts-1-hd. Each AI role binds a pinned, operator-selectable model — the CLAUDE_CLASSIFY / CLAUDE_EDITORIAL / CLAUDE_PREMIUM constants, with provider and fallback set by AL_AI_PROVIDER / AL_AI_FALLBACK_* — so output behavior cannot drift on a silent model upgrade (see the AI model registry note on the diagram).
3. Publish & gate — the run deploys to the edge, archives copies, and drafts the issue to the operator. No draft, no send: the subscriber campaign waits for the 06:30 gate (never Sunday), then goes out through SendGrid.
4. Serve — advisors open the email or visit the site. General content is public and skips the gate. At a NAIFA surface two checks fire in turn: Logged in? — if not, the visitor is sent to sign in and returned to the very same page via ?goto=; then NAIFA member? (verified or grace). nginx routes the page to Flask, which runs both. (The Listen Tools surface is gated by the same NAIFA check.)
5. Grace period — a logged-in member who isn't yet roster-matched takes the NAIFA gate's no branch into Claim, which grants provisional access immediately and opens a 720-hour (30-day) grace timer. During the window they have full access and see the yellow banner "NAIFA processing — verifying your NAIFA Alabama membership. Access granted · Nh left." At the timer (or earlier, the moment the roster matches), an on roster? decision resolves: a match → verified (permanent access, green "Active Member" banner, no countdown); no match by expiry → expired (access locked, back to claim). A member already on the roster — for example wes@c2wealth.com — skips grace entirely: the roster match short-circuits straight to verified, so they never see the yellow processing countdown, only the green Active Member state.
6. Measure & convert — every request and engagement is logged with the real source IP; the whole flow aims at one end event, a dues-paying NAIFA member.