feat(org-lens): add foundations and projects section to org overview

[ahmedomosanya]

WIP / Draft. Adds the Foundations and Projects section to /org/overview. Stacks on top of PR #646 (feat/CD-3507-org-lens-shell); merge target is the feature branch, not main.

Ticket: LFXV2-1680

Stacked on: #646

Summary

• New section under /org/overview (mounted via @defer (on viewport) with a 4-tile skeleton placeholder):
  • 4-tile stat strip: Foundations (per-tier breakdown) · Projects (Leading / Contributing / Participating / Silent) · Governance Roles (board + committee) · Meetings This Week (board / technical / marketing / working group / other).
  • Foundations table with one row per foundation the org touches, sorted member tier-ranked → non-member by LF project count → an Outside-LF umbrella row last. Each row carries a tier-ribbon subtitle, Org Role, Voting Status, Governance Participation, plus a chevron to expand inline-detail per-project rows (sorted by commits desc).
• New API: GET /api/orgs/:accountId/lens/foundations-and-projects (single LEFT JOIN against the ORG_LENS_FOUNDATIONS_AND_PROJECTS rollup × ORG_LENS_FOUNDATION_PROJECTS_DETAIL per-project detail). Empty-org case returns 200 with an empty rows envelope, never 404.
• Wire-boundary normalisation: dbt's __outside_lf__ sentinel becomes the kebab-case outside-lf slug before it reaches testids / telemetry.
• Shared interfaces added for the row, project, stat-strip, and response shapes.
• MembershipTierClass expanded from the prior 10-class union to the canonical 13-class ladder (Founding, Strategic, End User, Contributor added; Sponsor removed; Steering demoted to rank 6) with the rank order documented in JSDoc.

Important — temporary dev-schema bridge

