Brainforge Knowledge

2026-03-16_weekly-kick-off-update

5 min read

CTA — Weekly Kick-Off Update

Date: 2026-03-16
Format: Kick-off (summary, last week, this week, blockers, actions, questions, next sync)

Internal (CSO notes)

Sources used:

  • Linear: Team CTA; list_issues (recent/updated). Projects/milestones inferred from issues (CES Analytics, Data Platform, Cortex ramp-up, Member Engagement Report, Integrations).
  • Transcripts: Last 7 days — no CTA-dedicated transcript in window (most recent: 2026-03-06 Brainforge x CTA weekly). Also checked knowledge/clients/unassigned/transcripts/; none in last 7 days mention CTA. Update leans on Linear and prior week’s kick-off (2026-03-09).
  • Slack: CTA is not in Supabase Slack project client tables (schema lists eden, javvy, abchome, etc., not CTA). Internal AI Core clients lookup returned permission denied. Slack MCP used as fallback: public search “CTA after:2026-03-09” returned only sales/deal mentions (e.g. Feb’6 – CTA (UPSELL) Deal #3 for Shopify), no client-delivery channel context.
  • Links: SOW and resources in knowledge/clients/cta/; CES execution roadmap, cortex runbook, and snowflake memos in vault.

Recommendations: Lead with CES star schema and Expocad pipeline progress; keep blocked report areas and exhibitor follow-up clear. If you have a concrete next weekly or QA session time, add it under Next sync.

Gaps: No CTA client Slack channel in Supabase, so no Slack thread context for last week. No transcript in the last 7 days; consider adding a line that the last joint sync was Mar 6 and any highlights you have from async or Slack. Add any specific meeting dates (e.g. next Brainforge x CTA weekly, QA session) if you have them. Exhibitor data follow-up and 3-year backfill are in Backlog; confirm with Awaish/Ashwini whether to call out in client comms.

Summary

We moved CES modeling toward a star-schema foundation (in testing), shipped the CES open-questions doc to you, and advanced Expocad ingestion and staging in Snowflake. This week we’ll focus on finishing CES star-schema QA and merge, identity stitching, and the Expocad pipeline (ingest, staging, identity resolution). A few CES report areas (exhibitor, member attendance, executive club/LIT, conferences) remain blocked until we confirm data availability; we’ll keep that list in front of you.

Last week’s achievements

  • CES and Snowflake
    • CES star-schema work is in testing; dimension/fact split and aggregations are being validated.
    • Documented CES model open questions (where we can’t build yet or need data) and sent to the client.
    • Pre-audit report queries (parallel PR) in progress for semantic-layer alignment.
    • Media report model completed and in the books.
  • Expocad
    • Ingest from S3 into Snowflake and staging models for Expocad tables are in PR review.
    • Config seed from S3 into CTA database in PR review.
    • Identity resolution and dimensional modelling for Expocad (identity-stitched) are in the backlog and queued.
  • Data platform and integrations
    • re:Members Data Share V2: PR to switch references is ready; merge planned with a quick QA pass.
    • data_governance ingestion from S3 into Snowflake in progress.
    • re:Members source DB rename in dbt in PR review.
  • Identity and CES
    • Identity stitching in Engagement Core and finalize-identity-stitching tickets are in cycle/backlog; sequencing with CES star schema and Expocad.
    • Backfill 3-year CES data load for QA tracked as a separate deliverable after current pipeline scope.

This week’s focus

  • CES
    • Complete CES star-schema QA and move to marts; then continue star-schema build-out as the under-the-hood structure for aggregations.
    • Use any scheduled QA working session for first-pass validation (Snowflake vs. audit report) and sync on mismatches or logic tweaks.
    • Fortune 500 seed (per year, present_at_ces) and industry/media-by-department view for async QA remain in scope when bandwidth allows.
  • Expocad
    • Merge and land Expocad ingest, staging, and config-seed PRs; then advance identity resolution and dimensional modelling for Expocad.
  • Identity stitching
    • Finalize identity stitching for CTA CES data and Engagement Core; align with CES and re:Members usage.
  • Blocked report areas
    • Keep the list of CES report areas we can’t complete yet (exhibitor, member attendance, executive club/LIT, conferences) and data needs in front of you; follow up on exhibitor data availability as agreed.
  • Cortex
    • Continue Cortex setup and testing against CES views once eligibility and access are confirmed.

Blockers

  • CES reports (exhibitor, member attendance, executive club/LIT, conferences): We still can’t build these report models until we have the right source data or confirmation where it lives. We’ll keep the short note on what’s missing and what we need from your side updated and will follow up on exhibitor data specifically.
  • Cortex: Account-owner verification and eligibility confirmation remain an external dependency; we’ll proceed with setup and testing as access allows.

Action items

OwnerActionDue
BrainforgeComplete CES star-schema QA, merge to marts, and continue star-schema buildThis week
BrainforgeMerge Expocad ingest, staging, and config-seed PRs; advance identity/dimensional workThis week
BrainforgeKeep CES blocked-areas note updated and follow up on exhibitor dataThis week
CTA / KyleShare industry and media by department query/logic for async QA when readyWhen ready
BothAttend QA working session (Snowflake vs. audit report) if scheduledPer calendar

Questions or discussion topics

  • Once you’ve had a look at the blocked-areas note: preferred order for unblocking (e.g. exhibitor vs. member vs. conferences)?
  • Any other report slices you want in the next QA session?

Next sync

  • Recurring Brainforge x CTA weekly; QA working session as agreed when on the calendar. Add specific date/time in Slack block when you have it.

Graph View