B2BEA.org Capability Map v5

Source of record: RedKey Supabase Studio artifact.

• Project: B2BEA.org Rebuild
• Project ID: a820dd0c-6cef-4133-bfbd-d802fd806e44
• Artifact: capability-map
• Artifact ID: c889a1fe-c3ce-4b0d-873c-af4e0ec8dfe4
• Version: 5
• Status: draft
• Updated: 2026-05-06T20:00:09.332+00:00

This capability map is derived from the reverse-engineering pass over the current B2BEA.org repo. It is now a V1 production-scope catalog: production-ready capability areas are included in V1 unless explicitly excluded.

Capability names use VerbObject style so they can later become permissions, service methods, API operations, QA scenarios, and UI actions.

• current: Evidence exists in the current repo.
• partial: Some evidence exists, but the capability is incomplete or indirectly implemented.
• planned: Target capability implied by the rebuild/surface model but not present as a first-class current workflow.
• candidate: Possible capability to review before committing to target scope.

• Current mapped capabilities: 161
• V1 production capability target: 260 capabilities
• Public Site: 25 capabilities
• Auth / Account Security: 13 capabilities
• Individual Member Dashboard + Profile: 21 capabilities
• B2BEA Admin: 59 capabilities
• Vendor Management Portal: 18 capabilities
• Practitioner Company Workspace: 18 capabilities
• Cross-cutting system capabilities: 7 capabilities
• Additional V1 production capabilities: 99 capabilities

V1 should be production-ready across the site, not a thin MVP with obvious operational gaps deferred to a later phase.

The only intentionally light area is internal core-site administration. Core site changes are handled by a small trusted team: Brett, Sarah, and Justin. V1 does not need granular internal admin privilege tiers or complex approval chains for that team.

Production controls still matter where changes affect public content, external users, self-service portals, entitlements, payments, learning access, surveys, jobs, vendor data, company workspaces, and reporting.

B2BEA needs two production publishing paths:

| Path | Use When | V1 Controls | |---|---|---| | Custom HTML import | A landing page or resource needs a custom look beyond standard templates. | Owner, status, preview, publish, rollback/archive, analytics hooks, SEO metadata. | | Sanity standard page creation | A standard site page should use structured content and reusable page templates. | Template selection, required fields, preview, publish/schedule, archive, SEO metadata. |

Every V1 capability should define:

• Who owns the record or content.
• Required lifecycle states.
• Required fields and validation.
• Public/private visibility rules.
• Admin, vendor, company, member, and anonymous access behavior.
• Notification side effects.
• Audit/event logging for material public changes.
• Empty, loading, error, and success states.
• Acceptance criteria that can become QA checks.

For Brett, Sarah, and Justin, permissions can stay simple. For members, vendors, practitioner companies, entitlements, and public publishing, authorization and lifecycle rules need to be explicit and enforced.

| ID | Topic | Decision | |---|---|---| | DEC-001 | Public practitioner company profiles | Exclude from V1. Keep vendor public profiles; practitioner companies get private workspace only. | | DEC-002 | Company-created jobs | Require B2BEA admin review before public publishing in V1. | | DEC-003 | Sanity versus Supabase source of truth | Sanity owns editorial/public content. B2BEA Supabase owns application and operational data, including people, company, vendor, membership, course, survey, job, event, analytics, and notification records. | | DEC-004 | Notifications | V1 is email-first with an internal notification event log. In-app notifications are designed for later unless a surface explicitly needs them. | | DEC-005 | CRM source of truth | HubSpot is the primary CRM for leads, pipeline, sales activity, and renewals. B2BEA Supabase owns website profiles and operational entities. | | DEC-006 | Vendor and company analytics exports | V1 allows bounded own-account exports only. No raw platform-wide data, cross-account comparisons, or sensitive user-level data unless explicitly consented and permitted. |

These groups are V1 scope unless removed during spec review.

| Group | Count | Examples | |---|---:|---| | Surveys and assessments | 19 | AdminCreateSurvey, AdminPublishSurvey, PublicTakeSurvey, MemberTakeSurvey, CompanyAssignSurvey, AdminDisplaySurveyData, AdminExportSurveyResponses | | Forms and intake | 9 | AdminCreateForm, PublicSubmitForm, VendorSubmitForm, AdminReviewFormSubmission, AdminExportFormSubmissions | | Events and sponsorship | 11 | AdminCreateEvent, AdminManageEventSponsors, MemberRegisterForEvent, VendorSponsorEvent, AdminExportEventRegistrations | | Vendor commercial workflow | 12 | VendorPurchaseMembership, VendorManageBilling, VendorInviteTeamMember, VendorViewLeads, AdminCreateVendorInvoice | | Editorial workflow | 13 | AdminCreateArticle, AdminScheduleArticle, AdminReviewVendorContent, AdminManageEditorialCalendar, AdminManageRedirects | | Academy and certification | 11 | AdminCreateCertification, AdminIssueCertificate, MemberViewCertificate, AdminCreateQuiz, CompanyAssignLearningPath | | Notifications | 8 | SystemSendEmailNotification, SystemSendInAppNotification, SystemNotifySurveyAssigned, UserManageNotificationPreferences | | Reporting and anal

Purpose: Browse, learn, discover, search, convert, and view public people/company/vendor/content pages.

| Capability | Status | Notes | |---|---:|---| | PublicSearchSite | current | Global modal search and page-level search/filter patterns exist. | | PublicFilterVendorDirectory | current | Filters by vendor type/category/search term. | | PublicFilterPeopleDirectory | current | People directory includes public browsing/filtering behavior. | | PublicFilterCareerJobs | current | Public jobs list has search/filter behavior. | | PublicFilterCourses | current | Course catalog filters and enrollment badges are client-side. | | PublicFilterResources | current | Resource/report/guide discovery patterns exist but should be unified. |

| Capability | Status | Notes | |---|---:|---| | PublicViewArticle | current | Includes page-view tracking. | | PublicViewGuide | current | Supports vendor attribution and gated downloads. | | PublicViewReport | current | Supports vendor attribution and gated downloads. | | PublicDownloadResource | current | Current pages record resource_downloads in several places. | | PublicGateResourceByAccount | current | Anonymous users see signup/login CTA. | | PublicGateResourceByMembership | current | Pro-gated content checks membership client-side. | | PublicViewTopicHub | current | Topic/category hubs exist and need target model consolidation. | | PublicViewConcept | current | Concept detail pages exist. |