organization.service.ts (the existing ORG_LENS_ACCOUNT_CONTEXT query) and the new OrgLensFoundationsService both read from ANALYTICS_DEV.LF_AOPEYEMI_PLATINUM_LFX_ONE rather than ANALYTICS.PLATINUM_LFX_ONE, because the upstream dbt PR that promotes the ORG_LENS_FOUNDATIONS_AND_PROJECTS / ORG_LENS_FOUNDATION_PROJECTS_DETAIL rollups (and the 13-class tier ladder) into prod is still in flight. Both qualifiers MUST flip back to ANALYTICS.PLATINUM_LFX_ONE before the parent PR (#646) merges to main. Tracked in this PR so it can't get lost.

Out of scope (intentionally)

• Slug-aware Memberships drilldown — row body click currently routes to /org/memberships (placeholder) without a slug; restore the slug arg + register org/memberships/:foundationSlug once the detail page lands.
• Slug-aware per-project drilldown — LF project rows route to /org/projects (no slug, no ProjectContext mutation, no lens switch) until the slug-aware destination ships.
• Reverting the dev-schema qualifier (above) — done in the follow-up commit once the dbt PR merges.

Test plan

• /org/overview mounts the new section after the involvement carousel and renders the 4 stat tiles with non-zero counts for a Platinum / Premier org (Toyota, IBM family).
• Switching the active org via the org selector re-fetches once, clears expansion state, and re-emits the overview_view Plausible event for the new org id.
• Foundations table sort order: member rows first (by tier rank then name), then non-member LF rows (by project_count_lf desc then name), then the Outside-LF umbrella row.
• Chevron expands the inline-detail project rows (sorted by commits desc); collapsing leaves no orphan UI; switching org closes all expanded rows.
• LF project row click navigates to /org/projects and emits mfp_project_row_click. Non-LF rows under Outside-LF are no-ops (no nav, no event).
• Outside-LF row has no Org Role / Voting Status / Governance Participation badges (em-dash), is not keyboard-activatable, and renders the outside-lf testid slug (never the __outside_lf__ sentinel).
• Empty-org case (no foundation involvement) renders the empty caption — no error toast, no 404.
• Error path (force a 5xx) renders the retry affordance; clicking retry re-issues the request.
• yarn build, yarn check-types, yarn lint:check, yarn format:check all pass (pre-push build already green).
• Manual a11y pass on the chevron (Enter / Space toggle, focus return, aria-label flips between Expand / Collapse).

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 656a1e31-3161-42a3-8bb5-b03c144042a4

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch feat/LFXV2-1680-foundations-and-projects

Tip

💬 Introducing Slack Agent: The best way for teams to turn conversations into code.

Slack Agent is built on CodeRabbit's deep understanding of your code, so your team can collaborate across the entire SDLC without losing context.

• Generate code and open pull requests
• Plan features and break down work
• Investigate incidents and troubleshoot customer tickets together
• Automate recurring tasks and respond to alerts with triggers
• Summarize progress and report instantly

Built for teams:

• Shared memory across your entire org—no repeating context
• Per-thread sandboxes to safely plan and execute work
• Governance built-in—scoped access, auditability, and budget controls

One agent for your entire SDLC. Right inside Slack.

👉 Get started

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[Copilot]

Pull request overview

Adds the Foundations and Projects section to the Org Lens overview page (/org/overview), backed by a new BFF endpoint that joins two pre-aggregated dbt rollups in Snowflake. The shared MembershipTierClass union is widened from 10 to 13 canonical tier classes (Sponsor removed; Founding/Strategic/End User/Contributor added; Steering demoted). Both Snowflake reads are temporarily wired to a developer-scoped dev schema (ANALYTICS_DEV.LF_AOPEYEMI_PLATINUM_LFX_ONE) and must be flipped back to ANALYTICS.PLATINUM_LFX_ONE before the parent feature branch merges to main.

Changes:

• New API GET /api/orgs/:accountId/lens/foundations-and-projects with controller + service + dedicated /api/orgs router.
• New Angular section component (stat strip, foundations table with chevron expansion to per-project inline detail) deferred on viewport, plus tier/logo helpers and a client OrgLensFoundationsService.
• Shared interface additions for the new response shape and a breaking widening of MembershipTierClass to the 13-class ladder.

Reviewed changes

Copilot reviewed 19 out of 19 changed files in this pull request and generated 12 comments.

Show a summary per file

File	Description
packages/shared/src/interfaces/org-lens.interface.ts	Widens MembershipTierClass; adds row/project/stat-strip/response interfaces
apps/lfx-one/src/server/services/organization.service.ts	Switches ORG_LENS_ACCOUNT_CONTEXT to dev schema
apps/lfx-one/src/server/services/org-lens-foundations.service.ts	New service: joined Snowflake query, sentinel slug normalization, stat-strip aggregation
apps/lfx-one/src/server/controllers/org-lens-foundations.controller.ts	New controller with accountId regex validation
apps/lfx-one/src/server/routes/orgs.route.ts	New router for /api/orgs/:accountId/lens/...
apps/lfx-one/src/server/server.ts	Mounts the new /api/orgs router
apps/lfx-one/src/app/shared/services/org-lens-foundations.service.ts	Client HTTP proxy for the new endpoint
apps/lfx-one/src/app/modules/dashboards/org/org-overview/org-overview.component.{ts,html}	Adds deferred-on-viewport section with skeleton placeholder
.../org-overview-foundations-and-projects.component.{ts,html,scss}	Parent section: state stream, retry, expansion, telemetry
.../components/foundations-stat-strip.component.{ts,html}	4-tile stat strip with detail-line aggregation
.../components/foundation-row.component.{ts,html,scss}	Per-foundation row with badges, chevron, navigation
.../helpers/{tier-ribbon,foundation-logo}.helper.ts	Tier-pill palette and deterministic logo-square fallback

Comments suppressed due to low confidence (4)

apps/lfx-one/src/server/services/org-lens-foundations.service.ts:210

• The Outside-LF sentinel is normalized to outside-lf only on foundationSlug; foundationId (__outside_lf__) is still used as the React-style key in @for ... track row.foundationId in the parent template, as the expansion-state map key, and as the Map key in rowsByFoundation. The PR description states the __outside_lf__ sentinel "MUST NOT leak into testids, telemetry payloads, or future routing keys" — but it currently leaks into the mfp_caret_toggle / mfp_row_click Plausible payloads (which receive foundationName, but the parent's toggleExpansion(row.foundationId) and the testid fallback row.foundationSlug || row.foundationId would still emit it for any non-outside-lf row whose dbt slug is null). Recommend normalizing both foundationId and foundationSlug to outside-lf for the umbrella row, or computing the testid/expansion key from the already-normalized foundationSlug.

        // Normalize the Outside-LF umbrella row's slug at the wire boundary.
        // dbt emits FOUNDATION_ID='__outside_lf__' and FOUNDATION_SLUG also
        // equal to '__outside_lf__' (literal sentinel string, NOT null) for
        // the umbrella row. The wire value MUST be the kebab-case slug
        // 'outside-lf'. We force this for any row_kind='outside_lf'
        // regardless of what dbt sends — the sentinel is an internal
        // implementation detail and MUST NOT leak into testids, telemetry
        // payloads, or future routing keys.
        const foundationSlug =
          raw.ROW_KIND === 'outside_lf' ? 'outside-lf' : (raw.FOUNDATION_SLUG ?? raw.FOUNDATION_ID);
        row = {
          foundationId: raw.FOUNDATION_ID,
          foundationSlug,
          foundationName: raw.FOUNDATION_NAME,
          foundationLogoUrl: raw.FOUNDATION_LOGO_URL,
          rowKind: raw.ROW_KIND,
          membershipTierClass: raw.MEMBERSHIP_TIER_CLASS,
          membershipTierDisplayName: raw.MEMBERSHIP_TIER_DISPLAY_NAME,
          projectCount: raw.PROJECT_COUNT_LF ?? 0,
          badges: {
            orgRole: raw.ORG_ROLE,
            votingStatus: raw.VOTING_STATUS,
            // Outside LF emits NULL bucket → render em-dash.
            governanceParticipation: raw.GOVERNANCE_PARTICIPATION_BUCKET ?? '—',
            governanceAttendancePct: raw.GOVERNANCE_ATTENDANCE_PCT,
          },
          projects: [],
        };
        rowsByFoundation.set(raw.FOUNDATION_ID, row);

apps/lfx-one/src/server/services/org-lens-foundations.service.ts:231

• projectCount is set to raw.PROJECT_COUNT_LF ?? 0 from the upstream rollup, while the projects array is populated from the LEFT JOIN and may include projects that fall outside the PROJECT_COUNT_LF definition (e.g. non-LF projects under the Outside-LF umbrella, or projects gated out by PROJECT_INFLUENCE_MAX_BUCKET being null on line 231). As a result, projectCount may not match projects.length, and projectsInvolvedText ("{count} project(s) involved") on the row can display a different number than the inline-detail caption ("Projects Involved ({{ row.projects.length }})"). Consider either deriving projectCount from projects.length server-side or documenting the intentional discrepancy.

          projectCount: raw.PROJECT_COUNT_LF ?? 0,
          badges: {
            orgRole: raw.ORG_ROLE,
            votingStatus: raw.VOTING_STATUS,
            // Outside LF emits NULL bucket → render em-dash.
            governanceParticipation: raw.GOVERNANCE_PARTICIPATION_BUCKET ?? '—',
            governanceAttendancePct: raw.GOVERNANCE_ATTENDANCE_PCT,
          },
          projects: [],
        };
        rowsByFoundation.set(raw.FOUNDATION_ID, row);

        // Foundations tile: count member foundations only.
        if (row.rowKind === 'member' && row.membershipTierClass) {
          foundationsTotal += 1;
          tierBreakdown[row.membershipTierClass] = (tierBreakdown[row.membershipTierClass] ?? 0) + 1;
        }

        // Governance + meetings tiles: LF foundations only.
        // Outside-LF emits zero from dbt, but skip to be explicit.
        if (row.rowKind !== 'outside_lf') {
          boardMembers += raw.BOARD_MEMBER_SEAT_COUNT ?? 0;
          committeeMembers += raw.COMMITTEE_MEMBER_SEAT_COUNT ?? 0;
          mtwBoard += raw.MEETINGS_THIS_WEEK_BOARD ?? 0;
          mtwTechnical += raw.MEETINGS_THIS_WEEK_TECHNICAL ?? 0;
          mtwMarketing += raw.MEETINGS_THIS_WEEK_MARKETING ?? 0;
          mtwWorkingGroup += raw.MEETINGS_THIS_WEEK_WORKING_GROUP ?? 0;
          mtwOther += raw.MEETINGS_THIS_WEEK_OTHER ?? 0;
        }
      }

      if (raw.PROJECT_ID && raw.PROJECT_INFLUENCE_MAX_BUCKET) {

apps/lfx-one/src/server/services/org-lens-foundations.service.ts:261

• Project rows are skipped silently if PROJECT_INFLUENCE_MAX_BUCKET is null even when PROJECT_ID is non-null — this drops them from both the inline-detail table and the projects-tile counts with no log. If dbt ever emits a project row before the influence bucket is computed (or with an unmapped value), the user sees a foundation row claiming N projects involved with fewer rendered. Either default the bucket to 'Silent' in the SQL/CASE or log a warning when this branch is hit.

      if (raw.PROJECT_ID && raw.PROJECT_INFLUENCE_MAX_BUCKET) {
        const project: OrgLensFoundationProject = {
          projectId: raw.PROJECT_ID,
          projectSlug: raw.PROJECT_SLUG ?? raw.PROJECT_ID,
          projectName: raw.PROJECT_NAME ?? raw.PROJECT_ID,
          isLfProject: raw.PROJECT_IS_LF_PROJECT === true,
          influence: raw.PROJECT_INFLUENCE_MAX_BUCKET,
          maintainers: raw.PROJECT_MAINTAINERS_COUNT ?? 0,
          contributors: raw.PROJECT_CONTRIBUTORS_COUNT ?? 0,
          collaborators: raw.PROJECT_COLLABORATORS_COUNT ?? 0,
          commits: raw.PROJECT_COMMITS_COUNT ?? 0,
        };
        row.projects.push(project);

        // Projects tile: count every project on every row (including
        // Outside-LF) per the influence bucket.
        switch (project.influence) {
          case 'Leading':
            projectsLeading += 1;
            break;
          case 'Contributing':
            projectsContributing += 1;
            break;
          case 'Participating':
            projectsParticipating += 1;
            break;
          case 'Silent':
            projectsSilent += 1;
            break;
        }
      }

apps/lfx-one/src/server/services/org-lens-foundations.service.ts:301

• When result.rows.length === 0 the service returns an empty response with accountName: ''. The FE component then uses companyName() which falls back to the AccountContext, so the UI is fine — but consumers of the API directly would see a blank account name where the org actually exists (just has no foundation involvement). Consider either fetching/echoing the account name from the existing ORG_LENS_ACCOUNT_CONTEXT table for the empty path, or documenting on the response interface that accountName is empty string for the zero-engagement case.

  private emptyResponse(accountId: string): OrgLensFoundationsAndProjectsResponse {
    return {
      accountId,
      accountName: '',
      statStrip: {
        foundations: { total: 0, breakdown: {} },
        projects: { total: 0, leading: 0, contributing: 0, participating: 0, silent: 0 },
        governanceRoles: { total: 0, boardMembers: 0, committeeMembers: 0 },
        meetingsThisWeek: { total: 0, board: 0, technical: 0, marketing: 0, workingGroup: 0, other: 0 },
      },
      rows: [],
    };
  }

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.