ce — Public API surface

Types & interfaces

interface ActivitySearchFilters

file: src/cores/ce/hooks/useActivitySearch.ts:23
kind: interface
core: ce
spec: CE-04
summary: Filter criteria for searching activities: free-text query, activity types, subject type,creator, and a date range.
score: 3

type AdminCardUpdate

file: src/cores/ce/hooks/useMemberCards.ts:56
kind: type
core: ce
spec: (none)
summary: Fields an admin may update on any card.
score: 2

interface ApproveIntakeArgs

file: src/cores/ce/hooks/useIntakeAgent.ts:108
kind: interface
core: ce
spec: (none)
summary: Args the approve flow re-passes to execute_writes (mirror of the Deno ExecuteWritesDeps).
score: 2

type CampaignFormData

file: src/cores/ce/components/campaigns/CampaignFormDialog.tsx:42
kind: type
core: ce
spec: CE-09
summary: Validated shape of the campaign create/edit form, inferred from the Zod schema covering name,type, status, date window, budget, goals, and UTM attribution fields.
score: 3

interface CardPreviewData

file: src/cores/ce/components/connect/CardPreview.tsx:18
kind: interface
core: ce
spec: (none)
summary: The subset of card fields the preview renders.
score: 2

interface CEActivityItem

file: src/cores/ce/hooks/useCERecentActivity.ts:18
kind: interface
core: ce
spec: none
summary: A single recent-activity feed item for the CE dashboard, carrying its type, icon,title/description, timestamp, and a navigation route.
score: 3

interface CEDashboardMetrics

file: src/cores/ce/hooks/useCEDashboardMetrics.ts:29
kind: interface
core: ce
spec: none
summary: Aggregated headline metrics for the CE dashboard — total contacts, active leads, monthly calls,and conversion rate — each paired with its trend.
score: 3

type ConsentChannelType

file: src/cores/ce/hooks/useConsentEvidence.ts:25
kind: type
core: ce
spec: CE-16
summary: Communication channel a consent record applies to (email, SMS, phone, or all channels).
score: 3

type ConsentEvidenceAction

file: src/cores/ce/hooks/useConsentEvidence.ts:19
kind: type
core: ce
spec: CE-16
summary: Action recorded by a consent-evidence event: consent granted, withdrawn, or reaffirmed.
score: 3

type ConsentEvidenceMethod

file: src/cores/ce/hooks/useConsentEvidence.ts:32
kind: type
core: ce
spec: CE-16
summary: Method by which consent was captured (web form, SMS keyword, email link, verbal, written, API,or import).
score: 3

interface ConsentEvidenceRecord

file: src/cores/ce/hooks/useConsentEvidence.ts:40
kind: interface
core: ce
spec: CE-16
summary: A persisted, append-only consent-evidence row capturing who consented, the action and method,optional consent text, and the captured IP/user-agent metadata.
score: 3

interface ContactTagAssignmentFieldProps

file: src/cores/ce/components/contacts/ContactTagAssignmentField.tsx:23
kind: interface
core: ce
spec: CE-61
summary: Props for : the target and a flagcontrolling whether tags may be assigned or removed.
score: 3

interface ContactTagBadgeProps

file: src/cores/ce/components/contacts/ContactTagBadge.tsx:19
kind: interface
core: ce
spec: CE-61
summary: Props for : the tag to render plus optional removable/size/classNamecontrols and an callback.
score: 3

interface ContactTagDialogProps

file: src/cores/ce/components/settings/ContactTagDialog.tsx:45
kind: interface
core: ce
spec: CE-61
summary: Props for : open state, the tag being edited (or null when creating), an handler, a submitting flag, and the default sort order for new tags.
score: 3

type ContractRenewalAction

file: src/cores/ce/hooks/useContractRenewalLogMutation.ts:22
kind: type
core: ce
spec: (none)
summary: Action values aligned with the CHECKconstraint. Any other value will be rejected at the database level.
score: 2

interface CreateLeadConversionInput

file: src/cores/ce/hooks/useLeadConversions.ts:19
kind: interface
core: ce
spec: (none)
summary: Input for creating a lead conversion audit record.
score: 2

interface CreateScreeningInput

file: src/cores/ce/hooks/useCreateScreening.ts:26
kind: interface
core: ce
spec: (none)
summary: Input for creating a screening (result + attempt).
score: 2

type DbMatchCandidate

file: src/cores/ce/hooks/useMatchCandidates.ts:19
kind: type
core: ce
spec: (none)
summary: Row shape of ce_match_candidates (the probabilistic review queue).
score: 2

type DbMergeLog

file: src/cores/ce/hooks/useContactMerge.ts:16
kind: type
core: ce
spec: (none)
summary: Row shape of ce_merge_log (merge audit + undo source).
score: 2

interface DocumentAdapterError

file: src/cores/ce/lib/document-storage-adapter.ts:35
kind: interface
core: ce
spec: (none)
summary: Normalized adapter error contract.
score: 2

interface EmailMatchOptions

file: src/cores/ce/utils/email-matching.ts:34
kind: interface
core: ce
spec: (none)
summary: Options for email matching
score: 1

interface EmailMatchResult

file: src/cores/ce/utils/email-matching.ts:24
kind: interface
core: ce
spec: (none)
summary: Result of email-to-entity matching
score: 2

type EmailMatchType

file: src/cores/ce/utils/email-matching.ts:21
kind: type
core: ce
spec: (none)
summary: Match types in priority order
score: 1

interface EmailMessageWithMeta

file: src/cores/ce/hooks/useEmailMessages.ts:37
kind: interface
core: ce
spec: (none)
summary: Email message with computed fields for display
score: 2

interface ExtractionSuggestions

file: src/cores/ce/hooks/useContactDocumentExtraction.ts:23
kind: interface
core: ce
spec: CE-59
summary: AI-extracted field suggestions from a contact document — insurance carrier/member/group, PCP,diagnosis codes, and medication names — each optional when not detected.
score: 3

interface FetchContactHistoryArgs

file: src/cores/ce/history/adapters/index.ts:36
kind: interface
core: ce
spec: CE-60
summary: Arguments for : org/contact scope, page size, optional filters andcursor, redaction policy, and the CE-63 stage-fallback flag.
score: 3

interface FieldConflict

file: src/cores/ce/lib/mergeSurvivorship.ts:74
kind: interface
core: ce
spec: (none)
summary: A field where the two contacts disagree, with the survivorship default.
score: 2

interface FormattedPublishError

file: src/cores/ce/wizards/sequences/utils/parsePublishError.ts:251
kind: interface
core: ce
spec: (none)
summary: User-facing toast message composed from a structured error detail.
score: 2

interface IdentityMatchedOn

file: src/cores/ce/hooks/useIdentityResolution.ts:25
kind: interface
core: ce
spec: (none)
summary: Which fields matched and how (drives the matched-on chips).
score: 2

type IdentityMatchTier

file: src/cores/ce/hooks/useIdentityResolution.ts:22
kind: type
core: ce
spec: (none)
summary: Match tier: auto (deterministic-equivalent) or review (queue-bound).
score: 2

interface IdentityResolutionMatch

file: src/cores/ce/hooks/useIdentityResolution.ts:34
kind: interface
core: ce
spec: (none)
summary: One ranked match returned by ce_resolve_identity.
score: 2

interface IdentityResolutionPayload

file: src/cores/ce/hooks/useIdentityResolution.ts:47
kind: interface
core: ce
spec: (none)
summary: Contact-shaped payload resolved against the org’s existing contacts.
score: 2

interface IntakeArtifact

file: src/cores/ce/hooks/intake-agent-types.ts:35
kind: interface
core: ce
spec: (none)
summary: The artifact header + latest version body the recommendation card renders.
score: 2

interface IntakeProposal

file: src/cores/ce/hooks/intake-agent-types.ts:12
kind: interface
core: ce
spec: (none)
summary: The structured proposed appointment the edge fn returns + the UI re-passes to execute_writes.
score: 2

interface IntakeRunStartResult

file: src/cores/ce/hooks/intake-agent-types.ts:22
kind: interface
core: ce
spec: (none)
summary: The widened result (additive over the Stage-1 ).
score: 2

interface KeywordMatchResult

file: src/cores/ce/lib/crisisKeywordMatcher.ts:44
kind: interface
core: ce
spec: (none)
summary: Result of a single match attempt.
score: 2

type LeadAssignmentAction

file: src/cores/ce/utils/leadAssignment.ts:10
kind: type
core: ce
spec: (none)
summary: What happened to a lead’s assignee as a result of an assign mutation.
score: 2

type LeadStageTransitionKind

file: src/cores/ce/lib/classifyLeadStageTransition.ts:12
kind: type
core: ce
spec: (none)
summary: CE-63: Classify a destination pipeline stage to decide which transitiondialog (if any) the kanban / stage-selector should open before committingthe move.Classification is driven by (preferred)and . We deliberately avoid switching on because the spec calls the buckets out by behavior, not by stage_typeenum value.
score: 2

interface MappingPreviewRow

file: src/cores/ce/components/contacts/import-utils/mappingPreview.ts:14
kind: interface
core: ce
spec: none
summary: Preview row pairing a source CSV column with its mapped database field and the sample valuesobserved for that column.
score: 3

type MatchCandidateStatus

file: src/cores/ce/hooks/useMatchCandidates.ts:22
kind: type
core: ce
spec: (none)
summary: Candidate lifecycle: pending → linked | dismissed | merged (never deleted).
score: 2

interface MatchCandidateWithContacts

file: src/cores/ce/hooks/useMatchCandidates.ts:25
kind: interface
core: ce
spec: (none)
summary: Candidate row joined with both contacts’ display fields for the compare drawer.
score: 2

type MergeableField

file: src/cores/ce/lib/mergeSurvivorship.ts:43
kind: type
core: ce
spec: (none)
summary: A column the merge dialog may decide on (mirrors the RPC whitelist).
score: 2

interface MergeContactsArgs

file: src/cores/ce/hooks/useContactMerge.ts:19
kind: interface
core: ce
spec: (none)
summary: Inputs for the ce_merge_contacts mutation.
score: 2

interface MergeContext

file: src/cores/ce/utils/merge-fields.ts:24
kind: interface
core: ce
spec: (none)
summary: Merge field context with all available data sources
score: 2

interface MergeFieldDefinition

file: src/cores/ce/utils/merge-fields.ts:43
kind: interface
core: ce
spec: (none)
summary: Merge field definition
score: 1

interface MergeFieldGroup

file: src/cores/ce/utils/merge-fields.ts:53
kind: interface
core: ce
spec: (none)
summary: Merge field group for UI picker
score: 2

type MergePartner

file: src/cores/ce/utils/merge-fields.ts:16
kind: type
core: ce
spec: (none)
summary: CE-66: Partner subset for merge context. / are sourcedfrom the resolved primary partner-contact row (not the deprecated / columns). Callers must resolve via before populating this shape.
score: 2

type MergeSide

file: src/cores/ce/lib/mergeSurvivorship.ts:71
kind: type
core: ce
spec: (none)
summary: Which record’s value wins a conflicting field.
score: 2

type MyCardInput

file: src/cores/ce/hooks/useMyCard.ts:28
kind: type
core: ce
spec: (none)
summary: Fields a member can edit on their own card (slug/audit/org/user are managed).
score: 2

interface OrgCalendarCapability

file: src/cores/ce/lib/orgCalendarCapability.ts:17
kind: interface
core: ce
spec: (none)
summary: Result of evaluating org-calendar (DWD) capability for a user.
score: 2

interface PhiPattern

file: src/cores/ce/utils/sms-opt-out.ts:158
kind: interface
core: ce
spec: (none)
summary: PHI Detection PatternsExtended patterns for comprehensive PHI/PII detectionReference: HIPAA Safe Harbor, IRS Publication 1075
score: 2

interface PipelineTrackInput

file: src/cores/ce/lib/resolveLeadPipelineTrack.ts:13
kind: interface
core: ce
spec: (none)
summary: CE-64: Resolve which pipeline track a lead belongs to based on itsrequested services and the org’s configured tracks.Rules: - Active tracks only. - A track matches if any of the lead’s is listed in the track’s . - Exactly one match → that track. - Zero or multiple matches → the org’s track (typically “General”). If no default exists, returns .
score: 2

type PublishSequenceErrorCategory

file: src/cores/ce/wizards/sequences/utils/parsePublishError.ts:19
kind: type
core: ce
spec: (none)
summary: Error category for RPC failures.Allowed values: ‘auth’, ‘access’, ‘name_required’, ‘name_duplicate’, ‘no_steps’,‘enrollment_criteria_required’, ‘step_invalid_type’, ‘step_name_required’,‘step_delay_negative’, ‘step_missing_content’, ‘template_not_found’, ‘unknown’.
score: 2

interface PublishSequenceErrorDetail

file: src/cores/ce/wizards/sequences/utils/parsePublishError.ts:39
kind: interface
core: ce
spec: (none)
summary: Structured detail parsed from a RPC error.Contains category (one of ), step context when applicable(stepNumber, stepName, stepType), template details if relevant (templateId, templateKind),a user-facing reason, and the original sanitized fallback message.
score: 2

interface RecordConsentEvidenceInput

file: src/cores/ce/hooks/useConsentEvidence.ts:93
kind: interface
core: ce
spec: CE-16
summary: Input for recording a new consent-evidence event: contact, consent channel, action, capturemethod, and optional consent text and user agent.
score: 3

interface RequestedServicesMultiSelectProps

file: src/cores/ce/components/RequestedServicesMultiSelect.tsx:21
kind: interface
core: ce
spec: CE-58
summary: Props for : the selected service values, an handler, and optional label/description/aria/disabled overrides.
score: 3

interface ScheduleOrgMeetingParams

file: src/cores/ce/hooks/useScheduleOrgMeeting.ts:31
kind: interface
core: ce
spec: (none)
summary: Parameters for an org-calendar (DWD) scheduling request.Shaped like the personal-path minus the personal , plus the resolved PF-101 connection id andan optional Google Meet flag. The event lands on the current user’s primarycalendar within the verified org domain (the DWD subject is the user’s email)./ are passed straight to the Google event summary/description —callers must keep these PHI-free per the CE-21 calendar PHI policy.
score: 2

type SegmentConditionFormData

file: src/cores/ce/schemas/segment-criteria.schema.ts:43
kind: type
core: ce
spec: (none)
summary: Inferred type for segment condition
score: 2

type SegmentCriteriaFormData

file: src/cores/ce/schemas/segment-criteria.schema.ts:48
kind: type
core: ce
spec: (none)
summary: Inferred type for segment criteria
score: 2

type SegmentFormData

file: src/cores/ce/components/segments/SegmentFormDialog.tsx:35
kind: type
core: ce
spec: CE-09
summary: Validated shape of the audience-segment create/edit form, inferred from the Zod schema coveringname, description, and active state.
score: 3

interface SequenceListFilters

file: src/cores/ce/hooks/useSequenceList.ts:11
kind: interface
core: ce
spec: (none)
summary: Optional filters for sequence list queries. isActive - When set, filters to active () or inactive () sequences. search - Case-insensitive sequence name search text.
score: 2

type ShareSource

file: src/cores/ce/lib/cardShare.ts:32
kind: type
core: ce
spec: (none)
summary: Fields needed to build share assets: a slug plus the vCard source fields.
score: 2

type SmsMessageIntent

file: src/cores/ce/utils/sms-opt-out.ts:140
kind: type
core: ce
spec: (none)
summary: Determine message intent for routing
score: 2

interface SmsNotificationToastProps

file: src/cores/ce/components/sms/SmsNotificationToast.tsx:16
kind: interface
core: ce
spec: CE-08
summary: Props for the inbound-SMS notification toast: the matched contact name/id (null when unmatched),sender number, message preview, and a view callback.
score: 3

interface TagFilterControlProps

file: src/cores/ce/components/pipeline/TagFilterControl.tsx:22
kind: interface
core: ce
spec: CE-61
summary: Props for : the selected tag ids, the match mode, an callbackemitting both, and an optional className.
score: 3

interface TrackPipelineRowProps

file: src/cores/ce/components/TrackPipelineRow.tsx:30
kind: interface
core: ce
spec: CE-64
summary: Props for : track identity/colour, its stage groups, collapsed state andtoggle handler, the active lead, and a collapsibility flag.
score: 3

interface TrendData

file: src/cores/ce/hooks/useCEDashboardMetrics.ts:17
kind: interface
core: ce
spec: none
summary: Period-over-period trend for a dashboard KPI: direction, magnitude, and a human-readablecomparison label.
score: 3

interface TriageCategoryThreshold

file: src/cores/ce/utils/screeningTriage.ts:35
kind: interface
core: ce
spec: (none)
summary: A descending score threshold mapping to a category.
score: 2

interface TriageFlagPoint

file: src/cores/ce/utils/screeningTriage.ts:29
kind: interface
core: ce
spec: (none)
summary: Points added when a clinical flag is present in the detected flag set.
score: 2

interface TriageLevelOfCareThreshold

file: src/cores/ce/utils/screeningTriage.ts:41
kind: interface
core: ce
spec: (none)
summary: A descending score threshold mapping to a level-of-care code.
score: 2

interface TriageRuleset

file: src/cores/ce/utils/screeningTriage.ts:51
kind: interface
core: ce
spec: (none)
summary: A configurable, versioned triage ruleset. In CE-81 this is resolved perorganization + jurisdiction (PF-96) from ; the default below isthe seeded fallback that reproduces the legacy hardcoded model.
score: 2

interface TriageScoreWeight

file: src/cores/ce/utils/screeningTriage.ts:22
kind: interface
core: ce
spec: (none)
summary: A single scoring rule: when , add .
score: 2

interface TriageTraceEntry

file: src/cores/ce/utils/screeningTriage.ts:130
kind: interface
core: ce
spec: (none)
summary: One entry in the rule trace: a weight or flag rule that fired during scoring.
score: 2

interface UpsertSlaConfigInput

file: src/cores/ce/hooks/useScreeningSlaConfig.ts:90
kind: interface
core: ce
spec: (none)
summary: Input for creating/updating SLA config
score: 2

type Urgency

file: src/cores/ce/lib/urgency.ts:10
kind: type
core: ce
spec: (none)
summary: The four lead-urgency levels in ascending severity, matching the enum.
score: 2

interface UrgencyAccent

file: src/cores/ce/lib/urgency.ts:26
kind: interface
core: ce
spec: (none)
summary: Resolved UI treatment for one urgency level: the short label plus thesemantic-token badge variant, tile border, popover text colour, and icon usedto surface it. is true only for high/critical (the levels calledout on the board); the colour/icon fields are null for low/medium.
score: 2

interface UseActivitiesOptions

file: src/cores/ce/hooks/useActivities.ts:24
kind: interface
core: ce
spec: CE-04
summary: Options for : org scope plus optional subject, activity-type, creator, andpaging filters for the activity list query.
score: 3

interface UseActivitiesResult

file: src/cores/ce/hooks/useActivities.ts:52
kind: interface
core: ce
spec: CE-04
summary: Result of : the activity list, total count, loading/error state, a refetchtrigger, and whether more pages exist.
score: 3

interface UseActivitySearchOptions

file: src/cores/ce/hooks/useActivitySearch.ts:38
kind: interface
core: ce
spec: CE-04
summary: Options for : org scope, the active filters, paging, and an enabledflag.
score: 3

interface UseActivitySearchResult

file: src/cores/ce/hooks/useActivitySearch.ts:52
kind: interface
core: ce
spec: CE-04
summary: Result of : the matched activities, total count, loading/error state, arefetch trigger, and whether more pages exist.
score: 3

interface UseContactsOptions

file: src/cores/ce/hooks/useContacts.ts:14
kind: interface
core: ce
spec: (none)
summary: Filter/pagination options for the contacts list query.
score: 2

interface UseContactsResult

file: src/cores/ce/hooks/useContacts.ts:27
kind: interface
core: ce
spec: (none)
summary: Contacts list query result: rows, total count, and query state.
score: 2

interface UseContactsWithoutLeadsOptions

file: src/cores/ce/hooks/useContactsWithoutLeads.ts:12
kind: interface
core: ce
spec: (none)
summary: Options for the contacts-without-leads picker query.
score: 2

interface UseOrgCalendarCapabilityResult

file: src/cores/ce/hooks/useOrgCalendarCapability.ts:18
kind: interface
core: ce
spec: (none)
summary: Hook result: capability flags plus loading state.
score: 2

type VCardSource

file: src/cores/ce/lib/vcard.ts:53
kind: type
core: ce
spec: (none)
summary: Fields a vCard is built from — a structural subset of a member card.
score: 2

type WidgetPosition

file: src/cores/ce/components/settings/WidgetPositionPreview.tsx:17
kind: type
core: ce
spec: CE-14
summary: Screen corner where the embeddable widget is anchored — one of the four bottom/top, left/rightpositions.
score: 3

Hooks

hook useActiveCrisisAlertSummary

file: src/cores/ce/hooks/useCrisisAlerts.ts:48
kind: hook
core: ce
spec: (none)
summary: Lightweight summary for the queue-header widget.
score: 4

hook useActiveEmailTemplates

file: src/cores/ce/hooks/useEmailTemplates.ts:117
kind: hook
core: ce
spec: (none)
summary: Fetch active templates for compose dialog dropdown
score: 4

hook useActiveLeadCount

file: src/cores/ce/hooks/useActiveLeadCount.ts:33
kind: hook
core: ce
spec: (none)
summary: Hook for managing active lead count.
score: 1

hook useActivities

file: src/cores/ce/hooks/useActivities.ts:68
kind: hook
core: ce
spec: (none)
summary: Returns paginated CE activities with subject/date/type filters and joined timeline metadata.
score: 4

hook useActivitySearch

file: src/cores/ce/hooks/useActivitySearch.ts:101
kind: hook
core: ce
spec: (none)
summary: Provides activity search queries and mutation actions scoped to the current organization.
score: 4

hook useAddQueueMember

file: src/cores/ce/hooks/useAssignmentQueue.ts:82
kind: hook
core: ce
spec: (none)
summary: Provides add queue member queries and mutation actions scoped to the current organization.
score: 4

hook useAdminUpdateCard

file: src/cores/ce/hooks/useMemberCards.ts:61
kind: hook
core: ce
spec: (none)
summary: Admin update of any member’s card (e.g. deactivate). Gated on .
score: 4

hook useAfterHoursHandoverQueue

file: src/cores/ce/hooks/useAfterHoursHandover.ts:21
kind: hook
core: ce
spec: CE-28
summary: Queries after-hours intake arrivals that lack a linked outcome (spec D-04), surfacing screeningattempts that still need handover follow-up for the current org.
returns: A React Query result of unresolved after-hours screening attempts.
score: 5

hook useAllWebFormStats

file: src/cores/ce/hooks/useWebFormSubmissions.ts:176
kind: hook
core: ce
spec: (none)
summary: Hook for managing all web form stats.
score: 1

hook useApproveIntake

file: src/cores/ce/hooks/useIntakeAgent.ts:121
kind: hook
core: ce
spec: (none)
summary: Approve: human verify (draft→verified) then the server-side gate→approve→mint→governed write.
score: 4

hook useAssignmentQueue

file: src/cores/ce/hooks/useAssignmentQueue.ts:37
kind: hook
core: ce
spec: (none)
summary: Provides assignment queue queries and mutation actions scoped to the current organization.
score: 4

hook useAttendeeCheckIn

file: src/cores/ce/hooks/useEventAttendees.ts:49
kind: hook
core: ce
spec: (none)
summary: Attendee check-in mutation
score: 1

hook useAttendeeMutations

file: src/cores/ce/hooks/useEventAttendees.ts:88
kind: hook
core: ce
spec: (none)
summary: Attendee mutations (add, update, remove)
score: 4

hook useAttributeLeadToCampaign

file: src/cores/ce/hooks/useLeadAttribution.ts:85
kind: hook
core: ce
spec: (none)
summary: Hook to attribute a lead to a campaign
score: 4

hook useBulkDismissMatchCandidates

file: src/cores/ce/hooks/useMatchCandidates.ts:123
kind: hook
core: ce
spec: (none)
summary: Bulk-dismisses pending candidates (review-queue toolbar action).
score: 4

hook useBusinessHours

file: src/cores/ce/hooks/useBusinessHours.ts:66
kind: hook
core: ce
spec: CE-28
summary: Resolves the org’s business-hours config into live open/closed state, exposing whether it isopen now, the next opening time, and an predicate for arbitrary timestamps.
returns: The config plus , , and an helper.
score: 5

hook useBusinessHoursConfig

file: src/cores/ce/hooks/useBusinessHours.ts:29
kind: hook
core: ce
spec: CE-28
summary: Loads the org’s intake business-hours configuration from , falling back to asensible default when none is stored.
returns: A React Query result of the org’s business-hours config.
score: 5

hook useCalendarConnections

file: src/cores/ce/hooks/useCalendarConnections.ts:20
kind: hook
core: ce
spec: (none)
summary: Hook for listing and managing the current user’s calendar connections.
score: 1

hook useCalendarEvents

file: src/cores/ce/hooks/useCalendarEvents.ts:18
kind: hook
core: ce
spec: (none)
summary: Hook for querying synced calendar events with optional filters.
score: 1

hook useCallAnalytics

file: src/cores/ce/hooks/useCallAnalytics.ts:119
kind: hook
core: ce
spec: (none)
summary: Hook for fetching call analytics with configurable options
params:
- options — Configuration for date range, filtering, and aggregation
returns: Query result with call analytics metrics and summary
score: 1

hook useCampaignAnalytics

file: src/cores/ce/hooks/useCampaignAnalytics.ts:98
kind: hook
core: ce
spec: (none)
summary: Hook for fetching campaign analytics with computed metrics
score: 1

hook useCampaignDetail

file: src/cores/ce/hooks/useCampaignDetail.ts:20
kind: hook
core: ce
spec: (none)
summary: Fetches one non-deleted campaign by id with organization guard and not-found handling.
score: 4

hook useCampaignList

file: src/cores/ce/hooks/useCampaignList.ts:22
kind: hook
core: ce
spec: (none)
summary: Hook for managing campaign list.
score: 1

hook useCampaignROI

file: src/cores/ce/hooks/useCampaignROI.ts:44
kind: hook
core: ce
spec: (none)
summary: Hook for computing ROI metrics across campaigns
params:
- campaigns — List of campaign metrics
- options — ROI calculation options
score: 1

hook useCaptureLead

file: src/cores/ce/hooks/useCaptureLead.ts:66
kind: hook
core: ce
spec: (none)
summary: In-app capture mutation. Resolves the field contact against existing contactsand persists contact/lead/parked-candidate rows plus the capture audit row.Returns the outcome and the resolved ids. Gated on .
score: 4

hook useCardCaptures

file: src/cores/ce/hooks/useCardCaptures.ts:27
kind: hook
core: ce
spec: (none)
summary: List card captures for the org, or for a single card when is given.Ordered by descending.
score: 4

hook useCEDashboardMetrics

file: src/cores/ce/hooks/useCEDashboardMetrics.ts:184
kind: hook
core: ce
spec: (none)
summary: Provides cedashboard metrics queries and mutation actions scoped to the current organization.
score: 4

hook useCEModuleSettings

file: src/cores/ce/hooks/useCEModuleSettings.ts:15
kind: hook
core: ce
spec: (none)
summary: Hook for managing CE module settings at the organization levelUses context for organizationId - standardized pattern
score: 1

hook useCERecentActivity

file: src/cores/ce/hooks/useCERecentActivity.ts:143
kind: hook
core: ce
spec: (none)
summary: Hook for managing cerecent activity.
score: 1

hook useCESettings

file: src/cores/ce/hooks/useCESettings.ts:16
kind: hook
core: ce
spec: (none)
summary: Consumer-friendly hook for accessing CE module settings with defaults applied.Usage:This hook provides a clean API for reading settings without needing tohandle null/undefined checks or know about the defaults.
score: 4

hook useCollapsedTracks

file: src/cores/ce/hooks/useCollapsedTracks.ts:38
kind: hook
core: ce
spec: CE-64
summary: Manages the set of collapsed pipeline tracks for the current org, persisting state andre-hydrating it whenever the active organization changes.
returns: The collapsed-track set plus its setter.
score: 5

hook useConsentEvidence

file: src/cores/ce/hooks/useConsentEvidence.ts:57
kind: hook
core: ce
spec: (none)
summary: Fetch consent evidence timeline for a single contact.
score: 4

hook useContact

file: src/cores/ce/hooks/useContact.ts:12
kind: hook
core: ce
spec: (none)
summary: Hook for managing contact.
score: 1

hook useContactDocuments

file: src/cores/ce/hooks/useContactDocuments.ts:19
kind: hook
core: ce
spec: (none)
summary: List active (non-soft-deleted) documents for a contact.
score: 4

hook useContactMerge

file: src/cores/ce/hooks/useContactMerge.ts:37
kind: hook
core: ce
spec: (none)
summary: Merges two duplicate contacts in one transaction; resolves to the id (the undo handle).
score: 4

hook useContactNetwork

file: src/cores/ce/hooks/useContactNetwork.ts:39
kind: hook
core: ce
spec: (none)
summary: Fetches a 2-degree contact network via two sequential queries.
params:
- contactId — The focal contact ID
- organizationId — Organization for tenant isolation
- focalName — Display name for the focal contact
score: 4

hook useContactRelationships

file: src/cores/ce/hooks/useContactRelationships.ts:14
kind: hook
core: ce
spec: (none)
summary: Fetches active relationships for a contact, joining related contact names.
params:
- contactId — The focal contact ID
- organizationId — Organization for tenant isolation
score: 4

hook useContacts

file: src/cores/ce/hooks/useContacts.ts:38
kind: hook
core: ce
spec: (none)
summary: Returns paginated contacts with search and filter criteria scoped to one organization.
score: 4

hook useContactsForPartnerLinking

file: src/cores/ce/hooks/useContactsForPartnerLinking.ts:23
kind: hook
core: ce
spec: (none)
summary: Fetch contacts that can be linked to a partner (excludes already-linked contacts)
score: 4

hook useContactsWithoutLeads

file: src/cores/ce/hooks/useContactsWithoutLeads.ts:40
kind: hook
core: ce
spec: (none)
summary: Fetch contacts in an organization that do not have an active lead, optionally filtered by search. Returns a React Query result containing active contacts (id, first_name, last_name, email, phone, contact_type) for the specified organization that are not associated with any lead whose status is not “converted” or “lost”. When a string with trimmed length = 2 is provided, results are further filtered by case-insensitive matches against first name, last name, email, or by phone substring.
params:
- options — Options controlling the query - organizationId: string: The organization ID to scope contacts and leads (required) - search: string | undefined: Optional search text used to filter contacts; applied when trimmed length = 2 - enabled: boolean | undefined: Optional flag to enable or disable the query (defaults to true)
returns: UseQueryResultDbContact[], Error - A React Query result containing an array of eligible objects
example: | // Fetch contacts without active leads for an organization with a search termconst data: contacts, isLoading, error = useContactsWithoutLeads( organizationId: ‘org_123’, search: ‘smith’, enabled: true,);
score: 4

hook useContractRenewals

file: src/cores/ce/hooks/useContractRenewals.ts:42
kind: hook
core: ce
spec: (none)
summary: Fetch contracts approaching renewal within (default 90).
score: 4

hook useCreateActivity

file: src/cores/ce/hooks/useActivityMutations.ts:26
kind: hook
core: ce
spec: (none)
summary: Provides a React Query mutation to create a ce_activities record for the given organization. Creates a new activity row in , enforcing the provided , invalidates the activities list cache for that organization on success, and shows success or error toasts.
params:
- organizationId — The organization ID to associate with the created activity; must be a non-empty string.
returns: A React Query mutation object configured to insert an activity (accepts an object matching and resolves to the inserted row).
example: | const createActivity = useCreateActivity(orgId);createActivity.mutate( title: ‘Meeting’, description: ‘Discuss roadmap’ );
score: 4

hook useCreateCampaign

file: src/cores/ce/hooks/useCampaignMutations.ts:16
kind: hook
core: ce
spec: (none)
summary: Hook for managing create campaign.
score: 1

hook useCreateContact

file: src/cores/ce/hooks/useContactMutations.ts:14
kind: hook
core: ce
spec: (none)
summary: Hook for managing create contact.
score: 1

hook useCreateLeadConversion

file: src/cores/ce/hooks/useLeadConversions.ts:62
kind: hook
core: ce
spec: (none)
summary: Mutation hook for inserting a ce_lead_conversions audit record.Used by the enhanced convertLead flow in useLeadMutations.
score: 4

hook useCreateMilestone

file: src/cores/ce/hooks/usePartnerMilestones.ts:75
kind: hook
core: ce
spec: (none)
summary: Provides create milestone queries and mutation actions scoped to the current organization.
score: 4

hook useCreatePartner

file: src/cores/ce/hooks/usePartnerMutations.ts:26
kind: hook
core: ce
spec: (none)
summary: Create a React-Query mutation hook to insert a new partner for the given organization. Provides a mutation that inserts a partner row into with the supplied fields plus . On success it invalidates the partners list cache for the organization and shows a success toast; on error it shows an error toast.
params:
- organizationId — The organization ID to associate with the new partner; required and must be a non-empty string.
returns: A React Query mutation object that accepts a partner object (all fields except ) and resolves to the inserted partner row.
example: | const createPartner = useCreatePartner(orgId);createPartner.mutate( name: ‘Acme Co’, … );
score: 4

hook useCreatePartnerContract

file: src/cores/ce/hooks/usePartnerContracts.ts:68
kind: hook
core: ce
spec: (none)
summary: Create a new partner contract
score: 1

hook useCreatePartnerProgress

file: src/cores/ce/hooks/usePartnerProgressMutation.ts:16
kind: hook
core: ce
spec: (none)
summary: Hook for managing create partner progress.
score: 1

hook useCreateReferralSource

file: src/cores/ce/hooks/useReferralSources.ts:147
kind: hook
core: ce
spec: (none)
summary: Create a new referral source
score: 1

hook useCreateRelationship

file: src/cores/ce/hooks/useContactRelationshipMutations.ts:38
kind: hook
core: ce
spec: (none)
summary: Creates a bi-directional relationship (two rows) + logs activity.
score: 4

hook useCreateScreening

file: src/cores/ce/hooks/useCreateScreening.ts:68
kind: hook
core: ce
spec: (none)
summary: Mutation hook that creates a screening result + attempt pair.1. Inserts ce_screening_results (questionnaire data, triage, ASAM)2. Computes SLA from lead.created_at → now3. Inserts ce_screening_attempts linking to the result4. Publishes ce_screening_completed event (consent-gated per 42 CFR Part 2)5. Conditionally publishes ce_lead_waitlisted6. Invalidates screening attempt queries
score: 4

hook useCreateSlaConfig

file: src/cores/ce/hooks/useScreeningSlaConfig.ts:99
kind: hook
core: ce
spec: (none)
summary: Mutation hook for creating an SLA config record.
score: 4

hook useCreateWebForm

file: src/cores/ce/hooks/useWebForms.ts:122
kind: hook
core: ce
spec: (none)
summary: Provides create web form queries and mutation actions scoped to the current organization.
score: 4

hook useCrisisKeywordMatcher

file: src/cores/ce/hooks/useCrisisKeywordMatcher.ts:49
kind: hook
core: ce
spec: (none)
summary: Returns a memoized matcher function bound to the org’s active keyword set.
score: 4

hook useDeactivateMyCard

file: src/cores/ce/hooks/useMyCard.ts:144
kind: hook
core: ce
spec: (none)
summary: Toggle on the current user’s own card. Gated on .
score: 4

hook useDeleteActivity

file: src/cores/ce/hooks/useActivityMutations.ts:127
kind: hook
core: ce
spec: (none)
summary: Provide a mutation hook that deletes a ce_activities record scoped to an organization. Creates a React Query mutation which performs a hard delete of an activity row from the table, enforcing the provided as a defense-in-depth filter and showing success/error toasts.
params:
- organizationId — The current organization ID used to scope and authorize the delete operation; must be a non-empty string.
returns: The React Query mutation object for deleting an activity by its ID. Call or to perform the deletion.
example: | const deleteActivity = useDeleteActivity(orgId);// ImperativedeleteActivity.mutate(‘activity-id-123’);// Async/awaitawait deleteActivity.mutateAsync(‘activity-id-123’);
score: 4

hook useDeleteCampaign

file: src/cores/ce/hooks/useCampaignMutations.ts:91
kind: hook
core: ce
spec: (none)
summary: Hook for managing delete campaign.
score: 1

hook useDeleteContact

file: src/cores/ce/hooks/useContactMutations.ts:97
kind: hook
core: ce
spec: (none)
summary: Hook for managing delete contact.
score: 1

hook useDeleteMilestone

file: src/cores/ce/hooks/usePartnerMilestones.ts:137
kind: hook
core: ce
spec: (none)
summary: Provides delete milestone queries and mutation actions scoped to the current organization.
score: 4

hook useDeletePartner

file: src/cores/ce/hooks/usePartnerMutations.ts:108
kind: hook
core: ce
spec: (none)
summary: Provides a React Query mutation for soft-deleting a partner scoped to the given organization. Call the mutation with a partner ID to mark that partner’s timestamp instead of removing the row.
params:
- organizationId — The organization identifier used to scope the deletion; must be a non-empty string.
returns: UseMutationResultvoid, unknown, string, unknown A React Query mutation object for performing the soft-delete. Invoke or with the partner ID.
example: | const deletePartner = useDeletePartner(organizationId);// soft-delete a partnerdeletePartner.mutate(‘partner-id-123’);
score: 4

hook useDeletePartnerContact

file: src/cores/ce/hooks/usePartnerContacts.ts:216
kind: hook
core: ce
spec: (none)
summary: CE-66: Delete a partner-contact row (linked or standalone).Alias of for standalone rows. The DB trigger clears when the deleted row was primary.
score: 4

hook useDeletePartnerContract

file: src/cores/ce/hooks/usePartnerContracts.ts:134
kind: hook
core: ce
spec: (none)
summary: Soft delete a partner contract
score: 4

hook useDeletePartnerProgress

file: src/cores/ce/hooks/usePartnerProgressMutation.ts:82
kind: hook
core: ce
spec: (none)
summary: Hook for managing delete partner progress.
score: 1

hook useDeleteReferralSource

file: src/cores/ce/hooks/useReferralSources.ts:228
kind: hook
core: ce
spec: (none)
summary: Soft delete a referral source
score: 1

hook useDeleteRelationship

file: src/cores/ce/hooks/useContactRelationshipMutations.ts:109
kind: hook
core: ce
spec: (none)
summary: Soft-deletes a relationship (both directions) + logs activity.
score: 4

hook useDeleteWebForm

file: src/cores/ce/hooks/useWebForms.ts:202
kind: hook
core: ce
spec: (none)
summary: Provides delete web form queries and mutation actions scoped to the current organization.
score: 4

hook useDisconnectEmailAccount

file: src/cores/ce/hooks/useEmailAccountMutations.ts:141
kind: hook
core: ce
spec: (none)
summary: Disconnect (soft delete) an email account
score: 4

hook useDownloadContactDocument

file: src/cores/ce/hooks/useContactDocumentMutations.ts:163
kind: hook
core: ce
spec: (none)
summary: Generate a short-lived signed URL for downloading a document.Returned via mutation so consumers can trigger an action (e.g. open tab).
score: 4

hook useDownloadPartnerDocument

file: src/cores/ce/hooks/usePartnerDocumentMutations.ts:196
kind: hook
core: ce
spec: (none)
summary: Generate a short-lived signed URL for a partner document binary.Returned via mutation so consumers can open the URL on user gesture.
score: 4

hook useEmailAccount

file: src/cores/ce/hooks/useEmailAccounts.ts:106
kind: hook
core: ce
spec: (none)
summary: Fetch a single email account by ID
score: 4

hook useEmailAccounts

file: src/cores/ce/hooks/useEmailAccounts.ts:67
kind: hook
core: ce
spec: (none)
summary: Fetch connected email accounts for current user
score: 4

hook useEmailCompose

file: src/cores/ce/hooks/useEmailCompose.ts:46
kind: hook
core: ce
spec: (none)
summary: Provides email compose queries and mutation actions scoped to the current organization.
score: 4

hook useEmailCount

file: src/cores/ce/hooks/useEmailMessages.ts:140
kind: hook
core: ce
spec: (none)
summary: Get email count for a contact/partner (for tab badges)
score: 4

hook useEmailMessage

file: src/cores/ce/hooks/useEmailMessages.ts:117
kind: hook
core: ce
spec: (none)
summary: Fetch a single email message by ID
score: 4

hook useEmailMessages

file: src/cores/ce/hooks/useEmailMessages.ts:61
kind: hook
core: ce
spec: (none)
summary: Fetch paginated email messages for a contact/partner/lead
score: 4

hook useEmailSyncSummary

file: src/cores/ce/hooks/useEmailAccounts.ts:130
kind: hook
core: ce
spec: (none)
summary: Fetch email sync summary for dashboard widget
score: 4

hook useEmailTemplate

file: src/cores/ce/hooks/useEmailTemplates.ts:80
kind: hook
core: ce
spec: (none)
summary: Fetch a single email template by ID
score: 4

hook useEmailTemplateMutations

file: src/cores/ce/hooks/useEmailTemplateMutations.ts:28
kind: hook
core: ce
spec: (none)
summary: Hook for managing email template mutations.
score: 1

hook useEmailTemplates

file: src/cores/ce/hooks/useEmailTemplates.ts:30
kind: hook
core: ce
spec: (none)
summary: Fetch email templates for the current organization
score: 4

hook useEnrollmentMutation

file: src/cores/ce/hooks/useEnrollmentMutation.ts:30
kind: hook
core: ce
spec: (none)
summary: Provides CE sequence enrollment mutations scoped to one organization.
params:
- args — Enrollment mutation args containing .
returns: Mutation objects for , , , , and .
example: | const bulkEnroll = useEnrollmentMutation( organizationId );await bulkEnroll.mutateAsync( sequenceId, leadIds );
score: 4

hook useEventAttendees

file: src/cores/ce/hooks/useEventAttendees.ts:19
kind: hook
core: ce
spec: (none)
summary: Fetch attendees for an event
score: 1

hook useEventDetail

file: src/cores/ce/hooks/useEvents.ts:74
kind: hook
core: ce
spec: (none)
summary: Fetch a single event by ID
score: 1

hook useEventList

file: src/cores/ce/hooks/useEvents.ts:20
kind: hook
core: ce
spec: (none)
summary: Fetch all events for the current organization
score: 4

hook useEventMutations

file: src/cores/ce/hooks/useEvents.ts:103
kind: hook
core: ce
spec: (none)
summary: Event mutations (create, update, delete)
score: 4

hook useFreeBusy

file: src/cores/ce/hooks/useFreeBusy.ts:20
kind: hook
core: ce
spec: (none)
summary: Hook for fetching free/busy slots from a connected calendar.
params:
- params — Free/busy query parameters. Pass null to disable.
score: 1

hook useIdentityResolution

file: src/cores/ce/hooks/useIdentityResolution.ts:75
kind: hook
core: ce
spec: (none)
summary: Resolves a contact-shaped payload against the org’s existing contacts,returning ranked matches with tier + matched-on field breakdown.
score: 4

hook useIntakeArtifact

file: src/cores/ce/hooks/useIntakeAgent.ts:61
kind: hook
core: ce
spec: (none)
summary: Read the PF-128 artifact header + its latest version body (RLS-allowed direct selects).
score: 4

hook useIntakeAudit

file: src/cores/ce/hooks/useIntakeAgent.ts:185
kind: hook
core: ce
spec: (none)
summary: Read the content-free PF-127/PF-126/PF-111 audit surface for the thread (reuses the 2d adapter).
score: 4

hook useLead

file: src/cores/ce/hooks/useLead.ts:20
kind: hook
core: ce
spec: (none)
summary: Hook for managing lead.
score: 1

hook useLeadClosureMutation

file: src/cores/ce/hooks/useLeadClosureMutation.ts:50
kind: hook
core: ce
spec: (none)
summary: Hook returning the CE-63 lead-closure mutation. Use inside the closuredialog; the dialog is responsible for collecting and validating fields.
score: 4

hook useLeadConversions

file: src/cores/ce/hooks/useLeadConversions.ts:33
kind: hook
core: ce
spec: (none)
summary: Fetches the conversion history for a specific lead.Returns records ordered by created_at descending (most recent first).
score: 4

hook useLeadConversionWizard

file: src/cores/ce/wizards/lead-conversion/hooks/useLeadConversionWizard.ts:102
kind: hook
core: ce
spec: (none)
summary: State management for the lead conversion wizard.
score: 4

hook useLeadIntakeWizard

file: src/cores/ce/wizards/lead-intake/hooks/useLeadIntakeWizard.ts:113
kind: hook
core: ce
spec: (none)
summary: Central hook for Lead Intake Wizard state, validation, draft persistence, and submission.
score: 4

hook useLeadMutations

file: src/cores/ce/hooks/useLeadMutations.ts:131
kind: hook
core: ce
spec: (none)
summary: Provides lead mutations queries and mutation actions scoped to the current organization.
score: 4

hook useLeads

file: src/cores/ce/hooks/useLeads.ts:94
kind: hook
core: ce
spec: (none)
summary: Hook for managing leads.
score: 1

hook useLeadsByContact

file: src/cores/ce/hooks/useLeadsByContact.ts:17
kind: hook
core: ce
spec: (none)
summary: Hook for managing leads by contact.
score: 1

hook useLeadsByStage

file: src/cores/ce/hooks/useLeadsByStage.ts:48
kind: hook
core: ce
spec: (none)
summary: Provides leads by stage queries and mutation actions scoped to the current organization.
score: 4

hook useLeadStageMutations

file: src/cores/ce/hooks/useLeadStageMutations.ts:51
kind: hook
core: ce
spec: (none)
summary: Hook for managing lead stage mutations.
score: 1

hook useLeadStages

file: src/cores/ce/hooks/useLeadStages.ts:24
kind: hook
core: ce
spec: (none)
summary: Hook for fetching lead stages for the current organization.CE-64: pass to scope to one pipeline track. Without a the hook returns all active stages across all tracks in the org (legacybehavior for callers that aggregate across tracks).
score: 1

hook useLinkContactToPartner

file: src/cores/ce/hooks/usePartnerContacts.ts:50
kind: hook
core: ce
spec: (none)
summary: Link a contact to a partner
score: 1

hook useLocalDraft

file: src/cores/ce/wizards/lead-intake/hooks/useLocalDraft.ts:32
kind: hook
core: ce
spec: (none)
summary: Simple localStorage-based draft persistence for wizard form data.This store is unencrypted, survives logout, and is readable by any script onthe origin, so it MUST NOT receive PHI. It does not inspect or filter what itis given — callers are responsible for excluding PHI from the value they save.The lead-intake wizard enforces this by stripping insurance PHI (member_id,payer, coverage dates) before and never rehydrating it on load(see ). Only operational lead fields (names, phone, email)are persisted.
score: 4

hook useLogContractRenewal

file: src/cores/ce/hooks/useContractRenewalLogMutation.ts:38
kind: hook
core: ce
spec: (none)
summary: Append an entry to . Invalidates the renewalsdashboard so the UI reflects the latest state.
score: 4

hook useMatchCampaign

file: src/cores/ce/hooks/useLeadAttribution.ts:47
kind: hook
core: ce
spec: (none)
summary: Hook to match UTM params to campaigns
score: 4

hook useMatchCandidates

file: src/cores/ce/hooks/useMatchCandidates.ts:38
kind: hook
core: ce
spec: (none)
summary: Lists the org’s match candidates (default: pending review queue), joinedwith both contacts’ display fields for the side-by-side compare drawer.
score: 4

hook useMemberCards

file: src/cores/ce/hooks/useMemberCards.ts:28
kind: hook
core: ce
spec: (none)
summary: Admin list of all member cards in the org, newest first. Gated on .
score: 4

hook useMergeLog

file: src/cores/ce/hooks/useContactMerge.ts:82
kind: hook
core: ce
spec: (none)
summary: Merge-log entries for the org (newest first), optionally scoped to onecontact (survivor or merged side) — powers the merged-record banner andthe undo affordance.
score: 4

hook useMobileContactDetail

file: src/cores/ce/hooks/useMobileCrm.ts:54
kind: hook
core: ce
spec: (none)
summary: Fetches a single contact and records it in the LRU recent views.
score: 4

hook useMobileContactSearch

file: src/cores/ce/hooks/useMobileCrm.ts:32
kind: hook
core: ce
spec: (none)
summary: Mobile-optimized contact search with debouncing.Sorts by last_name asc (inherits from useContacts).
score: 4

hook useMobilePartnerDetail

file: src/cores/ce/hooks/useMobileCrm.ts:85
kind: hook
core: ce
spec: (none)
summary: Fetches a single partner and records it in the LRU recent views.
score: 4

hook useMyCard

file: src/cores/ce/hooks/useMyCard.ts:49
kind: hook
core: ce
spec: (none)
summary: Read the current user’s own card for the active org (null if none yet).
score: 4

hook useOfflineActivityQueue

file: src/cores/ce/hooks/useOfflineActivityQueue.ts:95
kind: hook
core: ce
spec: (none)
summary: Hook for enqueuing offline activities and syncing them to ce_activities.
score: 1

hook useOfflineContactCache

file: src/cores/ce/hooks/useOfflineContactCache.ts:37
kind: hook
core: ce
spec: (none)
summary: Hook providing cached contact/partner entries from the LRU store.Useful for displaying recently viewed items when offline.
score: 4

hook useOfflineQueueStatus

file: src/cores/ce/hooks/useOfflineActivityQueue.ts:38
kind: hook
core: ce
spec: (none)
summary: Provides the current offline queue status (pending count, full flag, online state).
score: 4

hook useOrgCalendarCapability

file: src/cores/ce/hooks/useOrgCalendarCapability.ts:26
kind: hook
core: ce
spec: (none)
summary: Determine whether the current user may schedule through the org’s GoogleWorkspace calendar via PF-101 domain-wide delegation.
score: 4

hook usePartner

file: src/cores/ce/hooks/usePartner.ts:14
kind: hook
core: ce
spec: (none)
summary: Provides partner queries and mutation actions scoped to the current organization.
score: 4

hook usePartnerContacts

file: src/cores/ce/hooks/usePartnerContacts.ts:20
kind: hook
core: ce
spec: (none)
summary: Fetch all contacts linked to a partner
score: 4

hook usePartnerContract

file: src/cores/ce/hooks/usePartnerContracts.ts:42
kind: hook
core: ce
spec: (none)
summary: Fetch a single contract by ID
score: 1

hook usePartnerContracts

file: src/cores/ce/hooks/usePartnerContracts.ts:16
kind: hook
core: ce
spec: (none)
summary: Fetch all contracts for a partner
score: 4

hook usePartnerHealthDashboard

file: src/cores/ce/hooks/usePartnerHealthDashboard.ts:65
kind: hook
core: ce
spec: (none)
summary: Hook for fetching aggregated partner health metrics for dashboard.
returns: error - If present, use before displaying to users
score: 1

hook usePartnerMilestones

file: src/cores/ce/hooks/usePartnerMilestones.ts:30
kind: hook
core: ce
spec: (none)
summary: Provides partner milestones queries and mutation actions scoped to the current organization.
score: 4

hook usePartnerMutations

file: src/cores/ce/hooks/usePartnerMutations.ts:138
kind: hook
core: ce
spec: (none)
summary: Legacy convenience wrapper for partner mutations.
score: 4

hook usePartnerOnboardingWizard

file: src/cores/ce/wizards/partner-onboarding/hooks/usePartnerOnboardingWizard.ts:111
kind: hook
core: ce
spec: (none)
summary: Central hook for Partner Onboarding Wizard state, validation, draft persistence, and submission.
score: 4

hook usePartnerProgressList

file: src/cores/ce/hooks/usePartnerProgressList.ts:36
kind: hook
core: ce
spec: (none)
summary: Provides partner progress list queries and mutation actions scoped to the current organization.
score: 4

hook usePartnerProgressReview

file: src/cores/ce/wizards/partner-progress-review/hooks/usePartnerProgressReview.ts:72
kind: hook
core: ce
spec: (none)
summary: Central hook for Partner Progress Review Wizard.
score: 4

hook usePartners

file: src/cores/ce/hooks/usePartners.ts:41
kind: hook
core: ce
spec: (none)
summary: Provides partners queries and mutation actions scoped to the current organization.
score: 4

hook usePartnerScorecard

file: src/cores/ce/hooks/usePartnerScorecard.ts:87
kind: hook
core: ce
spec: (none)
summary: Hook for fetching partner scorecard metrics
params:
- options — Configuration for sorting and filtering
returns: Query result with partner scorecard metrics
score: 1

hook usePendingMatchCandidateCount

file: src/cores/ce/hooks/useMatchCandidates.ts:154
kind: hook
core: ce
spec: (none)
summary: Count of pending candidates — review-queue badge.
score: 4

hook usePhiBlockCheck

file: src/cores/ce/hooks/usePhiBlockCheck.ts:35
kind: hook
core: ce
spec: (none)
summary: Check if a message contains PHI and whether it should be blocked
params:
- message — The message text to check
returns: PHI check result with block/warn status
score: 4

hook usePhoneInputFormatting

file: src/cores/ce/hooks/usePhoneInputFormatting.ts:19
kind: hook
core: ce
spec: (none)
summary: Hook for phone input formattingReturns handlers for onChange that format input while preserving raw digits for storage
score: 1

hook usePipelineContactHasAlertTag

file: src/cores/ce/components/pipeline/pipelineTagsContext.ts:31
kind: hook
core: ce
spec: (none)
summary: CE-65 tile-metadata contract: returns whether the contact has at least onealert tag assigned. Derived from the same in-memory map as the tag chipsso no extra query is needed.
score: 4

hook usePipelineContactTags

file: src/cores/ce/components/pipeline/pipelineTagsContext.ts:20
kind: hook
core: ce
spec: CE-61
summary: Reads the tags assigned to a single contact from the pipeline tags context, returning when the context is absent or no contact id is supplied.
params:
- contactId — Contact whose tags to look up; nullish ids yield .
returns: The contact’s tags, or when unavailable.
score: 5

hook usePipelineMetrics

file: src/cores/ce/hooks/usePipelineMetrics.ts:113
kind: hook
core: ce
spec: (none)
summary: Hook for fetching pipeline metrics with configurable options
params:
- options — Configuration for date range and polling
returns: Query result with pipeline summary and stage metrics
score: 1

hook usePublishSequence

file: src/cores/ce/wizards/sequences/hooks/usePublishSequence.ts:47
kind: hook
core: ce
spec: (none)
summary: Mutation hook that calls the ce_publish_sequence RPC.
score: 4

hook useRealtimeSmsMessages

file: src/cores/ce/hooks/useRealtimeSmsMessages.ts:31
kind: hook
core: ce
spec: (none)
summary: Hook for managing realtime sms messages.
score: 1

hook useRecalculateAllSegments

file: src/cores/ce/hooks/useSegmentMembership.ts:90
kind: hook
core: ce
spec: (none)
summary: Recalculate all segments for the organization
score: 4

hook useRecalculateSegment

file: src/cores/ce/hooks/useSegmentMembership.ts:59
kind: hook
core: ce
spec: (none)
summary: Recalculate segment membership count
score: 4

hook useRecordConsentEvidence

file: src/cores/ce/hooks/useConsentEvidence.ts:105
kind: hook
core: ce
spec: (none)
summary: Append a new consent evidence record. Append-only — no update/delete.
score: 4

hook useReferralAttemptMutations

file: src/cores/ce/hooks/useReferralAttempts.ts:198
kind: hook
core: ce
spec: (none)
summary: Convenience wrapper mirroring useReferralSourceMutations.
score: 4

hook useReferralSource

file: src/cores/ce/hooks/useReferralSources.ts:121
kind: hook
core: ce
spec: (none)
summary: Fetch a single referral source by ID
score: 4

hook useReferralSourceMutations

file: src/cores/ce/hooks/useReferralSources.ts:183
kind: hook
core: ce
spec: (none)
summary: Legacy convenience wrapper for create/update/delete referral source mutations.
score: 4

hook useReferralSources

file: src/cores/ce/hooks/useReferralSources.ts:38
kind: hook
core: ce
spec: (none)
summary: Fetch paginated list of referral sources
score: 4

hook useRejectIntake

file: src/cores/ce/hooks/useIntakeAgent.ts:163
kind: hook
core: ce
spec: (none)
summary: Deny: transition the artifact draft→rejected (no write). Allowed for a holder of pf.artifact.verify.
score: 4

hook useRemoveQueueMember

file: src/cores/ce/hooks/useAssignmentQueue.ts:144
kind: hook
core: ce
spec: (none)
summary: Provides remove queue member queries and mutation actions scoped to the current organization.
score: 4

hook useReorderQueueMembers

file: src/cores/ce/hooks/useAssignmentQueue.ts:223
kind: hook
core: ce
spec: (none)
summary: Provides reorder queue members queries and mutation actions scoped to the current organization.
score: 4

hook useResolveMatchCandidate

file: src/cores/ce/hooks/useMatchCandidates.ts:91
kind: hook
core: ce
spec: (none)
summary: Flips a single candidate to or , recording reviewer +timestamp (AC-5 then-leg). Merge resolution happens via (the merge RPC settles involved candidates itself).
score: 4

hook useRingCentralRemoteExtensions

file: src/cores/ce/hooks/useRingCentralRemoteExtensions.ts:27
kind: hook
core: ce
spec: (none)
summary: Hook to fetch RingCentral extensions directly from the RingCentral APIvia the ringcentral-list-extensions edge function.
score: 4

hook useRingCentralWizard

file: src/cores/ce/hooks/useRingCentralWizard.ts:130
kind: hook
core: ce
spec: (none)
summary: Provides state and actions to drive the RingCentral setup wizard, including step navigation, completion tracking, prerequisite checks, and per-organization draft persistence.
returns: An object with the wizard state, prerequisite status, navigation helpers, and completion controls:- (number): Active wizard step.- (number[]): Steps marked as completed.- (number): Total number of steps in the wizard.- (PrerequisiteStatus | null): Latest prerequisite check result or if not loaded.- (boolean): Whether prerequisites are currently being fetched.- (unknown): Error from the prerequisites check, if any.- (function): Function to re-run the prerequisites check.- (function): Jump to a valid step between 1 and .- (function): Advance to the next step and mark the current step complete.- (function): Move to the previous step.- (function): Mark a specific step as completed.- (function): Return if is marked complete.- (function): Finalize the wizard, clear the draft, show a completion toast, and navigate to the CE settings page.- (function): Cancel the wizard, clear the draft, and navigate to the CE settings page.
score: 4

hook useScheduleMeeting

file: src/cores/ce/hooks/useScheduleMeeting.ts:18
kind: hook
core: ce
spec: (none)
summary: Hook for scheduling a meeting through a connected calendar.
score: 1

hook useScheduleOrgMeeting

file: src/cores/ce/hooks/useScheduleOrgMeeting.ts:57
kind: hook
core: ce
spec: (none)
summary: Hook for scheduling a meeting on the org Google Workspace calendar via PF-101.
score: 1

hook useScreeningAttempts

file: src/cores/ce/hooks/useScreeningAttempts.ts:18
kind: hook
core: ce
spec: (none)
summary: Fetches all screening attempts for a given lead, ordered most recent first.Includes screener profile (id, full_name) via join.
score: 4

hook useScreeningQuestionnaire

file: src/cores/ce/hooks/useScreeningQuestionnaire.ts:18
kind: hook
core: ce
spec: (none)
summary: Fetches the active screening questionnaire for the specified program type.Returns the highest-version active questionnaire.
score: 4

hook useScreeningSlaConfigs

file: src/cores/ce/hooks/useScreeningSlaConfig.ts:22
kind: hook
core: ce
spec: (none)
summary: Fetches all SLA config records for the current organization.
score: 4

hook useScreeningSlaThreshold

file: src/cores/ce/hooks/useScreeningSlaConfig.ts:50
kind: hook
core: ce
spec: (none)
summary: Fetches the SLA threshold for a specific program type + optional site.Falls back to org-level config if no site-specific config exists.
score: 4

hook useSegmentDetail

file: src/cores/ce/hooks/useSegments.ts:63
kind: hook
core: ce
spec: (none)
summary: Fetch a single segment by ID
score: 1

hook useSegmentList

file: src/cores/ce/hooks/useSegments.ts:25
kind: hook
core: ce
spec: (none)
summary: Fetch all segments for the current organization
score: 4

hook useSegmentMembers

file: src/cores/ce/hooks/useSegmentMembership.ts:122
kind: hook
core: ce
spec: (none)
summary: Get segment members
score: 1

hook useSegmentMutations

file: src/cores/ce/hooks/useSegments.ts:92
kind: hook
core: ce
spec: (none)
summary: Segment mutations (create, update, delete)
score: 4

hook useSegmentPreview

file: src/cores/ce/hooks/useSegmentMembership.ts:17
kind: hook
core: ce
spec: (none)
summary: Preview segment member count based on criteriaUses debounced calls to avoid excessive DB queries
score: 4

hook useSequenceDetail

file: src/cores/ce/hooks/useSequenceDetail.ts:13
kind: hook
core: ce
spec: (none)
summary: Fetches sequence detail (including related steps) for one sequence within an organization.
params:
- sequenceId — Sequence id to load, or to disable the lookup.
- organizationId — Active organization id, or when org context is unavailable.
returns: React Query result resolving to ; returns when ids are missing and throws on Supabase query errors.
score: 4

hook useSequenceList

file: src/cores/ce/hooks/useSequenceList.ts:25
kind: hook
core: ce
spec: (none)
summary: Returns CE sequences for the active organization with optional status and search filtering.
params:
- organizationId — Active organization id used for tenant scoping.
- filters — Optional (, ).
returns: React Query result containing an array of rows for the organization.
score: 4

hook useSequenceMutation

file: src/cores/ce/hooks/useSequenceMutation.ts:17
kind: hook
core: ce
spec: (none)
summary: Provides CE sequence mutations scoped to one organization.
params:
- args — Sequence mutation arguments containing .
returns: Mutation objects: , , , , and .
score: 4

hook useSetPrimaryContact

file: src/cores/ce/hooks/usePartnerContacts.ts:109
kind: hook
core: ce
spec: (none)
summary: Set a contact as the primary contact for a partnerNote: The database trigger will automatically sync this to ce_partners.primary_contact_id
score: 4

hook useSmsConsent

file: src/cores/ce/hooks/useSmsConsent.ts:50
kind: hook
core: ce
spec: (none)
summary: Hook to fetch SMS consent records
score: 4

hook useSmsConsentByPhone

file: src/cores/ce/hooks/useSmsConsent.ts:109
kind: hook
core: ce
spec: (none)
summary: Hook to fetch a single consent record by phone number
score: 4

hook useSmsConsentMutations

file: src/cores/ce/hooks/useSmsConsentMutations.ts:40
kind: hook
core: ce
spec: (none)
summary: Hook for SMS consent mutations
score: 1

hook useSmsContactMatch

file: src/cores/ce/hooks/useSmsContactMatch.ts:34
kind: hook
core: ce
spec: (none)
summary: Find a contact by phone numberSearches both phone and mobile_phone columns
params:
- phoneNumber — Phone number to search (any format)
- options — Query options
score: 4

hook useSmsContactMatchBatch

file: src/cores/ce/hooks/useSmsContactMatch.ts:76
kind: hook
core: ce
spec: (none)
summary: Find multiple contacts by phone numbers (batch matching)Useful for matching multiple inbound messages
params:
- phoneNumbers — Array of phone numbers to search
- options — Query options
score: 4

hook useSmsMessages

file: src/cores/ce/hooks/useSmsMessages.ts:59
kind: hook
core: ce
spec: (none)
summary: Hook to fetch SMS messages
score: 1

hook useSmsMessagesMutations

file: src/cores/ce/hooks/useSmsMessagesMutations.ts:70
kind: hook
core: ce
spec: (none)
summary: Hook for SMS message mutations
score: 1

hook useSmsNotifications

file: src/cores/ce/hooks/useSmsNotifications.ts:36
kind: hook
core: ce
spec: (none)
summary: Hook for real-time SMS notification toasts
score: 1

hook useSmsSend

file: src/cores/ce/hooks/useSmsSend.ts:57
kind: hook
core: ce
spec: (none)
summary: Hook for sending SMS messages via edge function
score: 1

hook useSmsSettings

file: src/cores/ce/hooks/useSmsSettings.ts:32
kind: hook
core: ce
spec: (none)
summary: Hook for managing SMS-specific settings
score: 1

hook useSmsTemplate

file: src/cores/ce/hooks/useSmsTemplates.ts:84
kind: hook
core: ce
spec: (none)
summary: Fetch a single SMS template by ID
score: 4

hook useSmsTemplateMutations

file: src/cores/ce/hooks/useSmsTemplateMutations.ts:38
kind: hook
core: ce
spec: (none)
summary: Provides sms template mutations queries and mutation actions scoped to the current organization.
score: 4

hook useSmsTemplates

file: src/cores/ce/hooks/useSmsTemplates.ts:43
kind: hook
core: ce
spec: (none)
summary: Fetch SMS templates for the current organization
score: 4

hook useSoftDeleteContactDocument

file: src/cores/ce/hooks/useContactDocumentMutations.ts:132
kind: hook
core: ce
spec: (none)
summary: Soft-delete a contact document by setting .The underlying storage object is intentionally preserved (FR-1.6).
score: 4

hook useSoftDeletePartnerDocument

file: src/cores/ce/hooks/usePartnerDocumentMutations.ts:166
kind: hook
core: ce
spec: (none)
summary: Soft-delete a partner document by setting . Storage objects areintentionally preserved (versioning audit trail).
score: 4

hook useStaleLeadCount

file: src/cores/ce/hooks/useStaleLeadCount.ts:33
kind: hook
core: ce
spec: (none)
summary: Counts active leads older than the configured stale threshold and refreshes periodically.
score: 4

hook useStartIntakeRun

file: src/cores/ce/hooks/useIntakeAgent.ts:46
kind: hook
core: ce
spec: (none)
summary: Start a run: invoke(‘start’) → server opens run+thread, reads, writes the draft artifact.
score: 4

hook useSubmitToOptum

file: src/cores/ce/hooks/priorAuth/usePriorAuthSubmissions.ts:99
kind: hook
core: ce
spec: (none)
summary: Invoke the ce-submit-optum-pa edge function (AC-3 / AC-6).
score: 4

hook useSuppressionCheck

file: src/cores/ce/hooks/useSuppressions.ts:190
kind: hook
core: ce
spec: (none)
summary: Check whether a contact is suppressed for the given channel.Returns . always counts as suppressed.
score: 4

hook useSuppressionMutations

file: src/cores/ce/hooks/useSuppressions.ts:241
kind: hook
core: ce
spec: (none)
summary: Mutation hooks for suppressions: upsert (create/update) and remove.
score: 4

hook useSuppressions

file: src/cores/ce/hooks/useSuppressions.ts:68
kind: hook
core: ce
spec: (none)
summary: List suppressions for the current organization, optionally filtered by channel/contact.
score: 4

hook useSuppressionsPaginated

file: src/cores/ce/hooks/useSuppressions.ts:128
kind: hook
core: ce
spec: (none)
summary: Server-side paginated + filtered suppression list for the current organization.Uses Supabase + for true server-side pagination sothe dataset can scale beyond the default 1000-row query limit.
score: 4

hook useSyncEmailAccount

file: src/cores/ce/hooks/useEmailAccountMutations.ts:27
kind: hook
core: ce
spec: (none)
summary: Trigger manual sync for an email account
score: 4

hook useTestOptumConnection

file: src/cores/ce/hooks/priorAuth/useOptumCredentials.ts:51
kind: hook
core: ce
spec: (none)
summary: Lightweight connection check (FR-16): confirms both credentials are stored.A live portal probe is not possible from the browser/edge runtime; the livesmoke against pct.my.site.com is a pre-go-live manual step.
score: 4

hook useToggleEmailSync

file: src/cores/ce/hooks/useEmailAccountMutations.ts:99
kind: hook
core: ce
spec: (none)
summary: Toggle sync enabled/disabled for an account
score: 4

hook useToggleQueueMemberStatus

file: src/cores/ce/hooks/useAssignmentQueue.ts:182
kind: hook
core: ce
spec: (none)
summary: Provides toggle queue member status queries and mutation actions scoped to the current organization.
score: 4

hook useToggleWebFormStatus

file: src/cores/ce/hooks/useWebForms.ts:239
kind: hook
core: ce
spec: (none)
summary: Provides toggle web form status queries and mutation actions scoped to the current organization.
score: 4

hook useUndoMerge

file: src/cores/ce/hooks/useContactMerge.ts:60
kind: hook
core: ce
spec: (none)
summary: Undoes a merge inside the org’s undo window; resolves to the restoredcontact id.
score: 4

hook useUnlinkContactFromPartner

file: src/cores/ce/hooks/usePartnerContacts.ts:81
kind: hook
core: ce
spec: (none)
summary: Unlink a contact from a partner
score: 4

hook useUpdateActivity

file: src/cores/ce/hooks/useActivityMutations.ts:72
kind: hook
core: ce
spec: (none)
summary: Update an existing activity scoped to the given organization. Performs a defense-in-depth update of a row filtered by and , sets to the current timestamp, and returns the updated row. On success the hook invalidates the organization’s activities list and the specific activity cache entry, and shows a success toast. On error it shows a sanitized error toast.
params:
- organizationId — The organization ID used to scope and authorize the update operation
returns: UseMutationResultDbActivity, unknown, DbActivityUpdate & id: string , unknown - A React Query mutation object for performing activity updates
example: | const updateActivity = useUpdateActivity(‘org_123’);updateActivity.mutate( id: ‘act_456’, description: ‘Updated description’ );
score: 4

hook useUpdateCampaign

file: src/cores/ce/hooks/useCampaignMutations.ts:52
kind: hook
core: ce
spec: (none)
summary: Hook for managing update campaign.
score: 1

hook useUpdateContact

file: src/cores/ce/hooks/useContactMutations.ts:64
kind: hook
core: ce
spec: (none)
summary: Hook for managing update contact.
score: 1

hook useUpdateEmailAccount

file: src/cores/ce/hooks/useEmailAccountMutations.ts:181
kind: hook
core: ce
spec: (none)
summary: Update email account settings
score: 1

hook useUpdateMilestone

file: src/cores/ce/hooks/usePartnerMilestones.ts:105
kind: hook
core: ce
spec: (none)
summary: Provides update milestone queries and mutation actions scoped to the current organization.
score: 4

hook useUpdatePartner

file: src/cores/ce/hooks/usePartnerMutations.ts:65
kind: hook
core: ce
spec: (none)
summary: Creates a React-Query mutation for updating a partner within a given organization. Returns a mutation hook that updates a partner row in , scoped to the provided , invalidates related query cache on success, and shows toast notifications for success or error.
params:
- organizationId — The organization id to scope the update to; must be a non-empty string.
returns: The mutation result (React Query useMutation) configured to perform partner updates.
example: | const updatePartner = useUpdatePartner(currentOrganizationId);updatePartner.mutate( id: ‘partner-id’, name: ‘New Name’ );
score: 4

hook useUpdatePartnerContract

file: src/cores/ce/hooks/usePartnerContracts.ts:100
kind: hook
core: ce
spec: (none)
summary: Update an existing partner contract
score: 4

hook useUpdatePartnerProgress

file: src/cores/ce/hooks/usePartnerProgressMutation.ts:48
kind: hook
core: ce
spec: (none)
summary: Hook for managing update partner progress.
score: 1

hook useUpdatePriorAuthStatus

file: src/cores/ce/hooks/priorAuth/usePriorAuthSubmissions.ts:67
kind: hook
core: ce
spec: (none)
summary: Manual decision update when Optum responds by phone/mail (AC-4, FR-13).
score: 4

hook useUpdateReferralSource

file: src/cores/ce/hooks/useReferralSources.ts:194
kind: hook
core: ce
spec: (none)
summary: Update an existing referral source
score: 4

hook useUpdateWebForm

file: src/cores/ce/hooks/useWebForms.ts:162
kind: hook
core: ce
spec: (none)
summary: Provides update web form queries and mutation actions scoped to the current organization.
score: 4

hook useUploadContactDocument

file: src/cores/ce/hooks/useContactDocumentMutations.ts:44
kind: hook
core: ce
spec: (none)
summary: Upload a contact document: validates, inserts metadata, uploads to storage,and rolls back the metadata row if storage upload fails.
score: 4

hook useUploadPartnerDocument

file: src/cores/ce/hooks/usePartnerDocumentMutations.ts:70
kind: hook
core: ce
spec: (none)
summary: Upload a partner document: validates, inserts metadata, uploads to storage,and rolls back the metadata row if the storage upload fails.
score: 4

hook useUpsertMyCard

file: src/cores/ce/hooks/useMyCard.ts:77
kind: hook
core: ce
spec: (none)
summary: Create or update the current user’s card. On create, generates a unique slugand retries once with a fresh suffix if the global slug constraint trips.Gated on .
score: 4

hook useUpsertPartnerContact

file: src/cores/ce/hooks/usePartnerContacts.ts:153
kind: hook
core: ce
spec: (none)
summary: CE-66: Insert or update a partner-contact row (linked or standalone).If is provided, performs an UPDATE; otherwise INSERT. When is true,any sibling primary rows are unset first so the partial unique constraint is satisfied.
score: 4

hook useWebFormDetail

file: src/cores/ce/hooks/useWebForms.ts:88
kind: hook
core: ce
spec: (none)
summary: Provides web form detail queries and mutation actions scoped to the current organization.
score: 4

hook useWebFormList

file: src/cores/ce/hooks/useWebForms.ts:42
kind: hook
core: ce
spec: (none)
summary: Provides web form list queries and mutation actions scoped to the current organization.
score: 4

hook useWebFormSubmissions

file: src/cores/ce/hooks/useWebFormSubmissions.ts:38
kind: hook
core: ce
spec: (none)
summary: Hook for managing web form submissions.
score: 1

hook useWebFormSubmissionStats

file: src/cores/ce/hooks/useWebFormSubmissions.ts:97
kind: hook
core: ce
spec: (none)
summary: Hook for managing web form submission stats.
score: 1

Components

component ActivityAnalyticsPage

file: src/cores/ce/pages/ActivityAnalyticsPage.tsx:17
kind: component
core: ce
spec: (none)
summary: Utility for activity analytics page.
score: 1

component ActivityDialog

file: src/cores/ce/components/ActivityDialog.tsx:22
kind: component
core: ce
spec: (none)
summary: Hosts the activity form in a dialog and closes on submit or cancel.
score: 2

component ActivityForm

file: src/cores/ce/components/ActivityForm.tsx:88
kind: component
core: ce
spec: (none)
summary: Utility for activity form.
score: 1

component ActivitySearchFilters

file: src/cores/ce/components/ActivitySearchFilters.tsx:52
kind: component
core: ce
spec: (none)
summary: Utility for activity search filters.
score: 1

component ActivityTimeline

file: src/cores/ce/components/ActivityTimeline.tsx:70
kind: component
core: ce
spec: (none)
summary: Renders a chronological activity timeline for a subject with filtering, pagination, and loading/error/empty states.The component fetches and accumulates pages of activities, supports filtering by activity type, and provides a “Load More” controlwhen additional pages are available. It also handles initial loading, incremental loading, error retry, and an empty state tailoredto the active filter.
params:
- organizationId — The ID of the organization the subject belongs to.
- subjectType — The subject kind: either or .
- subjectId — The ID of the subject whose activities should be displayed.
- showFilters — When (default), display the activity type filter UI.
- maxHeight — Optional CSS value applied as the timeline’s max-height to enable an internal scrollable area (e.g., ).
returns: A React element containing the activity timeline UI.
example: | ActivityTimeline organizationId=“org_123” subjectType=“contact” subjectId=“contact_456” showFilters=true maxHeight=“480px”/Accessibility:- The activity-type SelectTrigger includes an ARIA label (“Filter activities by type”) to announce the filter control to assistive technologies.
score: 4

component ActivityTimelineItem

file: src/cores/ce/components/ActivityTimelineItem.tsx:95
kind: component
core: ce
spec: (none)
summary: Renders a timeline entry for a single activity, including icon, labels, timestamp, details, and optional follow-up task link.Renders the activity’s type-specific icon and color, a relative activity date (or “Unknown date” if invalid), creator name, subject, description, outcome, follow-up date, duration, call-specific badges (direction and disposition), and a linked task status badge when a follow-up task exists. - activity: The activity record to render. Expected shape matches ActivityListItem: includes fields like , , , , , , , , , and . - showConnector: Whether to render the vertical timeline connector line to the left of the item. Defaults to .
returns: The rendered timeline item element for the given activity.
example: | ActivityTimelineItem activity=activity showConnector=false /Accessibility considerations:- The timeline connector is marked aria-hidden.- Icons used are marked aria-hidden and important textual information (labels, dates, creator) is rendered as text for screen readers.
score: 5

component ActivityTimelineSkeleton

file: src/cores/ce/components/ActivityTimelineSkeleton.tsx:15
kind: component
core: ce
spec: (none)
summary: Renders the activity timeline skeleton interface.
score: 2

component AdditionalContactsStep

file: src/cores/ce/wizards/partner-onboarding/steps/AdditionalContactsStep.tsx:21
kind: component
core: ce
spec: (none)
summary: Step 3: Add optional additional contacts.
score: 2

component AddLeadDialog

file: src/cores/ce/components/AddLeadDialog.tsx:111
kind: component
core: ce
spec: (none)
summary: Renders a dialog for creating a new lead by selecting an existing contact or creating a new one,and capturing partner, campaign attribution, source, expected admission date, and notes.This component manages contact search, default lead stage selection, and submits a create-lead mutation.
params:
- props — Component props - open: Controls whether the dialog is open - onOpenChange: Callback invoked with the new open state when the dialog is opened or closedAccessibility:- The contact selector is implemented as a combobox-like popover with a labeled trigger and keyboard-accessible search.- Action buttons include accessible labels (e.g., the “Create new contact” button has an aria-label).
example: | AddLeadDialog open=isDialogOpen onOpenChange=(open) = setIsDialogOpen(open) /
score: 4

component AddLeadDialogTrackField

file: src/cores/ce/components/AddLeadDialog.tsx:73
kind: component
core: ce
spec: (none)
summary: CE-64-EN-01 AC-1: Pipeline track picker for the AddLeadDialog form.Lets the user explicitly pick a pipeline track for the new lead; defaults toautomatic track selection (based on services) when left unset.
params:
- props — Component props - value: The currently selected track id, or null for auto-selection - onChange: Callback invoked with the selected track id
score: 2

component AddSuppressionDialog

file: src/cores/ce/components/compliance/AddSuppressionDialog.tsx:39
kind: component
core: ce
spec: CE-16
summary: Dialog for adding or editing a contact’s communication suppression, letting staff suppress allchannels or toggle email/SMS/phone individually before upserting the record.
score: 3

component AiExtractionSettingsCard

file: src/cores/ce/components/settings/AiExtractionSettingsCard.tsx:22
kind: component
core: ce
spec: (none)
summary: CE-59 Phase 2 admin enablement card.Per-tenant toggle for AI document extraction on contact documents.Default OFF. Enabling requires explicit compliance acknowledgment ofCAC-2..6 controls (PHI redaction preflight, 42 CFR Part 2 fail-closed,confirm-only writes, append-only audit). Visibility/usage is also gatedby the permission.
score: 2

component AssigneeFilterSelect

file: src/cores/ce/components/AssigneeFilterSelect.tsx:39
kind: component
core: ce
spec: CE-62
summary: Dropdown that filters the lead pipeline by assignee, offering “All Users” (gated by), “Assigned to Me”, “Unassigned”, and an alphabetised list of active staff.
score: 3

component AssignmentQueueMemberItem

file: src/cores/ce/components/web-forms/AssignmentQueueMemberItem.tsx:26
kind: component
core: ce
spec: (none)
summary: Renders the assignment queue member item interface.
score: 2

component AssignmentQueueMemberSearch

file: src/cores/ce/components/web-forms/AssignmentQueueMemberSearch.tsx:28
kind: component
core: ce
spec: (none)
summary: Utility for assignment queue member search.
score: 1

component AssignmentQueuePanel

file: src/cores/ce/components/web-forms/AssignmentQueuePanel.tsx:46
kind: component
core: ce
spec: (none)
summary: Manages round-robin assignment members with drag reorder, status toggles, and add/remove actions.
score: 2

component AssignmentStep

file: src/cores/ce/wizards/lead-intake/steps/AssignmentStep.tsx:32
kind: component
core: ce
spec: (none)
summary: Lead-intake wizard step: choose the assigned intake coordinator (or leave thelead Unassigned to route it through the CE-62 assignment queue).
score: 2

component BedBoardEmbed

file: src/cores/ce/components/BedBoardEmbed.tsx:37
kind: component
core: ce
spec: CE-72
summary: Read-only bed-availability widget for the pipeline. See file header.
score: 3

component BedBoardSettingsCard

file: src/cores/ce/components/settings/BedBoardSettingsCard.tsx:19
kind: component
core: ce
spec: (none)
summary: Card toggling the Auth-risk tile on the pipeline bed-availability widget.
score: 2

component BulkEnrollDialog

file: src/cores/ce/components/sequences/BulkEnrollDialog.tsx:26
kind: component
core: ce
spec: none
summary: Dialog for enrolling multiple selected leads into a follow-up sequence at once, choosing anactive sequence and dispatching a bulk enrollment.
score: 3

component CalendarActivityIndicator

file: src/cores/ce/components/CalendarActivityIndicator.tsx:27
kind: component
core: ce
spec: (none)
summary: Renders a small badge indicating that an activity is linked to a syncedcalendar event. Shows the provider name and sync status on hover.
score: 2

component CalendarFollowUpSettingsCard

file: src/cores/ce/components/settings/CalendarFollowUpSettingsCard.tsx:21
kind: component
core: ce
spec: (none)
summary: CE-73 Leg C (CodeRabbit reverse flow) admin card.Per-tenant control for auto-creating a follow-up task when a meeting isscheduled () and the defaultlead time in days (, 1–14). Admin-gated on .
score: 2

component CallActivityWidget

file: src/cores/ce/components/dashboard/CallActivityWidget.tsx:55
kind: component
core: ce
spec: (none)
summary: Displays a compact widget listing recent call activity for the current organization.Renders loading skeletons, an error panel with a sanitized message, an empty-state message,or a scrollable list of recent calls showing direction, contact/partner or phone number,relative start time, disposition badge (or “Pending”), and user attribution. Rows arekeyboard-accessible and navigate to the call detail view when activated.
params:
- props — Component props - size: Widget size controlling item limit and layout; shows up to 5 items, any other value shows up to 10 items.
example: | CallActivityWidget size=“2x1” /Accessibility: each call row uses role=“button”, is focusable via tab, and supports activation with the Enter key. Error and empty states provide concise, readable messages.
score: 4

component CallAnalyticsDashboard

file: src/cores/ce/components/analytics/CallAnalyticsDashboard.tsx:106
kind: component
core: ce
spec: (none)
summary: Renders the Call Analytics dashboard with filters, KPI cards, recording coverage, and charts.Displays date range and aggregation controls, a refresh action, four KPI stat cards (Total, Inbound, Outbound, Avg Duration),a recording coverage card with progress and contextual messaging, and two charts (call volume over time and disposition breakdown).
params:
- props — Component props. - className: Optional container className passed to the root element for layout or styling.Accessibility:- ToggleGroup controls include aria-labels for each option.- Interactive controls (ToggleGroup, Button) are keyboard-focusable and announce state via native semantics.
returns: The rendered Call Analytics dashboard UI as a React element.
example: | CallAnalyticsDashboard className=“p-4” /
score: 4

component CallAnalyticsPage

file: src/cores/ce/pages/CallAnalyticsPage.tsx:17
kind: component
core: ce
spec: (none)
summary: Renders the call analytics page interface.
score: 2

component CallVolumeChart

file: src/cores/ce/components/analytics/CallVolumeChart.tsx:63
kind: component
core: ce
spec: (none)
summary: Renders the call volume chart interface.
score: 2

component CampaignAnalyticsDashboard

file: src/cores/ce/components/analytics/CampaignAnalyticsDashboard.tsx:63
kind: component
core: ce
spec: (none)
summary: Utility for campaign analytics dashboard.
score: 1

component CampaignAnalyticsPage

file: src/cores/ce/pages/CampaignAnalyticsPage.tsx:15
kind: component
core: ce
spec: (none)
summary: Renders the campaign analytics page interface.
score: 2

component CampaignCard

file: src/cores/ce/components/campaigns/CampaignCard.tsx:33
kind: component
core: ce
spec: (none)
summary: Utility for campaign card.
score: 1

component CampaignFormDialog

file: src/cores/ce/components/campaigns/CampaignFormDialog.tsx:55
kind: component
core: ce
spec: (none)
summary: Utility for campaign form dialog.
score: 1

component CampaignPerformanceChart

file: src/cores/ce/components/analytics/CampaignPerformanceChart.tsx:83
kind: component
core: ce
spec: (none)
summary: Compares campaign leads vs conversions and routes clicks to campaign detail.
score: 2

component CampaignROITable

file: src/cores/ce/components/analytics/CampaignROITable.tsx:54
kind: component
core: ce
spec: (none)
summary: Utility for campaign roitable.
score: 1

component CampaignsPage

file: src/cores/ce/pages/CampaignsPage.tsx:48
kind: component
core: ce
spec: (none)
summary: Utility for campaigns page.
score: 1

component CardCaptureSheet

file: src/cores/ce/components/mobile/CardCaptureSheet.tsx:60
kind: component
core: ce
spec: (none)
summary: Mobile field-capture sheet (manual entry + optional camera QR affordance).
score: 2

component CardPreview

file: src/cores/ce/components/connect/CardPreview.tsx:76
kind: component
core: ce
spec: (none)
summary: Read-only member-card preview. Renders only the fields that are present sothe layout stays stable as a card is filled in.
score: 2

component CardSharePanel

file: src/cores/ce/components/connect/CardSharePanel.tsx:35
kind: component
core: ce
spec: (none)
summary: Share controls for a member card: QR code, copy-link, and vCard download.
score: 2

component CEOverviewPage

file: src/cores/ce/pages/CEOverviewPage.tsx:26
kind: component
core: ce
spec: (none)
summary: CE (Community Engagement) Overview/Dashboard PageDisplays live metrics for contacts, leads, calls, and conversion rate.Includes keyboard shortcuts for Quick Dial (Cmd+D) and Log Call (Cmd+Shift+L).
score: 2

component CERecentActivityWidget

file: src/cores/ce/components/CERecentActivityWidget.tsx:34
kind: component
core: ce
spec: (none)
summary: Utility for cerecent activity widget.
score: 1

component CeSequenceBuilderWizardPage

file: src/cores/ce/wizards/sequences/CeSequenceBuilderWizardPage.tsx:27
kind: component
core: ce
spec: (none)
summary: Full-page wizard for creating automated follow-up sequences. Uses ModuleWizardRenderer (PF-41).
score: 2

component CeSequenceEnrollmentStep

file: src/cores/ce/wizards/sequences/steps/CeSequenceEnrollmentStep.tsx:17
kind: component
core: ce
spec: (none)
summary: Enrollment step: auto-enroll toggle + criteria JSON editor.
score: 2

component CeSequenceExitsStep

file: src/cores/ce/wizards/sequences/steps/CeSequenceExitsStep.tsx:16
kind: component
core: ce
spec: (none)
summary: Exit rules step: toggles for exit conditions.
score: 2

component CeSequenceStepBuilderStep

file: src/cores/ce/wizards/sequences/steps/CeSequenceStepBuilderStep.tsx:41
kind: component
core: ce
spec: (none)
summary: Step builder: add/remove/reorder sequence steps with channel-specific fields.
score: 2

component CESettingsForm

file: src/cores/ce/components/CESettingsForm.tsx:89
kind: component
core: ce
spec: (none)
summary: Utility for cesettings form.
score: 1

component CESettingsPage

file: src/cores/ce/pages/CESettingsPage.tsx:80
kind: component
core: ce
spec: (none)
summary: Renders the cesettings page interface.
score: 2

component CEWizardShortcutsWidget

file: src/cores/ce/components/CEWizardShortcutsWidget.tsx:74
kind: component
core: ce
spec: (none)
summary: Renders a card widget displaying wizard shortcut buttons for CE workflows.The widget includes quick-access buttons for common CE operations like creating leads,onboarding partners, importing contacts, and logging calls. Each button is permission-gatedand contextual shortcuts include tooltips explaining when they can be used.
params:
- props — Component props - onLogCall: Callback to invoke when the “Log Call” button is clicked
returns: A React element containing the wizard shortcuts card
example: | CEWizardShortcutsWidget onLogCall=() = setLogCallOpen(true) /
score: 4

component ComplianceSummaryCards

file: src/cores/ce/components/compliance/ComplianceSummaryCards.tsx:23
kind: component
core: ce
spec: CE-16
summary: Summary cards tallying suppression coverage across channels, counting all-channel, email, SMS,and phone suppressions (all-channel rolls into each per-channel total).
score: 3

component ConnectEmailAccountCard

file: src/cores/ce/components/email/ConnectEmailAccountCard.tsx:45
kind: component
core: ce
spec: (none)
summary: Utility for connect email account card.
score: 1

component ConnectHubPage

file: src/cores/ce/pages/ConnectHubPage.tsx:35
kind: component
core: ce
spec: (none)
summary: Connect hub page. Renders the digital business card tab strip via theshared primitive.
score: 2

component ConnectionStep

file: src/cores/ce/components/setup/steps/ConnectionStep.tsx:39
kind: component
core: ce
spec: (none)
summary: Render a setup step that guides the user through connecting a RingCentral account and creating a webhook subscription.Displays connection status, allows initiating a connection or testing credentials, and auto-advances when a subscription is active.Accessibility considerations:- Buttons are labeled with clear text and icons; ensure assistive tech can access the visible labels.- Success and informational alerts convey state changes visually and with text.
params:
- props — Component props - onNext: Callback invoked to advance to the next setup step - onBack: Callback invoked to return to the previous setup step
returns: The ConnectionStep UI as a React element
example: | ConnectionStep onNext=() = navigateNext() onBack=() = navigateBack() /
score: 4

component ConsentEvidenceTimeline

file: src/cores/ce/components/compliance/ConsentEvidenceTimeline.tsx:33
kind: component
core: ce
spec: CE-16
summary: Chronological timeline of a contact’s consent and withdrawal events, rendering skeletons whilethe audit-grade evidence loads.
score: 3

component ContactActivityTab

file: src/cores/ce/components/ContactActivityTab.tsx:22
kind: component
core: ce
spec: (none)
summary: Utility for contact activity tab.
score: 1

component ContactDetailPage

file: src/cores/ce/pages/ContactDetailPage.tsx:94
kind: component
core: ce
spec: (none)
summary: Renders the contact detail page with header, summary cards, tabbed content, and dialogs for editing and sending SMS.Displays a loading skeleton while fetching data, an error/empty state if the contact is unavailable, and the full detail UI when a contact is found. The UI includes click-to-call and send-SMS actions (when a phone number exists), summary cards (type, status, leads count, created date), tabs for overview, leads, calls, SMS, emails, and activity, and modal dialogs for editing the contact and composing SMS.
params:
- props — Component props (none)
returns: The rendered contact detail page element.
example: | ContactDetailPage /Accessibility considerations:- Back navigation, tab triggers, and action buttons are keyboard accessible.- Edit and SMS compose open in dialogs which should manage focus and be dismissible via keyboard.- Icons are presented alongside text labels to preserve meaning for screen reader users.
score: 4

component ContactDialog

file: src/cores/ce/components/ContactDialog.tsx:24
kind: component
core: ce
spec: (none)
summary: Utility for contact dialog.
score: 1

component ContactDocumentsTab

file: src/cores/ce/components/contacts/ContactDocumentsTab.tsx:70
kind: component
core: ce
spec: CE-59
summary: Contact-detail tab for managing uploaded documents, exposing upload, delete, and AI-extractionactions each gated by their respective permissions.
score: 3

component ContactDuplicatesPage

file: src/cores/ce/pages/ContactDuplicatesPage.tsx:155
kind: component
core: ce
spec: (none)
summary: Duplicate review queue: pending probabilistic match pairs with compare/merge/link/dismiss actions (CE-74).
score: 2

component ContactForm

file: src/cores/ce/components/ContactForm.tsx:60
kind: component
core: ce
spec: (none)
summary: Utility for contact form.
score: 1

component ContactHistoryTimeline

file: src/cores/ce/components/history/ContactHistoryTimeline.tsx:51
kind: component
core: ce
spec: CE-60
summary: Unified, filterable timeline of a contact’s history (activity, screenings, documents, stagechanges, profile updates) with date-preset, grouping, and paging controls.
score: 3

component ContactImportDialog

file: src/cores/ce/components/ContactImportDialog.tsx:51
kind: component
core: ce
spec: (none)
summary: Enhanced multi-step dialog for importing contacts from CSV with fuzzy duplicate detection.
score: 2

component ContactInfoCard

file: src/cores/ce/components/ContactInfoCard.tsx:39
kind: component
core: ce
spec: (none)
summary: Utility for contact info card.
score: 1

component ContactLeadsTab

file: src/cores/ce/components/ContactLeadsTab.tsx:40
kind: component
core: ce
spec: (none)
summary: Renders the contact leads tab interface.
score: 2

component ContactMergeDialog

file: src/cores/ce/components/identity/ContactMergeDialog.tsx:78
kind: component
core: ce
spec: (none)
summary: Merge confirmation dialog with survivorship field diff.
score: 2

component ContactRelationshipDialog

file: src/cores/ce/components/ContactRelationshipDialog.tsx:47
kind: component
core: ce
spec: CE-20
summary: Dialog for linking one contact to another by searching contacts and choosing a relationship typefrom the picklist before creating the link.
score: 3

component ContactRelationshipGraph

file: src/cores/ce/components/ContactRelationshipGraph.tsx:130
kind: component
core: ce
spec: CE-20
summary: Radial network graph of a contact’s relationships, computing node/edge positions from thesupplied network and navigating to a contact when its node is clicked.
score: 3

component ContactRelationshipsTab

file: src/cores/ce/components/ContactRelationshipsTab.tsx:37
kind: component
core: ce
spec: CE-20
summary: Contact-detail tab listing relationships with type and strength filters and (when is held) controls to add or delete links.
score: 3

component ContactsPage

file: src/cores/ce/pages/ContactsPage.tsx:32
kind: component
core: ce
spec: (none)
summary: Utility for contacts page.
score: 1

component ContactsTable

file: src/cores/ce/components/ContactsTable.tsx:52
kind: component
core: ce
spec: (none)
summary: Utility for contacts table.
score: 1

component ContactsTableSkeleton

file: src/cores/ce/components/ContactsTableSkeleton.tsx:10
kind: component
core: ce
spec: (none)
summary: Utility for contacts table skeleton.
score: 1

component ContactSuppressionSection

file: src/cores/ce/components/compliance/ContactSuppressionSection.tsx:30
kind: component
core: ce
spec: CE-16
summary: Contact-scoped panel showing the current suppression state with controls to add, edit, or (when is held) remove the suppression record.
score: 3

component ContactTagAssignmentField

file: src/cores/ce/components/contacts/ContactTagAssignmentField.tsx:34
kind: component
core: ce
spec: CE-61
summary: Field for viewing and editing the tags assigned to a contact, presenting a popover of availabletags and assigning/unassigning them when editing is permitted.
score: 3

component ContactTagBadge

file: src/cores/ce/components/contacts/ContactTagBadge.tsx:33
kind: component
core: ce
spec: CE-61
summary: Renders a single contact tag as a colour-filled badge with an accessible name, flagging alerttags with a warning icon and ring and optionally exposing a remove button.
score: 3

component ContactTagDialog

file: src/cores/ce/components/settings/ContactTagDialog.tsx:61
kind: component
core: ce
spec: CE-61
summary: Dialog for creating or editing a contact tag, capturing its name and colour and defaulting sortorder from when creating.
score: 3

component ContactTagsSettingsCard

file: src/cores/ce/components/settings/ContactTagsSettingsCard.tsx:211
kind: component
core: ce
spec: CE-61
summary: Settings card for managing the org’s contact tags, gating the editable inner card behind the permission.
score: 3

component ContractSetupStep

file: src/cores/ce/wizards/partner-onboarding/steps/ContractSetupStep.tsx:24
kind: component
core: ce
spec: (none)
summary: Step 4: Optional contract details.
score: 2

component CopyStagesFromTrackDialog

file: src/cores/ce/components/CopyStagesFromTrackDialog.tsx:30
kind: component
core: ce
spec: CE-64
summary: Dialog for seeding a pipeline track’s stages by cloning them from another track, offering onlytracks that already have stages as copy sources.
score: 3

component CrisisAlertCard

file: src/cores/ce/components/crisis/CrisisAlertCard.tsx:32
kind: component
core: ce
spec: CE-28
summary: Card for a single crisis alert showing its confidence tier and status, with acknowledge/resolveand escalate actions gated by ; supports a compact layout.
score: 3

component CrisisAlertMobileSheet

file: src/cores/ce/components/mobile/CrisisAlertMobileSheet.tsx:24
kind: component
core: ce
spec: CE-28
summary: Bottom sheet presenting a single crisis alert on mobile, wrapping in atouch-friendly drawer.
score: 3

component CrisisOnCallSettingsCard

file: src/cores/ce/components/crisis/CrisisOnCallSettingsCard.tsx:41
kind: component
core: ce
spec: CE-28
summary: Settings card for configuring crisis business hours and on-call rotations, gated by the and permissions.
score: 3

component CrisisQueueList

file: src/cores/ce/components/crisis/CrisisQueueList.tsx:26
kind: component
core: ce
spec: CE-28
summary: List of active crisis alerts for a given confidence tier, rendering skeletons while loading andforwarding escalation requests to the supplied handler.
score: 3

component CrisisQueueWidget

file: src/cores/ce/components/crisis/CrisisQueueWidget.tsx:23
kind: component
core: ce
spec: CE-28
summary: Dashboard widget summarising the crisis queue — active and unacknowledged counts plus the oldestunacknowledged alert — and linking through to the full queue.
score: 3

component DeleteContactDocumentDialog

file: src/cores/ce/components/contacts/DeleteContactDocumentDialog.tsx:26
kind: component
core: ce
spec: CE-59
summary: Confirmation dialog that soft-deletes a contact document by name, awaiting the mutation beforeclosing.
score: 3

component DeletePipelineTrackDialog

file: src/cores/ce/components/DeletePipelineTrackDialog.tsx:40
kind: component
core: ce
spec: CE-64
summary: Confirmation dialog for deleting a pipeline track that, when the track still holds leads,requires choosing another active track to reassign them to first.
score: 3

component DispositionPieChart

file: src/cores/ce/components/analytics/DispositionPieChart.tsx:85
kind: component
core: ce
spec: (none)
summary: Renders the disposition pie chart interface.
score: 2

component DncImportDialog

file: src/cores/ce/components/compliance/DncImportDialog.tsx:36
kind: component
core: ce
spec: CE-16
summary: Dialog for bulk-importing Do-Not-Contact entries from pasted CSV, invalidating suppressionqueries and surfacing a per-row import result on completion.
score: 3

component DuplicateComparisonCard

file: src/cores/ce/components/contacts/components/DuplicateComparisonCard.tsx:44
kind: component
core: ce
spec: (none)
summary: Displays imported row vs existing contact with field-level diff highlighting.
score: 2

component DuplicateContactWarning

file: src/cores/ce/components/DuplicateContactWarning.tsx:47
kind: component
core: ce
spec: (none)
summary: Warning banner listing possible duplicate contacts with match strength andmatched-field detail.
score: 2

component DuplicateReviewStep

file: src/cores/ce/components/contacts/import-steps/DuplicateReviewStep.tsx:38
kind: component
core: ce
spec: (none)
summary: Step 4: Review duplicate clusters with skip/merge/import actions.Shows comparison cards and supports bulk actions.
score: 2

component EmailAccountCard

file: src/cores/ce/components/email/EmailAccountCard.tsx:63
kind: component
core: ce
spec: (none)
summary: Utility for email account card.
score: 1

component EmailAccountSettings

file: src/cores/ce/components/email/EmailAccountSettings.tsx:40
kind: component
core: ce
spec: (none)
summary: Utility for email account settings.
score: 1

component EmailAccountsList

file: src/cores/ce/components/email/EmailAccountsList.tsx:31
kind: component
core: ce
spec: (none)
summary: Renders the email accounts list interface.
score: 2

component EmailComposeDialog

file: src/cores/ce/components/email/EmailComposeDialog.tsx:30
kind: component
core: ce
spec: (none)
summary: Utility for email compose dialog.
score: 1

component EmailComposeForm

file: src/cores/ce/components/email/EmailComposeForm.tsx:76
kind: component
core: ce
spec: (none)
summary: Utility for email compose form.
score: 1

component EmailDetailDialog

file: src/cores/ce/components/email/EmailDetailDialog.tsx:36
kind: component
core: ce
spec: (none)
summary: Utility for email detail dialog.
score: 1

component EmailSettingsCard

file: src/cores/ce/components/email/EmailSettingsCard.tsx:15
kind: component
core: ce
spec: (none)
summary: Utility for email settings card.
score: 1

component EmailSyncStatusWidget

file: src/cores/ce/components/dashboard/EmailSyncStatusWidget.tsx:28
kind: component
core: ce
spec: (none)
summary: Utility for email sync status widget.
score: 1

component EmailTemplateFormDialog

file: src/cores/ce/components/email/EmailTemplateFormDialog.tsx:45
kind: component
core: ce
spec: (none)
summary: Renders the email template form dialog interface.
score: 2

component EmailTemplateList

file: src/cores/ce/components/email/EmailTemplateList.tsx:30
kind: component
core: ce
spec: (none)
summary: Renders the email template list interface.
score: 2

component EmailTemplatesPage

file: src/cores/ce/pages/EmailTemplatesPage.tsx:13
kind: component
core: ce
spec: (none)
summary: Renders the email templates page interface.
score: 2

component EmailTimeline

file: src/cores/ce/components/email/EmailTimeline.tsx:56
kind: component
core: ce
spec: (none)
summary: Utility for email timeline.
score: 1

component EmailTimelineItem

file: src/cores/ce/components/email/EmailTimelineItem.tsx:25
kind: component
core: ce
spec: (none)
summary: Renders the email timeline item interface.
score: 2

component EmbeddableSettingsSection

file: src/cores/ce/components/settings/EmbeddableSettingsSection.tsx:55
kind: component
core: ce
spec: (none)
summary: Renders settings UI for configuring the RingCentral Embeddable softphone widget (CE-14).Displays toggles for enabling the embeddable widget, selecting its on-screen position with a live preview,preferring embeddable for click-to-call, and enabling contact info tabs. Also shows contextual alerts whenRingCentral integration or the required client ID is missing.
params:
- props — Component props - form: React Hook Form controller for CEModule settings () used to read and manipulate form state for embeddable settings. - ringcentralEnabled: Flag indicating whether RingCentral integration is enabled; when false, the embeddable controls are disabled and an informational alert is shown.
example: | EmbeddableSettingsSection form=settingsForm ringcentralEnabled=true/Accessibility:- Interactive controls include ARIA labels (e.g., “Enable Embeddable widget”, “Select widget position”) to aid assistive technologies.- Disable states and descriptive alerts communicate required prerequisites (integration and client ID) to users.
score: 4

component EmptyAnalyticsState

file: src/cores/ce/components/analytics/EmptyAnalyticsState.tsx:26
kind: component
core: ce
spec: (none)
summary: Renders the empty analytics state interface.
score: 2

component EnrollInSequenceDialog

file: src/cores/ce/components/sequences/EnrollInSequenceDialog.tsx:26
kind: component
core: ce
spec: none
summary: Dialog for enrolling a single lead/contact into a follow-up sequence, selecting the sequence andan optional start time.
score: 3

component EventFormDialog

file: src/cores/ce/components/events/EventFormDialog.tsx:49
kind: component
core: ce
spec: (none)
summary: Utility for event form dialog.
score: 1

component EventsPage

file: src/cores/ce/pages/EventsPage.tsx:25
kind: component
core: ce
spec: (none)
summary: Utility for events page.
score: 1

component ExportConfirmationDialog

file: src/cores/ce/components/ExportConfirmationDialog.tsx:31
kind: component
core: ce
spec: (none)
summary: Renders the export confirmation dialog interface.
score: 2

component ExportDropdown

file: src/cores/ce/components/analytics/ExportDropdown.tsx:35
kind: component
core: ce
spec: (none)
summary: Utility for export dropdown.
score: 1

component ExtensionMappingCard

file: src/cores/ce/components/settings/ExtensionMappingCard.tsx:27
kind: component
core: ce
spec: (none)
summary: Card component for managing RingCentral extension-to-user mappings
score: 2

component ExtensionMappingCard

file: src/cores/ce/components/setup/ExtensionMappingCard.tsx:90
kind: component
core: ce
spec: (none)
summary: Renders the extension mapping card interface.
score: 2

component ExtractedDocumentDataReviewDialog

file: src/cores/ce/components/contacts/ExtractedDocumentDataReviewDialog.tsx:52
kind: component
core: ce
spec: CE-59
summary: Dialog for reviewing AI-extracted document fields against the contact’s current values, lettingstaff accept or discard each suggestion before applying.
score: 3

component HistoryFetchError

file: src/cores/ce/components/history/HistoryEmptyStates.tsx:61
kind: component
core: ce
spec: CE-60
summary: Error state shown when the contact history query fails, surfacing the message and a retryaction.
score: 3

component HistoryFilterBar

file: src/cores/ce/components/history/HistoryFilterBar.tsx:53
kind: component
core: ce
spec: CE-60
summary: Filter bar for the contact history timeline, controlling the visible category set, date preset,and grouping mode via the supplied change callbacks.
score: 3

component HistoryNoMatches

file: src/cores/ce/components/history/HistoryEmptyStates.tsx:38
kind: component
core: ce
spec: CE-60
summary: Empty state shown when active filters exclude every history row, offering a reset action towiden the view.
score: 3

component HistoryNoneYet

file: src/cores/ce/components/history/HistoryEmptyStates.tsx:17
kind: component
core: ce
spec: CE-60
summary: Empty state shown when a contact has no recorded history yet.
score: 3

component HistoryRowSkeleton

file: src/cores/ce/components/history/HistoryRowSkeleton.tsx:18
kind: component
core: ce
spec: CE-60
summary: Loading placeholder for the contact history timeline, rendering a configurable number ofskeleton rows.
score: 3

component IdentityResolutionSettingsCard

file: src/cores/ce/components/settings/IdentityResolutionSettingsCard.tsx:29
kind: component
core: ce
spec: (none)
summary: Card for tuning duplicate-match thresholds and the merge undo window.
score: 2

component ImportHistoryPanel

file: src/cores/ce/components/contacts/components/ImportHistoryPanel.tsx:12
kind: component
core: ce
spec: (none)
summary: Stub component for import history. Full implementation requiresce_import_batches table (documented as errata in CE-UX-04 spec).
score: 2

component ImportProgressStep

file: src/cores/ce/components/contacts/import-steps/ImportProgressStep.tsx:20
kind: component
core: ce
spec: (none)
summary: Step 5: Real-time import progress with percentage, count, and scrollable error log.
score: 2

component InsuranceFieldsSection

file: src/cores/ce/components/InsuranceFieldsSection.tsx:39
kind: component
core: ce
spec: CE-65
summary: Masked insurance-fields panel that reveals or edits carrier and member-ID values only forpermitted users, auditing every reveal and edit via the insurance-reveal audit hook.
score: 3

component IntakeScreeningWizardPage

file: src/cores/ce/wizards/screening/IntakeScreeningWizardPage.tsx:28
kind: component
core: ce
spec: (none)
summary: Full-page wizard for intake screening. Uses ModuleWizardRenderer (PF-41).
score: 2

component KPIEntryStep

file: src/cores/ce/wizards/partner-progress-review/steps/KPIEntryStep.tsx:56
kind: component
core: ce
spec: (none)
summary: Step for entering KPI metrics: referrals, admissions, quality, response time.
score: 2

component LeadAdmitConfirmDialog

file: src/cores/ce/components/LeadAdmitConfirmDialog.tsx:29
kind: component
core: ce
spec: CE-63
summary: Confirmation dialog for admitting a lead into a terminal admit stage, committing the move viathe lead-mutations hook and notifying the caller on success or cancel.
score: 3

component LeadCard

file: src/cores/ce/components/LeadCard.tsx:36
kind: component
core: ce
spec: (none)
summary: Renders the lead card interface.
score: 2

component LeadCardAssigneeMenu

file: src/cores/ce/components/LeadCardAssigneeMenu.tsx:44
kind: component
core: ce
spec: CE-62
summary: Compact assignee menu on a pipeline lead card, letting users with reassign thelead to any active staff member or leave it unassigned.
score: 3

component LeadCardMetadata

file: src/cores/ce/components/LeadCardMetadata.tsx:57
kind: component
core: ce
spec: CE-65
summary: Renders the configured metadata rows on a pipeline lead card, building each tile field (stage,assignee, insurance, etc.) only when its value is present and applying insurance masking.
score: 3

component LeadClosureDialog

file: src/cores/ce/components/LeadClosureDialog.tsx:43
kind: component
core: ce
spec: CE-63
summary: Dialog for closing/losing a lead at a terminal closure stage, capturing the closure reasonbefore committing the stage move.
score: 3

component LeadConversionDialog

file: src/cores/ce/components/LeadConversionDialog.tsx:49
kind: component
core: ce
spec: (none)
summary: Dialog for converting a lead. Writes audit record to ce_lead_conversionsand publishes CE-29 granular events.
score: 2

component LeadConversionHistory

file: src/cores/ce/components/LeadConversionHistory.tsx:30
kind: component
core: ce
spec: (none)
summary: Shows conversion audit trail records for a lead.Permission-gated by ce.lead-conversions.view.
score: 2

component LeadConversionWizard

file: src/cores/ce/wizards/lead-conversion/LeadConversionWizard.tsx:30
kind: component
core: ce
spec: (none)
summary: Guided 4-step lead conversion wizard dialog.
score: 2

component LeadDetailAssigneeCard

file: src/cores/ce/components/LeadDetailAssigneeCard.tsx:33
kind: component
core: ce
spec: CE-62
summary: Lead-detail card showing the current assignee with avatar initials and, for users holding, controls to reassign the lead.
score: 3

component LeadDetailPage

file: src/cores/ce/pages/LeadDetailPage.tsx:148
kind: component
core: ce
spec: (none)
summary: Utility for lead detail page.
score: 1

component LeadDetailsStep

file: src/cores/ce/wizards/lead-intake/steps/LeadDetailsStep.tsx:31
kind: component
core: ce
spec: (none)
summary: Step 3 of the lead-intake wizard: captures expected admission date, urgency,pipeline track (defaulting to the service-resolved track but overridable —CE-64-EN-01 AC-1), requested services, and notes. Field changes flow up through.
params:
- data — the wizard’s current form data.
- errors — per-field validation errors for this step.
- onUpdate — setter that writes a single form field by key.
score: 2

component LeadIntakeWizard

file: src/cores/ce/wizards/lead-intake/LeadIntakeWizard.tsx:29
kind: component
core: ce
spec: (none)
summary: Guided 7-step lead intake wizard dialog (search-first, then create).
score: 2

component LeadPipelineBoard

file: src/cores/ce/components/LeadPipelineBoard.tsx:58
kind: component
core: ce
spec: (none)
summary: Utility for lead pipeline board.
score: 1

component LeadPipelineColumn

file: src/cores/ce/components/LeadPipelineColumn.tsx:27
kind: component
core: ce
spec: (none)
summary: Renders the lead pipeline column interface.
score: 2

component LeadPipelineFunnelChart

file: src/cores/ce/components/analytics/LeadPipelineFunnelChart.tsx:66
kind: component
core: ce
spec: (none)
summary: Renders the pipeline funnel chart interface.
score: 2

component LeadPipelinePage

file: src/cores/ce/pages/LeadPipelinePage.tsx:75
kind: component
core: ce
spec: (none)
summary: Utility for lead pipeline page.
score: 1

component LeadScheduledStageDialog

file: src/cores/ce/components/LeadScheduledStageDialog.tsx:40
kind: component
core: ce
spec: CE-63
summary: Dialog for moving a lead into a scheduled stage, capturing the schedule details beforecommitting the move via the lead-mutations hook.
score: 3

component LeadSequenceStatus

file: src/cores/ce/components/sequences/LeadSequenceStatus.tsx:25
kind: component
core: ce
spec: none
summary: Shows a lead’s follow-up sequence enrollments with pause/resume/exit controls for the activeenrollment and an entry point to enroll in a new sequence.
score: 3

component LeadStageEditor

file: src/cores/ce/components/LeadStageEditor.tsx:98
kind: component
core: ce
spec: (none)
summary: Renders the lead stage editor interface.
score: 2

component LeadStageFormDialog

file: src/cores/ce/components/LeadStageFormDialog.tsx:44
kind: component
core: ce
spec: (none)
summary: Utility for lead stage form dialog.
score: 1

component LeadStageProgression

file: src/cores/ce/components/LeadStageProgression.tsx:25
kind: component
core: ce
spec: (none)
summary: Renders the lead stage progression interface.
score: 2

component LeadTrackSelector

file: src/cores/ce/components/LeadTrackSelector.tsx:27
kind: component
core: ce
spec: CE-64
summary: Selector for moving a lead to a different pipeline track, ignoring no-op selections and trackingthe pending track while the change mutation runs.
score: 3

component LeadTrackTransferDialog

file: src/cores/ce/components/LeadTrackTransferDialog.tsx:43
kind: component
core: ce
spec: CE-64
summary: Dialog confirming transfer of a lead between pipeline tracks, summarising the source/targettracks and current stage before committing the move.
score: 3

component LeadUrgencyControl

file: src/cores/ce/components/LeadUrgencyControl.tsx:28
kind: component
core: ce
spec: (none)
summary: Lead Information card control for viewing and editing a lead’s urgency. Userswith get a Select that writes the change via (theaudit row is recorded by the trigger); everyone elsesees the urgency read-only (CE-58-EN-01 AC-1).
params:
- leadId — the lead whose urgency is shown/edited.
- urgency — the lead’s current urgency, or null when unset.
score: 2

component LinkContactToPartnerDialog

file: src/cores/ce/components/LinkContactToPartnerDialog.tsx:29
kind: component
core: ce
spec: (none)
summary: Utility for link contact to partner dialog.
score: 1

component M365CalendarPushSettingsCard

file: src/cores/ce/components/settings/M365CalendarPushSettingsCard.tsx:34
kind: component
core: ce
spec: (none)
summary: CE-73 AC-2 admin card. Per-tenant control for pushing follow-up tasks to theMicrosoft 365 calendar ( edge function). Mirrors. Admin-gated on .Settings (): - — master on/off (default OFF). - — ‘delegated’ | ‘application’. Application mode posts as the org Entra app and requires a one-time tenant admin consent. - — ‘assigned_coordinator’ | ‘per_task_override’. - — fallback mailbox when no coordinator/override.
score: 2

component MappingStep

file: src/cores/ce/components/contacts/import-steps/MappingStep.tsx:30
kind: component
core: ce
spec: (none)
summary: Step 2: Map CSV columns to contact fields with sample value preview.
score: 2

component MarketingHubPage

file: src/cores/ce/pages/MarketingHubPage.tsx:41
kind: component
core: ce
spec: (none)
summary: Marketing hub page. Renders the campaigns/events/sequences/SMS tab strip viathe shared primitive.
score: 2

component MemberCardsAdminPage

file: src/cores/ce/pages/connect/MemberCardsAdminPage.tsx:89
kind: component
core: ce
spec: (none)
summary: Admin roster page for org member cards.
score: 2

component MergedRecordBanner

file: src/cores/ce/components/identity/MergedRecordBanner.tsx:31
kind: component
core: ce
spec: (none)
summary: Informational banner indicating the displayed record absorbed a merge.
score: 2

component MergeFieldPicker

file: src/cores/ce/components/email/MergeFieldPicker.tsx:36
kind: component
core: ce
spec: (none)
summary: Renders the merge field picker interface.
score: 2

component MergeFieldPickerCompact

file: src/cores/ce/components/email/MergeFieldPicker.tsx:89
kind: component
core: ce
spec: (none)
summary: Compact merge field picker for inline use
score: 2

component MilestonesStep

file: src/cores/ce/wizards/partner-onboarding/steps/MilestonesStep.tsx:63
kind: component
core: ce
spec: (none)
summary: Step 5: Milestones selection and configuration.
score: 2

component MilestoneTracker

file: src/cores/ce/components/MilestoneTracker.tsx:100
kind: component
core: ce
spec: (none)
summary: Renders the milestone tracker interface.
score: 2

component MilestoneUpdateStep

file: src/cores/ce/wizards/partner-progress-review/steps/MilestoneUpdateStep.tsx:21
kind: component
core: ce
spec: (none)
summary: Step for tracking milestone completion/missed status.
score: 2

component MobileContactView

file: src/cores/ce/components/mobile/MobileContactView.tsx:87
kind: component
core: ce
spec: (none)
summary: Mobile contact list with search, pull-to-refresh, skeleton loading, and empty states.
score: 2

component MobileCrmShell

file: src/cores/ce/components/mobile/MobileCrmShell.tsx:20
kind: component
core: ce
spec: (none)
summary: Mobile CRM shell providing bottom nav, FAB, and offline indicator.On desktop (≥ md), renders children only (no mobile chrome).
score: 2

component MobilePartnerView

file: src/cores/ce/components/mobile/MobilePartnerView.tsx:38
kind: component
core: ce
spec: (none)
summary: Mobile partner list with search, pull-to-refresh, skeleton loading, and empty states.
score: 2

component MyCardPage

file: src/cores/ce/pages/connect/MyCardPage.tsx:123
kind: component
core: ce
spec: (none)
summary: Member-card editor page with a live preview and share panel.
score: 2

component NotesActionsStep

file: src/cores/ce/wizards/partner-progress-review/steps/NotesActionsStep.tsx:24
kind: component
core: ce
spec: (none)
summary: Step for discussion notes and repeatable action items.
score: 2

component OfflineQueueIndicator

file: src/cores/ce/components/mobile/OfflineQueueIndicator.tsx:17
kind: component
core: ce
spec: (none)
summary: Offline status banner and sync controls for mobile.Shows below bottom nav when offline or queue has pending items.
score: 2

component OnCallRotationFormDialog

file: src/cores/ce/components/crisis/OnCallRotationFormDialog.tsx:34
kind: component
core: ce
spec: CE-28
summary: Dialog for creating or editing an on-call rotation, capturing its name, escalation-minute tiers,and ordered member list before upserting.
score: 3

component PartnerActivityTab

file: src/cores/ce/components/PartnerActivityTab.tsx:22
kind: component
core: ce
spec: (none)
summary: Renders the partner activity tab interface.
score: 2

component PartnerComparisonTable

file: src/cores/ce/components/analytics/PartnerComparisonTable.tsx:58
kind: component
core: ce
spec: (none)
summary: Renders a side-by-side comparison table for up to five partners showing key metrics,best-value highlights, and per-partner warnings. If no partners are provided, displaysan empty state prompting the user to select partners.The table shows metric rows defined by METRICS, highlights the best numeric valuesfor total referrals, successful admissions, and success rate, and provides per-partnercontrols to remove a partner or clear all selections.Accessibility:- Removal buttons include descriptive s (e.g., “Remove name from comparison”).- Table structure uses semantic , , and elements for screen readers.
params:
- props — Component props - partners: Array of partner metrics to display (max visually supported: five). - onRemovePartner: Callback invoked with a partnerId when the corresponding partner’s remove button is clicked. - onClearAll: Callback invoked when the “Clear All” control is activated.
example: | PartnerComparisonTable partners=[ partnerId: ‘p1’, name: ‘Partner A’, totalReferrals: 10, successfulAdmissions: 4, successRate: 40, lastReferralDate: ‘2025-01-01’, relationshipStatus: ‘Active’, isDecliningSuccessRate: false, isDecliningVolume: false ] onRemovePartner=() = undefined onClearAll=() = undefined/
score: 4

component PartnerContactPersonDialog

file: src/cores/ce/components/PartnerContactPersonDialog.tsx:45
kind: component
core: ce
spec: (none)
summary: Standalone contact-person create/edit dialog for the partner contacts panel.
score: 2

component PartnerContactsPanel

file: src/cores/ce/components/PartnerContactsPanel.tsx:30
kind: component
core: ce
spec: (none)
summary: Renders the partner contacts panel interface.
score: 2

component PartnerContractDialog

file: src/cores/ce/components/PartnerContractDialog.tsx:90
kind: component
core: ce
spec: (none)
summary: Renders a dialog for creating or editing a partner contract, including fields forname, type, status, dates, value, auto-renew settings, terms, notes, and custom fields.When opened in edit mode (a is provided) the form is populated with thecontract’s values; otherwise the form is initialized with defaults. Submitting theform creates or updates the contract and closes the dialog on success. Errors areshown via a destructive toast.
params:
- props — Component props - partnerId: ID of the partner this contract belongs to; added to the payload on submit. - organizationId: ID of the organization used to scope mutations and included in the payload. - open: Controls whether the dialog is visible. - onOpenChange: Callback invoked when the dialog open state should change. - contract: Optional existing contract to edit; when provided the dialog operates in edit mode.
example: | PartnerContractDialog partnerId=“partner_123” organizationId=“org_456” open=isDialogOpen onOpenChange=(open) = setDialogOpen(open) contract=selectedContract/Accessibility:- Form controls use associated labels and the dialog receives focus when opened via the Dialog component.- Required fields are indicated in the UI (e.g., “Contract Type *”); ensure screen-reader announcements and focus order remain correct when the dialog is rendered in your app.
score: 4

component PartnerContractDocumentsStep

file: src/cores/ce/wizards/partner-contract/steps/PartnerContractDocumentsStep.tsx:19
kind: component
core: ce
spec: (none)
summary: Renders the document upload/selection step for the partner contract wizard.
score: 2

component PartnerContractsPanel

file: src/cores/ce/components/PartnerContractsPanel.tsx:55
kind: component
core: ce
spec: (none)
summary: Renders a panel that lists, creates, edits, and deletes contracts for a partner within an organization.Displays loading and error states, contract items with status badges, start/end dates, formatted values,expiration warnings, and provides Add, Edit, and Delete workflows via a contract dialog and a delete confirmation dialog.
params:
- props — Component props - partnerId: ID of the partner whose contracts are managed - organizationId: ID of the organization that owns the partner and contracts
returns: The PartnerContractsPanel React element
example: | PartnerContractsPanel partnerId=“partner_123” organizationId=“org_456” /Accessibility:- Action buttons include meaningful aria-labels (e.g., “Edit contract”, “Delete contract”).- Modal dialogs provide descriptive titles and follow accessible modal patterns (focus management and keyboard interaction).
score: 4

component PartnerContractWizardPage

file: src/cores/ce/wizards/partner-contract/PartnerContractWizardPage.tsx:25
kind: component
core: ce
spec: (none)
summary: Full-page wizard for creating partner contracts. Uses ModuleWizardRenderer (PF-41).
score: 2

component PartnerDetailPage

file: src/cores/ce/pages/PartnerDetailPage.tsx:88
kind: component
core: ce
spec: (none)
summary: Page that displays detailed information and interactive tools for a single partner.Renders loading and error states, a header with actions (call and edit), summary statistic cards,tabbed sections for overview, contacts, contracts, calls, activity, emails, and progress,and modal dialogs for editing the partner and logging progress.
params:
- props — This component does not accept props; it reads the partner from the routeand the current organization from context.
returns: JSX.Element — the partner detail page UI
example: | Route path=“/ce/partners/:id” element=PartnerDetailPage / /Accessibility considerations:- Navigation controls (back button, tab list, dialog openers) are rendered as semantic buttons/links.- External links open with rel=“noopener noreferrer” and target=“_blank”.- Ensure surrounding app-level focus management moves focus into dialogs when they open and returns focus to the triggering control on close.
score: 4

component PartnerDialog

file: src/cores/ce/components/PartnerDialog.tsx:19
kind: component
core: ce
spec: (none)
summary: Renders the partner dialog interface.
score: 2

component PartnerDocumentsPanel

file: src/cores/ce/components/PartnerDocumentsPanel.tsx:41
kind: component
core: ce
spec: CE-24
summary: Panel listing a partner’s documents with download and soft-delete actions, plus an upload flow(gated by ) supporting versioned supersession.
score: 3

component PartnerDocumentUploadDialog

file: src/cores/ce/components/PartnerDocumentUploadDialog.tsx:47
kind: component
core: ce
spec: CE-24
summary: Dialog for uploading a partner document, optionally tied to a contract or superseding anexisting version, with a default document type.
score: 3

component PartnerForm

file: src/cores/ce/components/PartnerForm.tsx:58
kind: component
core: ce
spec: (none)
summary: Renders the partner form interface.
score: 2

component PartnerHealthDashboardPage

file: src/cores/ce/pages/PartnerHealthDashboardPage.tsx:93
kind: component
core: ce
spec: (none)
summary: Renders the Partner Health dashboard used to monitor partner performance, summary statistics, recent progress updates, and navigation controls.The component reads the current organization from context, fetches dashboard data for a configurable date range, and displays:- Top-level stats (total partners, at-risk, off-track, exceeding)- Summary cards for on-track and no-recent-progress counts- A list of recent partner progress updates with status badges and navigation to partner details- A date-range selector and a “View All Partners” actionAccessibility:- Interactive list items are rendered as buttons for keyboard and screen reader accessibility.- Ensure surrounding layout provides appropriate focus order and visible focus styles.
params:
- props — This component does not accept props; it reads organization and configuration from context and internal state.
returns: The rendered Partner Health dashboard UI as a React element.
example: | PartnerHealthDashboardPage /
score: 4

component PartnerOnboardingWizard

file: src/cores/ce/wizards/partner-onboarding/PartnerOnboardingWizard.tsx:28
kind: component
core: ce
spec: (none)
summary: Full-page 6-step partner onboarding wizard.
score: 2

component PartnerProfileStep

file: src/cores/ce/wizards/partner-onboarding/steps/PartnerProfileStep.tsx:21
kind: component
core: ce
spec: (none)
summary: Step 1: Partner profile details.
score: 2

component PartnerProgressReviewWizard

file: src/cores/ce/wizards/partner-progress-review/PartnerProgressReviewWizard.tsx:29
kind: component
core: ce
spec: (none)
summary: Guided 5-step partner progress review wizard dialog.
score: 2

component PartnerProgressTimeline

file: src/cores/ce/components/PartnerProgressTimeline.tsx:85
kind: component
core: ce
spec: (none)
summary: Utility for partner progress timeline.
score: 1

component PartnerScorecard

file: src/cores/ce/components/analytics/PartnerScorecard.tsx:136
kind: component
core: ce
spec: (none)
summary: Renders the Partner Scorecard UI for browsing, sorting, filtering, and comparing partner performance metrics.Shows summary metrics, a table of partners with sortable columns, filters for relationship status and minimum referrals,and an optional compare mode that lets users select up to five partners for side-by-side comparison.Accessibility:- Interactive controls (buttons, selects, checkboxes) use semantic components and should be reachable by keyboard.- Table rows are clickable for navigation when compare mode is off; checkbox cells stop propagation to avoid accidental navigation.
params:
- props — Component props - className: Optional container className passed to the top-level element for layout or styling overrides
returns: The Partner Scorecard UI as a React element
example: | PartnerScorecard className=“max-w-7xl mx-auto” /
score: 4

component PartnerScorecardPage

file: src/cores/ce/pages/PartnerScorecardPage.tsx:27
kind: component
core: ce
spec: (none)
summary: Renders the Partner Scorecard page wrapped by a permission gate.Renders a page header (title, description, users icon) with an export actions dropdown and the PartnerScorecard analytics content. The page is only shown to users with the “ce.scorecard.view” permission; the export action requires “ce.scorecard.export”.
returns: The page’s JSX element.
example: | PartnerScorecardPage /Accessibility: Header controls and the export dropdown should be keyboard operable and provide descriptive labels for screen readers.
score: 5

component PartnerSelector

file: src/cores/ce/components/PartnerSelector.tsx:63
kind: component
core: ce
spec: (none)
summary: A searchable dropdown for selecting an organization partner.Renders a combobox button that opens a popover containing a searchable list of active partners. Selecting an item calls with the partner’s id and closes the popover; choosing the clear option calls and closes the popover.
params:
- props — Component props - organizationId: ID of the organization whose partners should be listed - value: Currently selected partner id, or when no partner is selected - onChange: Callback invoked when the selection changes; receives the selected partner id or when cleared - placeholder: Placeholder text shown when no partner is selected (default: ) - disabled: When true, disables interaction with the combobox (default: ) - className: Optional additional CSS class names applied to the trigger buttonAccessibility:- The trigger button exposes and to convey open/closed state to assistive technologies.Search behavior:- The list is filtered by the search input; filtering is applied once the query has at least two characters.
example: | PartnerSelector organizationId=“org_123” value=selectedPartnerId onChange=(id) = setSelectedPartnerId(id)/
score: 4

component PartnersPage

file: src/cores/ce/pages/PartnersPage.tsx:45
kind: component
core: ce
spec: (none)
summary: Renders the Partners management page for the current organization.Displays header controls, search and filter inputs, the partners table (or an empty / error state),and the partner create/edit dialog. The entire UI is gated by the “ce.partners.view” permission.Accessibility: form controls and action buttons are standard interactive elements and should be reachablevia keyboard; ensure surrounding app provides appropriate focus management when the PartnerDialog opens.
params:
- props — This component accepts no props.
returns: The page JSX for viewing and managing referral partners for the active organization.
example: | PartnersPage /
score: 4

component PartnersTable

file: src/cores/ce/components/PartnersTable.tsx:29
kind: component
core: ce
spec: (none)
summary: Renders the partners table interface.
score: 2

component PartnersTableSkeleton

file: src/cores/ce/components/PartnersTable.tsx:176
kind: component
core: ce
spec: (none)
summary: Renders the partners table skeleton interface.
score: 2

component PayerMultiSelect

file: src/cores/ce/components/PayerMultiSelect.tsx:27
kind: component
core: ce
spec: (none)
summary: Renders the partner accepted-insurance multi-select (chips + add dropdown).
score: 2

component PipelineDashboard

file: src/cores/ce/components/analytics/PipelineDashboard.tsx:90
kind: component
core: ce
spec: (none)
summary: Dashboard that displays lead pipeline metrics including KPI cards, a funnel visualization, and stage conversion rates with drill-down navigation.Renders a date-range toggle, refresh controls, summary KPI cards (total leads, conversion rate, average days to convert, lost leads), a funnel chart of pipeline stages (clickable to navigate to filtered leads), and per-stage conversion progress bars when multiple stages exist.Accessibility:- Progress bars include ARIA attributes (, , , , and descriptive ) to expose conversion rates to assistive technologies.- Date range toggle items include values for screen reader context.
params:
- props — Component props - className: Optional container CSS class names applied to the root element
example: | PipelineDashboard className=“space-y-6” /
score: 4

component PipelineDashboardPage

file: src/cores/ce/pages/PipelineDashboardPage.tsx:17
kind: component
core: ce
spec: (none)
summary: Utility for pipeline dashboard page.
score: 1

component PipelineTagsProvider

file: src/cores/ce/components/pipeline/PipelineTagsProvider.tsx:15
kind: component
core: ce
spec: CE-61
summary: Context provider that shares a per-contact tag map across the pipeline board so tag chips andalert flags render without per-card queries.
score: 3

component PipelineTrackFormDialog

file: src/cores/ce/components/PipelineTrackFormDialog.tsx:56
kind: component
core: ce
spec: CE-64
summary: Dialog for creating or editing a pipeline track, defaulting new tracks to clone stages from theorg’s default track and persisting via the track-mutations hook.
score: 3

component PrerequisitesStep

file: src/cores/ce/components/setup/steps/PrerequisitesStep.tsx:55
kind: component
core: ce
spec: (none)
summary: Renders a setup step that verifies RingCentral API credentials are present in cloud secrets and presents status, guidance, and actions.Displays three credential checks (Client ID, Client Secret, JWT Token), a contextual tip, and contextual alerts when checks fail or all prerequisites are met. Provides actions to re-check the prerequisites and to continue when all required secrets are configured. - prerequisites: Object containing boolean flags for each credential and which is true when every required credential is present. - isLoading: When true, shows skeleton placeholders while the check is in progress. - error: An Error object to display when the prerequisite check fails; when present the component shows a destructive error alert and a retry action. - onRefresh: Callback invoked to re-run the prerequisites check (Retry / Re-check button). - onNext: Callback invoked to proceed to the next step (Continue button). This action is disabled until all prerequisites are configured.Accessibility considerations:- Action buttons use clear, descriptive labels and focusable controls.- External links open in a new tab with proper rel attributes to preserve security and context.
returns: The rendered step UI as a JSX element.
example: | PrerequisitesStep prerequisites= clientId: true, clientSecret: true, jwtToken: false, allConfigured: false, isLoading=false error=null onRefresh=() = checkPrereqs() onNext=() = goToNextStep()/
score: 5

component PrimaryContactStep

file: src/cores/ce/wizards/partner-onboarding/steps/PrimaryContactStep.tsx:30
kind: component
core: ce
spec: (none)
summary: Step 2: Select existing contact or create new.
score: 2

component ProgressUpdateForm

file: src/cores/ce/components/ProgressUpdateForm.tsx:86
kind: component
core: ce
spec: (none)
summary: Form component for creating or editing a partner’s progress record with validation and milestone management.Renders a controlled form (using React Hook Form and a Zod schema) to log or update KPIs, status, milestones, notes, and the reporting period for a specific partner within the current organization.
params:
- props — Component props - partnerId: The partner’s unique identifier to associate the progress record with. - partnerType: The partner’s type (used to load relevant milestones). - partnerName: Display name shown in the form header. - editRecord: Optional existing progress record to prefill the form for editing. - onSuccess: Optional callback invoked after a successful create or update. - onCancel: Optional callback invoked when the user cancels the form. - className: Optional container class name for styling.
example: | ProgressUpdateForm partnerId=“partner_123” partnerType=“facility” partnerName=“Sunrise Clinic” onSuccess=() = undefined onCancel=() = undefined/Accessibility considerations:- Date picker disables future dates and exposes the selected date textually; form controls include labels and descriptive messages for screen readers.- Milestone checkboxes are keyboard-focusable and use visible labels to convey state.
score: 4

component PublicCardPage

file: src/cores/ce/pages/connect/PublicCardPage.tsx:119
kind: component
core: ce
spec: (none)
summary: Public, unauthenticated card page with a “save contact” action and avisitor capture form.
score: 2

component QuickLogFAB

file: src/cores/ce/components/mobile/QuickLogFAB.tsx:24
kind: component
core: ce
spec: (none)
summary: Floating Action Button for quick activity logging.Shows pending badge when offline queue has items.
score: 2

component QuickLogForm

file: src/cores/ce/components/mobile/QuickLogForm.tsx:234
kind: component
core: ce
spec: (none)
summary: Quick log form — renders as bottom sheet on mobile, dialog on desktop.
score: 2

component ReferralAttemptDialog

file: src/cores/ce/components/ReferralAttemptDialog.tsx:40
kind: component
core: ce
spec: (none)
summary: Renders the log-referral-attempt dialog.
score: 2

component ReferralAttemptsTable

file: src/cores/ce/components/ReferralAttemptsTable.tsx:17
kind: component
core: ce
spec: (none)
summary: Renders the referral-attempt ledger table for a partner.
score: 2

component ReferralLedgerPanel

file: src/cores/ce/components/ReferralLedgerPanel.tsx:25
kind: component
core: ce
spec: (none)
summary: Renders the partner referral ledger panel (attempts table + gated log button).The Incoming/Outbound summary is derived live from the loaded attempts viaaggregateDirectionalCounts — the same per-direction reconciliation thece_partners trigger applies — so the panel reflects the in-cache ledger(incl. an attempt just logged in this panel) without re-querying the partnerrow, which lags until its TanStack cache entry is invalidated.
score: 2

component ReferralSourceDialog

file: src/cores/ce/components/ReferralSourceDialog.tsx:41
kind: component
core: ce
spec: (none)
summary: Utility for referral source dialog.
score: 1

component ReferralSourceManagement

file: src/cores/ce/components/ReferralSourceManagement.tsx:33
kind: component
core: ce
spec: (none)
summary: Renders the referral source management interface.
score: 2

component ReferralSourcesPage

file: src/cores/ce/pages/ReferralSourcesPage.tsx:14
kind: component
core: ce
spec: (none)
summary: Utility for referral sources page.
score: 1

component RequestedServicesMultiSelect

file: src/cores/ce/components/RequestedServicesMultiSelect.tsx:36
kind: component
core: ce
spec: CE-58
summary: Multi-select bound to the picklist for capturing the services a lead isinquiring about.
score: 3

component ResultsStep

file: src/cores/ce/components/contacts/import-steps/ResultsStep.tsx:34
kind: component
core: ce
spec: (none)
summary: Step 6: Import results with summary, error export, and done action.
score: 2

component ReviewPeriodStep

file: src/cores/ce/wizards/partner-progress-review/steps/ReviewPeriodStep.tsx:20
kind: component
core: ce
spec: (none)
summary: Step for selecting review period type and date range.
score: 2

component ReviewStep

file: src/cores/ce/wizards/lead-intake/steps/ReviewStep.tsx:28
kind: component
core: ce
spec: (none)
summary: Lead-intake wizard final step: read-only summary of every captured field withjump-back links so the coordinator can correct a section before submitting.
score: 2

component ReviewStep

file: src/cores/ce/wizards/partner-onboarding/steps/ReviewStep.tsx:35
kind: component
core: ce
spec: (none)
summary: Step 6: Review all data before submission.
score: 2

component RingCentralConnectionCard

file: src/cores/ce/components/settings/RingCentralConnectionCard.tsx:26
kind: component
core: ce
spec: (none)
summary: Displays and manages the RingCentral webhook connection status and actions.Renders loading, error, and normal states returned by the RingCentral setup hook and provides actionsto connect, test, refresh, and disconnect the integration. When connected, shows a brief subscriptionsummary including ID, expiration, and event filter count.Accessibility:- Action buttons are keyboard-focusable and provide visible labels for screen readers.- Status badges and alerts convey connection state and errors using text and icons.
example: | RingCentralConnectionCard /
score: 5

component RingCentralSetupPage

file: src/cores/ce/pages/RingCentralSetupPage.tsx:20
kind: component
core: ce
spec: (none)
summary: Page wrapper that hosts the RingCentral integration setup wizard.Renders the RingCentral setup wizard inside the application’s PageContainer to provide consistent layout and spacing.Accessibility: Placeholders and focus management should be handled by the contained RingCentralSetupWizard; this component preserves semantic structure for screen readers by using the app’s PageContainer.
example: | Route path=“/integrations/ringcentral” element=RingCentralSetupPage / /
score: 5

component RingCentralSetupWizard

file: src/cores/ce/components/setup/RingCentralSetupWizard.tsx:47
kind: component
core: ce
spec: (none)
summary: Renders a guided five-step wizard for configuring RingCentral telephony integration.Uses shared WizardShell (timeline layout) for consistent progress and navigation.
score: 2

component ScheduledLeadsPanel

file: src/cores/ce/components/ScheduledLeadsPanel.tsx:32
kind: component
core: ce
spec: CE-65
summary: Collapsible panel listing leads with upcoming scheduled stages within a rolling window, linkingeach to its lead detail.
score: 3

component ScheduledSmsList

file: src/cores/ce/components/sms/ScheduledSmsList.tsx:42
kind: component
core: ce
spec: (none)
summary: List queued/historical scheduled SMS with cancel controls.
score: 2

component ScheduleMeetingDialog

file: src/cores/ce/components/ScheduleMeetingDialog.tsx:84
kind: component
core: ce
spec: CE-21
summary: Dialog for scheduling a meeting against an activity through a connected calendar, selecting thecalendar connection and attendees before booking.
score: 3

component ScheduleSmsDialog

file: src/cores/ce/components/sms/ScheduleSmsDialog.tsx:42
kind: component
core: ce
spec: (none)
summary: Schedule an SMS for future delivery with TCPA-aware consent gates.
score: 2

component ScreeningDispositionStep

file: src/cores/ce/wizards/screening/steps/ScreeningDispositionStep.tsx:31
kind: component
core: ce
spec: (none)
summary: Renders disposition selection with conditional escalation and follow-up fields.
score: 2

component ScreeningForm

file: src/cores/ce/components/screening/ScreeningForm.tsx:75
kind: component
core: ce
spec: (none)
summary: Screening form for intake assessment with triage computation.
score: 2

component ScreeningFormSkeleton

file: src/cores/ce/components/screening/ScreeningFormSkeleton.tsx:11
kind: component
core: ce
spec: (none)
summary: Skeleton placeholder for the screening form while loading.
score: 2

component ScreeningHistory

file: src/cores/ce/components/screening/ScreeningHistory.tsx:29
kind: component
core: ce
spec: (none)
summary: Renders the screening attempt history for a given lead.
score: 2

component ScreeningPage

file: src/cores/ce/pages/ScreeningPage.tsx:20
kind: component
core: ce
spec: (none)
summary: Page component for conducting intake screening on a lead.
score: 2

component ScreeningQuestionnaireStep

file: src/cores/ce/wizards/screening/steps/ScreeningQuestionnaireStep.tsx:32
kind: component
core: ce
spec: (none)
summary: Renders the dynamic questionnaire for the selected program type.
score: 2

component ScreeningTriageResult

file: src/cores/ce/components/screening/ScreeningTriageResult.tsx:26
kind: component
core: ce
spec: (none)
summary: Displays the computed triage result from screening questionnaire responses.
score: 2

component ScreeningTriageSummaryStep

file: src/cores/ce/wizards/screening/steps/ScreeningTriageSummaryStep.tsx:41
kind: component
core: ce
spec: (none)
summary: Displays computed triage and requires acknowledgment for critical flags.
score: 2

component SegmentCriteriaBuilder

file: src/cores/ce/components/segments/SegmentCriteriaBuilder.tsx:37
kind: component
core: ce
spec: (none)
summary: Utility for segment criteria builder.
score: 1

component SegmentFormDialog

file: src/cores/ce/components/segments/SegmentFormDialog.tsx:52
kind: component
core: ce
spec: (none)
summary: Utility for segment form dialog.
score: 1

component SegmentsPage

file: src/cores/ce/pages/SegmentsPage.tsx:23
kind: component
core: ce
spec: (none)
summary: Renders the segments page interface.
score: 2

component SequenceAnalyticsTab

file: src/cores/ce/components/sequences/SequenceAnalyticsTab.tsx:66
kind: component
core: ce
spec: (none)
summary: Renders sequence enrollment KPIs and exit reason analytics for a sequence.
params:
- enrollments — Sequence enrollments including status/timestamps and optional display names (, ) used for CSV export.
returns: Analytics cards for completion/engagement/enrollment counts, exit-reason distribution bars, and CSV export output from .
score: 2

component SequenceForm

file: src/cores/ce/components/sequences/SequenceForm.tsx:88
kind: component
core: ce
spec: (none)
summary: SequenceForm renders create/edit controls for CE-13 sequence metadata and enrollment behavior.
params:
- initialValue — Optional sequence to edit; when present it seeds including JSON and .
- onSubmit — Submit handler receiving validated ; includes JSON text for .
- submitting — When true, disables the submit button and shows saving state.
returns: JSX.Element containing sequence fields, enrollment toggles, and conditional criteria JSON input.
score: 2

component SequenceSettingsTab

file: src/cores/ce/components/sequences/SequenceSettingsTab.tsx:36
kind: component
core: ce
spec: none
summary: Settings tab editing the org-level follow-up sequence module settings, loading the current row into an editable draft.
score: 3

component SequenceStepBuilder

file: src/cores/ce/components/sequences/SequenceStepBuilder.tsx:30
kind: component
core: ce
spec: (none)
summary: SequenceStepBuilder manages create/edit/delete/reorder controls for sequence steps.
params:
- steps — Ordered sequence steps to render and reorder.
- onCreateStep — Called when the user adds a new step by type.
- onUpdateStep — Called when edits are saved from .
- onDeleteStep — Called when a step is removed.
- onReorderStepIds — Called with reordered step ids from drag-and-drop.
returns: Step list UI with desktop drag-and-drop controls and a mobile read-only fallback.
score: 2

component SequenceStepBuilderDesktopDnd

file: src/cores/ce/components/sequences/SequenceStepBuilderDesktopDnd.tsx:19
kind: component
core: ce
spec: none
summary: Desktop drag-and-drop wrapper for the sequence step builder, reordering step ids on drop(ignoring no-op drags) and exposing edit/delete per step.
score: 3

component SlaComplianceDashboard

file: src/cores/ce/components/screening/SlaComplianceDashboard.tsx:18
kind: component
core: ce
spec: (none)
summary: SLA Compliance Dashboard showing screening SLA performance.
score: 2

component SlaIndicator

file: src/cores/ce/wizards/screening/components/SlaIndicator.tsx:23
kind: component
core: ce
spec: (none)
summary: Displays SLA compliance status for the current screening.
score: 2

component SlaStatusBadge

file: src/cores/ce/components/screening/SlaStatusBadge.tsx:18
kind: component
core: ce
spec: (none)
summary: Renders an SLA status badge with semantic colors.
score: 2

component SmsComposeDialog

file: src/cores/ce/components/sms/SmsComposeDialog.tsx:55
kind: component
core: ce
spec: (none)
summary: Utility for sms compose dialog.
score: 1

component SmsComposeInput

file: src/cores/ce/components/sms/SmsComposeInput.tsx:53
kind: component
core: ce
spec: (none)
summary: Renders the sms compose input interface.
score: 2

component SmsConfigStep

file: src/cores/ce/components/setup/steps/SmsConfigStep.tsx:56
kind: component
core: ce
spec: (none)
summary: Renders the SMS Configuration step used to select an SMS provider, enter the provider phone number, and toggle PHI detection.Presents a selectable provider (None, RingCentral), validates the RingCentral phone number in E.164 format when required, and persists settings via the app’s SMS settings hook. When “None” is selected the step can be skipped without saving.Accessibility:- Associates labels with form controls via /.- Exposes validation state using and for the phone input.
params:
- props — Component props - onNext: Callback invoked when the step completes successfully (or is skipped) - onBack: Callback invoked when the user navigates to the previous step
returns: The rendered JSX element for the SMS configuration step.
example: | SmsConfigStep onNext=() = console.log(‘advance’) onBack=() = console.log(‘go back’)/
score: 4

component SmsConsentBadge

file: src/cores/ce/components/sms/SmsConsentBadge.tsx:76
kind: component
core: ce
spec: (none)
summary: Utility for sms consent badge.
score: 1

component SmsConsentIndicator

file: src/cores/ce/components/sms/SmsConsentBadge.tsx:139
kind: component
core: ce
spec: (none)
summary: Utility for sms consent indicator.
score: 1

component SmsConsentPage

file: src/cores/ce/pages/SmsConsentPage.tsx:25
kind: component
core: ce
spec: (none)
summary: Utility for sms consent page.
score: 1

component SmsConsentStatusDialog

file: src/cores/ce/components/sms/SmsConsentStatusDialog.tsx:54
kind: component
core: ce
spec: (none)
summary: Utility for sms consent status dialog.
score: 1

component SmsConsentTable

file: src/cores/ce/components/sms/SmsConsentTable.tsx:51
kind: component
core: ce
spec: (none)
summary: Utility for sms consent table.
score: 1

component SmsConversation

file: src/cores/ce/components/sms/SmsConversation.tsx:29
kind: component
core: ce
spec: (none)
summary: Utility for sms conversation.
score: 1

component SmsConversationPanel

file: src/cores/ce/components/sms/SmsConversationPanel.tsx:36
kind: component
core: ce
spec: (none)
summary: Utility for sms conversation panel.
score: 1

component SmsConversationsPage

file: src/cores/ce/pages/SmsConversationsPage.tsx:35
kind: component
core: ce
spec: (none)
summary: CE-08 SMS queue page for monitoring active message threads and sending replies.Supports phone/contact-scoped filtering, realtime inbound/outbound message updates,PHI guardrails before send, and retry for the latest failed outbound message.
score: 2

component SmsMergeFieldPicker

file: src/cores/ce/components/sms/SmsMergeFieldPicker.tsx:56
kind: component
core: ce
spec: (none)
summary: Renders the sms merge field picker interface.
score: 2

component SmsMessageBubble

file: src/cores/ce/components/sms/SmsMessageBubble.tsx:38
kind: component
core: ce
spec: (none)
summary: Utility for sms message bubble.
score: 1

component SmsNotificationProvider

file: src/cores/ce/providers/SmsNotificationProvider.tsx:16
kind: component
core: ce
spec: (none)
summary: Provider that enables real-time SMS notification toasts.Returns null (short-circuits) if RealtimeProvider context is not available,preventing SmsNotificationInner and its useSmsNotifications hook from mounting.
score: 2

component SmsNotificationToast

file: src/cores/ce/components/sms/SmsNotificationToast.tsx:41
kind: component
core: ce
spec: (none)
summary: SMS notification toast content
score: 2

component SmsPhiWarning

file: src/cores/ce/components/sms/SmsPhiWarning.tsx:60
kind: component
core: ce
spec: (none)
summary: Renders the sms phi warning interface.
score: 2

component SmsPhiWarningInline

file: src/cores/ce/components/sms/SmsPhiWarning.tsx:122
kind: component
core: ce
spec: (none)
summary: Renders the sms phi warning inline interface.
score: 2

component SmsRoutingRulesManager

file: src/cores/ce/components/sms/SmsRoutingRulesManager.tsx:24
kind: component
core: ce
spec: (none)
summary: EN-05: Multi-number routing rules manager.Lets admins map sender phone numbers to a department/program/site targetwith priority + default-fallback configuration.
score: 2

component SmsSchedulePicker

file: src/cores/ce/components/sms/SmsSchedulePicker.tsx:18
kind: component
core: ce
spec: CE-08
summary: Date-time picker for scheduling an outbound SMS, normalising the chosen value to an ISOtimestamp and guarding against double-submission while scheduling.
score: 3

component SmsSettingsTab

file: src/cores/ce/components/settings/SmsSettingsTab.tsx:31
kind: component
core: ce
spec: (none)
summary: Renders provider, retention, compliance, and business-hour SMS module settings.
score: 2

component SmsTemplateForm

file: src/cores/ce/components/sms/SmsTemplateForm.tsx:61
kind: component
core: ce
spec: (none)
summary: Utility for sms template form.
score: 1

component SmsTemplateFormSkeleton

file: src/cores/ce/components/sms/SmsTemplateForm.tsx:284
kind: component
core: ce
spec: (none)
summary: Utility for sms template form skeleton.
score: 1

component SmsTemplateList

file: src/cores/ce/components/sms/SmsTemplateList.tsx:26
kind: component
core: ce
spec: (none)
summary: Utility for sms template list.
score: 1

component SmsTemplateListSkeleton

file: src/cores/ce/components/sms/SmsTemplateList.tsx:274
kind: component
core: ce
spec: (none)
summary: Utility for sms template list skeleton.
score: 1

component SmsTemplatesPage

file: src/cores/ce/pages/SmsTemplatesPage.tsx:14
kind: component
core: ce
spec: (none)
summary: Renders the sms templates page interface.
score: 2

component StageHeaderLeadsPopover

file: src/cores/ce/components/StageHeaderLeadsPopover.tsx:33
kind: component
core: ce
spec: (none)
summary: Pipeline stage-header popover listing the leads currently in a stage,colour-coded by urgency and each clickable to open the lead profile. Opens onhover and keyboard focus and renders from already-loaded board data, so it addsno extra fetch (CE-58-EN-01 AC-3). Renders nothing when the stage is empty.
params:
- stageName — the stage’s display name, used in the trigger label.
- leads — the leads in this stage, already loaded by the board.
- defaultOpen — test-only; render the popover content open.
score: 2

component StepCard

file: src/cores/ce/components/sequences/StepCard.tsx:22
kind: component
core: ce
spec: none
summary: Compact card summarising a single follow-up sequence step, choosing an icon and label from thestep’s type.
score: 3

component StepConfigDialog

file: src/cores/ce/components/sequences/StepConfigDialog.tsx:27
kind: component
core: ce
spec: (none)
summary: StepConfigDialog edits an individual sequence step and returns the updated with -specific content fields.
params:
- open — Controlled open state for the dialog.
- onOpenChange — Callback used to open/close the dialog from the parent.
- initialStep — Initial snapshot used to seed local form state.
- onSave — Called with the locally edited step when the user saves.
returns: JSX element rendering a step configuration dialog with type-specific content fields.
score: 2

component SubmitScheduleStep

file: src/cores/ce/wizards/partner-progress-review/steps/SubmitScheduleStep.tsx:22
kind: component
core: ce
spec: (none)
summary: Read-only summary with edit links and next check-in scheduling.
score: 2

component SuppressionTable

file: src/cores/ce/components/compliance/SuppressionTable.tsx:68
kind: component
core: ce
spec: CE-16
summary: Tabular list of contact suppression records showing the contact, suppressed channels, andreason, with a delete action gated by .
score: 3

component SuppressionTableSkeleton

file: src/cores/ce/components/compliance/SuppressionTable.tsx:39
kind: component
core: ce
spec: CE-16
summary: Loading-state placeholder for , rendering skeleton rows whilesuppression data is fetched.
score: 3

component TagFilterControl

file: src/cores/ce/components/pipeline/TagFilterControl.tsx:35
kind: component
core: ce
spec: CE-61
summary: Control for filtering the pipeline by contact tags, toggling tag selection and switching betweenany/all match modes.
score: 3

component TileFieldConfigCard

file: src/cores/ce/components/settings/TileFieldConfigCard.tsx:149
kind: component
core: ce
spec: CE-65
summary: Settings card for configuring which metadata tile fields appear on pipeline lead cards, gatedbehind the permission.
score: 3

component TrackPipelineRow

file: src/cores/ce/components/TrackPipelineRow.tsx:51
kind: component
core: ce
spec: CE-64
summary: Renders one pipeline track as a collapsible row of stage columns, accented by the track colourand optionally hiding the collapse control for terminal/virtual rows.
score: 3

component UploadContactDocumentDialog

file: src/cores/ce/components/contacts/UploadContactDocumentDialog.tsx:49
kind: component
core: ce
spec: CE-59
summary: Dialog for uploading a contact document, capturing a display name and type and enforcing theconfigured maximum file size before upload.
score: 3

component UploadStep

file: src/cores/ce/components/contacts/import-steps/UploadStep.tsx:30
kind: component
core: ce
spec: (none)
summary: Step 1: File upload with drag & drop, template download, and file info display.
score: 2

component UserMappingStep

file: src/cores/ce/components/setup/steps/UserMappingStep.tsx:74
kind: component
core: ce
spec: (none)
summary: Renders the user mapping step interface.
score: 2

component ValidationStep

file: src/cores/ce/components/contacts/import-steps/ValidationStep.tsx:19
kind: component
core: ce
spec: (none)
summary: Step 3: Display validation results — valid/invalid row counts and error details.
score: 2

component VerificationStep

file: src/cores/ce/components/setup/steps/VerificationStep.tsx:41
kind: component
core: ce
spec: (none)
summary: Renders the final verification step of the RingCentral setup flow, summarizing connection, user mappings, and SMS configuration and providing navigation controls.This component displays a loading skeleton while required integration data is fetched, then shows a success alert, three summary panels (Connection, User Mappings, SMS), a “What’s Next?” list, and Back / Complete Setup actions.
params:
- props — Component props - onComplete: Callback invoked when the user clicks “Complete Setup” - onBack: Callback invoked when the user clicks “Back”
returns: The verification step UI as a React element
example: | VerificationStep onBack=() = navigate(-1) onComplete=() = submitSetup() /Accessibility:- Action buttons are standard button elements to support keyboard and assistive technologies.- Informational content uses semantic headings and lists for screen reader readability.
score: 4

component WebFormBuilderPage

file: src/cores/ce/pages/WebFormBuilderPage.tsx:34
kind: component
core: ce
spec: (none)
summary: Utility for web form builder page.
score: 1

component WebFormCard

file: src/cores/ce/components/web-forms/WebFormCard.tsx:27
kind: component
core: ce
spec: (none)
summary: Utility for web form card.
score: 1

component WebFormDetailPage

file: src/cores/ce/pages/WebFormDetailPage.tsx:33
kind: component
core: ce
spec: (none)
summary: Utility for web form detail page.
score: 1

component WebFormEmbedPanel

file: src/cores/ce/components/web-forms/WebFormEmbedPanel.tsx:53
kind: component
core: ce
spec: (none)
summary: Utility for web form embed panel.
score: 1

component WebFormFieldEditor

file: src/cores/ce/components/web-forms/WebFormFieldEditor.tsx:47
kind: component
core: ce
spec: (none)
summary: Utility for web form field editor.
score: 1

component WebFormFieldItem

file: src/cores/ce/components/web-forms/WebFormFieldItem.tsx:49
kind: component
core: ce
spec: (none)
summary: Renders the web form field item interface.
score: 2

component WebFormFieldList

file: src/cores/ce/components/web-forms/WebFormFieldList.tsx:38
kind: component
core: ce
spec: (none)
summary: Utility for web form field list.
score: 1

component WebFormPreview

file: src/cores/ce/components/web-forms/WebFormPreview.tsx:19
kind: component
core: ce
spec: (none)
summary: Utility for web form preview.
score: 1

component WebFormsListPage

file: src/cores/ce/pages/WebFormsListPage.tsx:49
kind: component
core: ce
spec: (none)
summary: Renders the web forms list page interface.
score: 2

component WebFormStatsCards

file: src/cores/ce/components/web-forms/WebFormStatsCards.tsx:23
kind: component
core: ce
spec: (none)
summary: Renders the web form stats cards interface.
score: 2

component WebFormStylingEditor

file: src/cores/ce/components/web-forms/WebFormStylingEditor.tsx:19
kind: component
core: ce
spec: (none)
summary: Edits web-form theme settings including colors, button style, and typography.
score: 2

component WebFormSubmissionsTable

file: src/cores/ce/components/web-forms/WebFormSubmissionsTable.tsx:47
kind: component
core: ce
spec: (none)
summary: Utility for web form submissions table.
score: 1

component WidgetPositionPreview

file: src/cores/ce/components/settings/WidgetPositionPreview.tsx:47
kind: component
core: ce
spec: (none)
summary: Renders a miniature browser mockup that visualizes where an embeddable widget will appear on the screen and highlights the selected corner.The preview shows four corner indicators (top-left, top-right, bottom-left, bottom-right); the active position is styled with the primary color and displays a phone icon.Accessibility: the container uses role=“img” and an that announces the current widget position.
params:
- props — Component props - position: The active widget corner position to highlight - className: Optional additional class names to apply to the root container
returns: A JSX element containing the browser mockup and a textual label describing the selected position
example: | WidgetPositionPreview position=“bottom-right” /
score: 4

Functions & utilities

function __resetCrisisDetectionEnabledCache

file: src/cores/ce/lib/crisisDetectionSettings.ts:38
kind: function
core: ce
spec: (none)
summary: Test helper.
score: 1

function ActivitySearchPage

file: src/cores/ce/pages/ActivitySearchPage.tsx:77
kind: function
core: ce
spec: (none)
summary: Renders the activity search page interface.
score: 4

function addDays

file: src/cores/ce/lib/priorAuth/buildSubmissionPayload.ts:22
kind: function
core: ce
spec: (none)
summary: Add calendar days to a YYYY-MM-DD date, returning YYYY-MM-DD (UTC).
score: 4

function aggregateByDisposition

file: src/cores/ce/hooks/useCallAnalytics.ts:80
kind: function
core: ce
spec: (none)
summary: Aggregates by disposition for pie chart
score: 4

function aggregateByPeriod

file: src/cores/ce/hooks/useCallAnalytics.ts:23
kind: function
core: ce
spec: (none)
summary: Aggregates call analytics rows by the specified time period
score: 4

function aggregateByStage

file: src/cores/ce/hooks/usePipelineMetrics.ts:27
kind: function
core: ce
spec: (none)
summary: Aggregates raw view rows into stage-level metrics
score: 4

function aggregateDirectionalCounts

file: src/cores/ce/hooks/useReferralAttempts.ts:44
kind: function
core: ce
spec: (none)
summary: Pure directional aggregation mirroring the ce_partners reconciliation trigger:counts incoming vs outbound separately and ignores soft-deleted rows. Consumedby ReferralLedgerPanel to render the live Incoming/Outbound summary from theloaded attempts, so the panel reflects the in-cache ledger (incl. an attemptjust logged) without re-querying the partner row.
score: 4

function applyMergeFields

file: src/cores/ce/utils/merge-fields.ts:234
kind: function
core: ce
spec: (none)
summary: Apply merge fields to template text
params:
- template — Template text with field.name placeholders
- context — Data context for field substitution
- options — Substitution options
returns: Template with fields replaced by values
score: 4

function assertAssigneeEligible

file: src/cores/ce/utils/leadAssignmentAudit.ts:19
kind: function
core: ce
spec: (none)
summary: Verify the assignee belongs to the same org and currently holds anunexpired role assignment. (unassign) is always eligible.
score: 4

function assertPart2ConsentForScreening

file: src/cores/ce/utils/part2ConsentGate.ts:42
kind: function
core: ce
spec: (none)
summary: Enforce the Part 2 consent gate before SUD-screening triage is scored/persisted.Throws when consent is required and not obtained.
score: 4

function assignmentToastMessage

file: src/cores/ce/utils/leadAssignment.ts:28
kind: function
core: ce
spec: (none)
summary: AC-1/AC-2 success-toast copy for an assignment outcome.
score: 4

function autoDetectMapping

file: src/cores/ce/utils/csvImport.ts:125
kind: function
core: ce
spec: (none)
summary: Auto-detect column mapping based on header names
score: 4

function billingCodeForProgram

file: src/cores/ce/lib/priorAuth/buildSubmissionPayload.ts:13
kind: function
core: ce
spec: (none)
summary: S9480 = Mental Health IOP, H0015 = SUD IOP (FR-6).
score: 4

function buildAssignmentEventPayload

file: src/cores/ce/utils/leadAssignmentAudit.ts:98
kind: function
core: ce
spec: (none)
summary: Build the minimal, PHI-free payload used for both PF-10 notificationsand the canonical / domain events.
score: 4

function buildAssignmentNotification

file: src/cores/ce/utils/leadAssignment.ts:78
kind: function
core: ce
spec: (none)
summary: Build the row for an assignment (AC-5). Body staysPII-light — the lead reference travels in for the deep link, not thevisible text — and PF-10 delivery routes it to the assignee’s channels(email/in-app) per their preferences.
score: 4

function buildFieldDecisions

file: src/cores/ce/lib/mergeSurvivorship.ts:127
kind: function
core: ce
spec: (none)
summary: Builds the RPC payload from the reviewer’s selections:only fields whose chosen value differs from the survivor’s current valueare sent (the survivor’s own values need no decision).
score: 4

function buildPartnerAgreementContent

file: src/cores/ce/templates/partner-agreement-content.ts:10
kind: function
core: ce
spec: (none)
summary: Builds build partner agreement content data for downstream workflows.
score: 4

function buildPerTrackUnassignedColumns

file: src/cores/ce/lib/pipelineVirtualStages.ts:52
kind: function
core: ce
spec: (none)
summary: Splits unstaged active leads into one virtual Unassigned column per pipeline track(CE-64 FR-3.3 — lead appears only in the row for its ).
score: 4

function buildVCard

file: src/cores/ce/lib/vcard.ts:62
kind: function
core: ce
spec: (none)
summary: Build an RFC-6350 vCard 3.0 string from whitelisted card fields. Only fieldswith a non-empty value are emitted, so the output is stable and minimal.
score: 4

function calculatePartnerStatus

file: src/cores/ce/utils/calculatePartnerStatus.ts:107
kind: function
core: ce
spec: (none)
summary: Calculate partner status based on KPIs and milestonesStatus Logic:- exceeding: All KPIs above target- on_track: All KPIs within ±10% tolerance- at_risk: 1 KPI below target- off_track: 2+ KPIs below target OR 2+ missed milestones
score: 4

function calculateScreeningTriage

file: src/cores/ce/utils/screeningTriage.ts:176
kind: function
core: ce
spec: (none)
summary: Calculates the triage category, score, and recommended level of care by evaluatinga against questionnaire responses. Pure and deterministic.
score: 4

function calculateSegments

file: src/cores/ce/utils/sms-segment-utils.ts:213
kind: function
core: ce
spec: (none)
summary: Calculate SMS segments for given text
score: 4

function canAdvanceFromDocumentsStep

file: src/cores/ce/wizards/partner-contract/partnerContractWizardValidation.ts:39
kind: function
core: ce
spec: (none)
summary: Validates the documents step — always allows advancing, but warns if no document.
score: 4

function canSendSms

file: src/cores/ce/components/sms/SmsConsentBadge.tsx:173
kind: function
core: ce
spec: (none)
summary: Check if SMS can be sent based on consent status
score: 4

function cardShareAssets

file: src/cores/ce/lib/cardShare.ts:38
kind: function
core: ce
spec: (none)
summary: Build the full set of share assets for a card: public URL + vCard string +vCard data URI. The QR is rendered separately in the UI from .
score: 4

function checkAndNotifyStatusChange

file: src/cores/ce/utils/partnerProgressNotifications.ts:144
kind: function
core: ce
spec: (none)
summary: Check if status changed and send appropriate notification
score: 4

function checkDuplicateContact

file: src/cores/ce/utils/duplicateDetection.ts:29
kind: function
core: ce
spec: (none)
summary: Check for duplicate contacts by phone or emailReturns the first matching contact or null
score: 4

function checkPhiBlocking

file: src/cores/ce/hooks/usePhiBlockCheck.ts:87
kind: function
core: ce
spec: (none)
summary: Standalone function for checking PHI without React hooksUseful for validation in form schemas or edge functions
score: 4

function chooseCreateLeadTrackId

file: src/cores/ce/hooks/chooseCreateLeadTrackId.ts:19
kind: function
core: ce
spec: (none)
summary: Decide the to persist for a new lead. An explicit picker selectionalways wins; otherwise the track is auto-resolved from the lead’s requestedservices against the org’s active tracks; otherwise is returned sothe DB trigger assigns the org default (CE-64-EN-01 AC-1).
params:
- explicitTrackId — the track chosen in the New Lead picker, if any.
- tracks — the org’s active pipeline tracks, for service-based resolution.
- requestedServices — the lead’s requested services, used to auto-resolve.
returns: the resolved track id, or to defer to the DB default trigger.
score: 4

function classifyLeadStageTransition

file: src/cores/ce/lib/classifyLeadStageTransition.ts:37
kind: function
core: ce
spec: (none)
summary: Classify a destination stage row into the transition kind.- → (open Scheduled prompt)- → (open Admit confirm)- → (open Closure form)- Otherwise, if is true the caller should still surface the generic Scheduled prompt as a fallback action; we report to keep the UI behavior consistent. If neither flag is set we report and the caller should commit the move directly.
score: 4

function clearAllRecentViews

file: src/cores/ce/lib/mobileRecentViewsLru.ts:77
kind: function
core: ce
spec: (none)
summary: Clears ALL CE mobile recent view keys from localStorage.Called during sign-out to prevent PHI leakage.
score: 4

function clearOfflineQueue

file: src/cores/ce/lib/offlineActivityQueue.ts:108
kind: function
core: ce
spec: (none)
summary: Clears the entire offline queue.
score: 4

function clearRecentViews

file: src/cores/ce/lib/mobileRecentViewsLru.ts:65
kind: function
core: ce
spec: (none)
summary: Clears recent views for a specific user+org scope.
score: 4

function computeFieldConflicts

file: src/cores/ce/lib/mergeSurvivorship.ts:96
kind: function
core: ce
spec: (none)
summary: Lists fields where the two contacts genuinely conflict — both perspectivesshown side by side in the dialog. Fields where the merged side adds a valuethe survivor lacks are conflicts too (defaulting to the non-null side).
score: 4

function computeScreeningSla

file: src/cores/ce/utils/computeScreeningSla.ts:32
kind: function
core: ce
spec: (none)
summary: Computes the SLA status for a screening attempt.Uses UTC-based computation to avoid timezone edge cases.Both inputs are expected as ISO 8601 strings.
score: 4

function computeSummary

file: src/cores/ce/hooks/usePipelineMetrics.ts:83
kind: function
core: ce
spec: (none)
summary: Computes pipeline summary from stage metrics
score: 4

function constructTenantPath

file: src/cores/ce/lib/document-storage-adapter.ts:64
kind: function
core: ce
spec: (none)
summary: Construct a tenant-safe storage path.Layout: The first path segment is the organization id; storage RLS policies key on to enforce tenant isolation.
score: 4

function containsUnredactedPhi

file: src/cores/ce/lib/priorAuth/redactPhi.ts:31
kind: function
core: ce
spec: (none)
summary: True if any PHI key in the object still holds a non-redacted value.
score: 4

function createSampleContext

file: src/cores/ce/utils/merge-fields.ts:311
kind: function
core: ce
spec: (none)
summary: Create sample context for template preview
score: 4

function dequeueItems

file: src/cores/ce/lib/offlineActivityQueue.ts:71
kind: function
core: ce
spec: (none)
summary: Removes the first N items from the queue (FIFO drain after successful sync).
score: 4

function detectDuplicates

file: src/cores/ce/components/contacts/import-utils/fuzzyMatch.ts:53
kind: function
core: ce
spec: (none)
summary: Detect duplicate clusters by resolving imported rows through the CE-74identity engine.
params:
- validRows — Validated import rows
- organizationId — Organization to scope the search
returns: Array of duplicate clusters (best match per row)
score: 4

function detectPhiInMessage

file: src/cores/ce/utils/sms-opt-out.ts:290
kind: function
core: ce
spec: (none)
summary: Detect PHI patterns in message text
params:
- text — Message text to check
returns: Detection result with types found and severity
score: 4

function dispatchAssignmentNotification

file: src/cores/ce/utils/leadAssignment.ts:117
kind: function
core: ce
spec: (none)
summary: AC-5/AC-6: create the assignee notification when (and only when) the lead was(re)assigned to another user. Returns whether a notification was created socallers/tests can assert the decision. Caller wraps this best-effort so anotification failure never blocks the assignment itself.
score: 4

function downloadContactTemplate

file: src/cores/ce/utils/csvImport.ts:76
kind: function
core: ce
spec: (none)
summary: Initiates a browser download of the contact CSV template file.
score: 4

function downloadCSV

file: src/cores/ce/utils/exportActivities.ts:112
kind: function
core: ce
spec: (none)
summary: Download CSV content as a file
score: 4

function encoreFieldLabel

file: src/cores/ce/lib/hubspotMappingFields.ts:33
kind: function
core: ce
spec: (none)
summary: Label for a mapped field; falls back to the raw column name.
score: 4

function enqueueActivity

file: src/cores/ce/lib/offlineActivityQueue.ts:53
kind: function
core: ce
spec: (none)
summary: Enqueues an activity. Throws if queue is at capacity (100 items).
score: 4

function escapeCSVField

file: src/cores/ce/utils/exportActivities.ts:42
kind: function
core: ce
spec: (none)
summary: Escape a CSV field value for proper formatting
score: 4

function evaluateOrgCalendarCapability

file: src/cores/ce/lib/orgCalendarCapability.ts:48
kind: function
core: ce
spec: (none)
summary: Evaluate org-calendar DWD capability from the org’s Google Workspaceconnection and the current user’s email.Fails closed: any missing input, non- status, disabled calendarcapability, or domain mismatch yields .
params:
- connection — The active org’s PF-101 connection, or null/undefined.
- userEmail — The current user’s email (used only for the domain match).
score: 4

function exportActivitiesToCSV

file: src/cores/ce/utils/exportActivities.ts:131
kind: function
core: ce
spec: (none)
summary: Export activities to CSV with audit logging
score: 4

function extractCountryCode

file: src/cores/ce/utils/sms-phone-utils.ts:42
kind: function
core: ce
spec: (none)
summary: Extract country code from E.164 phone number
params:
- phone — E.164 phone number
returns: Country code (e.g., “+1” for US)
score: 4

function extractDomain

file: src/cores/ce/utils/email-matching.ts:59
kind: function
core: ce
spec: (none)
summary: Extract domain from email address
score: 4

function extractMergeFields

file: src/cores/ce/utils/merge-fields.ts:269
kind: function
core: ce
spec: (none)
summary: Extract merge field keys from template text
params:
- template — Template text to scan
returns: Array of unique field keys found
score: 4

function fetchActivityHistory

file: src/cores/ce/history/adapters/activity.ts:31
kind: function
core: ce
spec: CE-60
summary: History adapter that fetches a contact’s activity rows from , applying theredaction policy and date/limit window for the unified timeline.
params:
- args — Org/contact scope, optional , per-source , and redaction .
returns: Normalised history rows for activities.
score: 5

function fetchAuditHistory

file: src/cores/ce/history/adapters/audit.ts:30
kind: function
core: ce
spec: CE-60
summary: History adapter that fetches a contact’s audit-log rows from (profileupdates), applying the redaction policy and date/limit window.
params:
- args — Org/contact scope, optional , per-source , and redaction .
returns: Normalised history rows for audit/profile-update events.
score: 5

function fetchClosureHistory

file: src/cores/ce/history/adapters/closure.ts:31
kind: function
core: ce
spec: CE-60
summary: History adapter that derives closure/loss events for a contact by resolving its leads first,applying the redaction policy and date/limit window.
params:
- args — Org/contact scope, optional , per-source , and redaction .
returns: Normalised history rows for lead closures.
score: 5

function fetchContactHistory

file: src/cores/ce/history/adapters/index.ts:103
kind: function
core: ce
spec: CE-60
summary: Orchestrates the unified contact-history page by fanning out to the per-source adapters selectedby the active filters, over-fetching per source so the merged, cursored window can still yield afull page.
params:
- args — Scope, paging, filters, cursor, redaction policy, and stage-fallback flag.
returns: A merged, redacted, cursored page of history rows.
score: 5

function fetchDocumentHistory

file: src/cores/ce/history/adapters/document.ts:25
kind: function
core: ce
spec: CE-60
summary: History adapter that fetches a contact’s document events from (uploads,deletions, extraction status), applying the redaction policy and window.
params:
- args — Org/contact scope, optional , per-source , and redaction .
returns: Normalised history rows for documents.
score: 5

function fetchScreeningHistory

file: src/cores/ce/history/adapters/screening.ts:26
kind: function
core: ce
spec: CE-60
summary: History adapter that derives screening/intake events for a contact by resolving the contact’sleads first (a contact may have multiple intake attempts), applying the redaction policy andwindow.
params:
- args — Org/contact scope, optional , per-source , and redaction .
returns: Normalised history rows for screening attempts.
score: 5

function findNonGsm7Characters

file: src/cores/ce/utils/sms-segment-utils.ts:198
kind: function
core: ce
spec: (none)
summary: Find non-GSM-7 characters in text
score: 4

function formatActivityForExport

file: src/cores/ce/utils/exportActivities.ts:54
kind: function
core: ce
spec: (none)
summary: Format an activity for CSV export
score: 4

function formatCallDuration

file: src/cores/ce/utils/formatCallDuration.ts:14
kind: function
core: ce
spec: (none)
summary: Format call duration from seconds to mm:ss format
params:
- seconds — Duration in seconds (or null)
returns: Formatted string like “5:23” or ”-” for null
score: 4

function formatFileSize

file: src/cores/ce/utils/csvImport.ts:213
kind: function
core: ce
spec: (none)
summary: Format file size for display
score: 1

function formatLeadStageCreateError

file: src/cores/ce/lib/leadStageOrder.ts:60
kind: function
core: ce
spec: (none)
summary: User-facing message for stage create unique violations.
score: 4

function formatMergeValue

file: src/cores/ce/lib/mergeSurvivorship.ts:145
kind: function
core: ce
spec: (none)
summary: Human-readable cell for the diff table; PHI stays in the org-scoped UI.
score: 4

function formatPhoneForDisplay

file: src/cores/ce/utils/sms-phone-validation.ts:67
kind: function
core: ce
spec: (none)
summary: Format phone number for display
params:
- phone — E.164 phone number
returns: Formatted display string
score: 4

function formatPhoneMasked

file: src/cores/ce/utils/sms-phone-utils.ts:22
kind: function
core: ce
spec: (none)
summary: Format phone number with masking for privacy-safe displayShows only last 4 digits: +1******1234
params:
- phone — E.164 phone number
returns: Masked phone string
score: 4

function formatPublishError

file: src/cores/ce/wizards/sequences/utils/parsePublishError.ts:259
kind: function
core: ce
spec: (none)
summary: Convert a structured detail into a user-facing toast title + description.
score: 4

function formatReferralDate

file: src/cores/ce/lib/formatReferralDate.ts:31
kind: function
core: ce
spec: (none)
summary: Formats a stored referral timestamp as a calendar date in UTC.
params:
- value — ISO timestamp string (or null/undefined).
returns: The date formatted as e.g. , or when absent/invalid.
score: 4

function generateActivitiesCSV

file: src/cores/ce/utils/exportActivities.ts:72
kind: function
core: ce
spec: (none)
summary: Generate CSV content from activities
score: 4

function generateCardSlug

file: src/cores/ce/lib/cardSlug.ts:57
kind: function
core: ce
spec: (none)
summary: Build a globally-unique-candidate slug from a display name, e.g.. The base is deterministic; only the suffix is random.
score: 4

function generateSignedUrl

file: src/cores/ce/lib/document-storage-adapter.ts:128
kind: function
core: ce
spec: (none)
summary: Generate a short-lived signed URL for download.
score: 4

function getCharacterLimitWarning

file: src/cores/ce/utils/sms-segment-utils.ts:309
kind: function
core: ce
spec: (none)
summary: Get character limit warning if approaching or exceeding limits
score: 4

function getDefaultRecipient

file: src/cores/ce/hooks/useEmailCompose.ts:196
kind: function
core: ce
spec: (none)
summary: Get default recipient email from contact or partner
score: 4

function getGsm7Length

file: src/cores/ce/utils/sms-segment-utils.ts:183
kind: function
core: ce
spec: (none)
summary: Calculate GSM-7 character length (extended chars count as 2)
score: 4

function getMappingPreview

file: src/cores/ce/components/contacts/import-utils/mappingPreview.ts:28
kind: function
core: ce
spec: (none)
summary: Generate preview rows showing sample values for each mapped column.
params:
- rows — Parsed CSV rows
- columnMapping — Current column mapping
- maxSamples — Maximum sample values per column (default 5)
returns: Array of preview rows with sample values
score: 4

function getMatchTypeColor

file: src/cores/ce/utils/email-matching.ts:299
kind: function
core: ce
spec: (none)
summary: Get semantic color class for a match type badge
score: 4

function getMatchTypeLabel

file: src/cores/ce/utils/email-matching.ts:282
kind: function
core: ce
spec: (none)
summary: Get a human-readable label for a match type
score: 4

function getMergeFieldGroups

file: src/cores/ce/utils/merge-fields.ts:211
kind: function
core: ce
spec: (none)
summary: Get merge fields grouped by category for UI picker
score: 4

function getNextBusinessOpen

file: src/cores/ce/lib/businessHoursEvaluator.ts:60
kind: function
core: ce
spec: (none)
summary: Returns the next business-open Date (= ).Returns null if config is invalid.
score: 4

function getOfflineQueue

file: src/cores/ce/lib/offlineActivityQueue.ts:40
kind: function
core: ce
spec: (none)
summary: Retrieves the current offline queue.
score: 4

function getOptInKeyword

file: src/cores/ce/utils/sms-opt-out.ts:123
kind: function
core: ce
spec: (none)
summary: Get the matched opt-in keyword from message
params:
- body — SMS message body
returns: Matched keyword or null
score: 4

function getOptOutKeyword

file: src/cores/ce/utils/sms-opt-out.ts:103
kind: function
core: ce
spec: (none)
summary: Get the matched opt-out keyword from messageUseful for logging the specific keyword used
params:
- body — SMS message body
returns: Matched keyword or null
score: 4

function getPendingCount

file: src/cores/ce/lib/offlineActivityQueue.ts:100
kind: function
core: ce
spec: (none)
summary: Returns the count of pending items.
score: 4

function getPhiLabels

file: src/cores/ce/utils/sms-opt-out.ts:331
kind: function
core: ce
spec: (none)
summary: Get human-readable labels for detected PHI types
score: 4

function getPhoneValidationError

file: src/cores/ce/utils/sms-phone-validation.ts:31
kind: function
core: ce
spec: (none)
summary: Get user-friendly validation error for phone number
params:
- phone — Phone number to validate
returns: Error message or null if valid
score: 4

function getRecentViews

file: src/cores/ce/lib/mobileRecentViewsLru.ts:32
kind: function
core: ce
spec: (none)
summary: Retrieves recent views for a user+org, most recent first.
score: 4

function getRecipientName

file: src/cores/ce/hooks/useEmailCompose.ts:213
kind: function
core: ce
spec: (none)
summary: Get recipient display name
score: 1

function getSegmentDisplay

file: src/cores/ce/utils/sms-segment-utils.ts:293
kind: function
core: ce
spec: (none)
summary: Get display string for segment information
score: 4

function getSmsBlockReason

file: src/cores/ce/components/sms/SmsConsentBadge.tsx:180
kind: function
core: ce
spec: (none)
summary: Get reason why SMS cannot be sent
score: 4

function getSmsMessageIntent

file: src/cores/ce/utils/sms-opt-out.ts:145
kind: function
core: ce
spec: (none)
summary: Retrieves sms message intent data for caller use.
score: 4

function getStatusBgColor

file: src/cores/ce/utils/calculatePartnerStatus.ts:238
kind: function
core: ce
spec: (none)
summary: Get background color class for status badges
score: 4

function getStatusColor

file: src/cores/ce/utils/calculatePartnerStatus.ts:225
kind: function
core: ce
spec: (none)
summary: Get semantic color class for status
score: 4

function getStatusLabel

file: src/cores/ce/utils/calculatePartnerStatus.ts:212
kind: function
core: ce
spec: (none)
summary: Get human-readable status label
score: 4

function getUrgencyAccent

file: src/cores/ce/lib/urgency.ts:84
kind: function
core: ce
spec: (none)
summary: Resolve an urgency string to its UI accent, or null when absent/invalid.
score: 4

function groupStagesByTrack

file: src/cores/ce/lib/groupStagesByTrack.ts:19
kind: function
core: ce
spec: (none)
summary: Split a board’s stage groups into per-track buckets plus one shared terminalbucket. Stages with a group under that track; stages with no (the virtual Converted/Lost columns) collapse into a single list — the rule that makes terminal columns shared across tracksrather than duplicated per track (CE-64-EN-01 AC-2).
params:
- stages — the board’s stage groups, per-track and terminal mixed.
returns: (trackId → that track’s stages) and (the shared no-track stages).
score: 4

function invokeCalendarTaskPush

file: src/cores/ce/services/calendarTaskPush.ts:38
kind: function
core: ce
spec: (none)
summary: Fire-and-forget invoke of the push edge function. Swallows all errors: thepush is one-way and fail-open, so the caller’s task creation is never blocked.
score: 4

function isGsm7

file: src/cores/ce/utils/sms-segment-utils.ts:171
kind: function
core: ce
spec: (none)
summary: Check if text contains only GSM-7 characters
score: 4

function isHelpMessage

file: src/cores/ce/utils/sms-opt-out.ts:86
kind: function
core: ce
spec: (none)
summary: Check if message is a help request
params:
- body — SMS message body
returns: True if message is a help request
score: 4

function isOptInMessage

file: src/cores/ce/utils/sms-opt-out.ts:60
kind: function
core: ce
spec: (none)
summary: Check if message body contains an opt-in keyword
params:
- body — SMS message body
returns: True if message is an opt-in/re-consent request
score: 4

function isOptOutMessage

file: src/cores/ce/utils/sms-opt-out.ts:34
kind: function
core: ce
spec: (none)
summary: Check if message body contains an opt-out keyword
params:
- body — SMS message body
returns: True if message is an opt-out request
score: 4

function isPart2ConsentRequired

file: src/cores/ce/utils/part2ConsentGate.ts:32
kind: function
core: ce
spec: (none)
summary: Whether a 42 CFR Part 2 consent is required before scoring/persisting a screening ofthis program type. Fail-closed: every current screening program type is SUD/BH.
score: 4

function isSensitiveField

file: src/cores/ce/history/lib/redaction.ts:37
kind: function
core: ce
spec: CE-60
summary: Returns whether a field name is considered sensitive (DOB, phone, email, insurance, SSN,address, etc.) and therefore subject to masking unless the caller holds sensitive-view.
params:
- fieldName — Candidate field name; matched case-insensitively. Nullish names are never sensitive.
returns: when the field must be masked for non-privileged viewers.
score: 5

function isValidE164

file: src/cores/ce/utils/sms-phone-validation.ts:17
kind: function
core: ce
spec: (none)
summary: Validate E.164 phone number formatE.164 format: +[country code][subscriber number]Example: +14155551234 (US number)
params:
- phone — Phone number to validate
returns: true if valid E.164 format
score: 4

function isWithinBusinessHours

file: src/cores/ce/lib/businessHoursEvaluator.ts:42
kind: function
core: ce
spec: (none)
summary: Whether falls within the configured business hours.
score: 4

function logContactTagEvent

file: src/cores/ce/lib/contactTagAudit.ts:26
kind: function
core: ce
spec: (none)
summary: Best-effort audit event emission. Failures are logged but never thrown sothe underlying assignment mutation cannot be blocked by audit issues.
score: 4

function mapPartnerToFormValues

file: src/cores/ce/schemas/partnerSchema.ts:63
kind: function
core: ce
spec: (none)
summary: Map existing partner data to form values
score: 4

function mapToScorecardMetrics

file: src/cores/ce/hooks/usePartnerScorecard.ts:42
kind: function
core: ce
spec: (none)
summary: Maps raw view rows to scorecard metrics with declining flags
params:
- rows — Raw database view rows
- successRateThreshold — Threshold below which success rate is considered declining
- volumeThreshold — Days since last referral after which volume is considered declining
score: 4

function markItemFailed

file: src/cores/ce/lib/offlineActivityQueue.ts:89
kind: function
core: ce
spec: (none)
summary: Marks a queue item as failed with an error message and increments attempts.
score: 4

function maskInsuranceMemberId

file: src/cores/ce/utils/insurance-mask.ts:19
kind: function
core: ce
spec: (none)
summary: Mask an insurance member identifier.Rules: - null/empty → empty string - length ≤ 4 → fully masked (no last-N reveal) - length 4 → reveal the last 4 chars, mask the rest
score: 4

function maskValue

file: src/cores/ce/history/lib/redaction.ts:50
kind: function
core: ce
spec: CE-60
summary: Returns the value as-is when the redaction policy grants sensitive view, otherwise the masktoken; nullish input passes through as .
params:
- policy — Redaction policy whose flag decides masking.
returns: The original value, the mask token, or .
score: 5

function matchCrisisKeywords

file: src/cores/ce/lib/crisisKeywordMatcher.ts:81
kind: function
core: ce
spec: (none)
summary: Run keyword detection against an arbitrary text body.Pure function — safe to call in workers, edge functions, or React render.
score: 4

function matchEmailsToEntities

file: src/cores/ce/utils/email-matching.ts:241
kind: function
core: ce
spec: (none)
summary: Match multiple email addresses in batchUseful for displaying match indicators on email listsProcesses emails in parallel with concurrency limit to avoidoverwhelming the database.
score: 4

function matchEmailToEntity

file: src/cores/ce/utils/email-matching.ts:164
kind: function
core: ce
spec: (none)
summary: Match an email address to a contact, lead, or partnerPriority:1. Exact contact email match2. If contact found, check for active lead3. Partner domain match4. No match
score: 4

function missingRequiredFields

file: src/cores/ce/lib/priorAuth/buildSubmissionPayload.ts:65
kind: function
core: ce
spec: (none)
summary: Required fields that must be present before submission is enabled (FR-3, AC-2).
score: 4

function normalizeEmail

file: src/cores/ce/utils/duplicateDetection.ts:20
kind: function
core: ce
spec: (none)
summary: Normalize email by lowercasing and trimming
score: 4

function normalizeEmail

file: src/cores/ce/utils/email-matching.ts:51
kind: function
core: ce
spec: (none)
summary: Normalize email address for consistent matching
score: 4

function normalizePhone

file: src/cores/ce/utils/duplicateDetection.ts:12
kind: function
core: ce
spec: (none)
summary: Normalize phone number by removing formatting characters
score: 4

function normalizePhoneToE164

file: src/cores/ce/utils/sms-phone-validation.ts:92
kind: function
core: ce
spec: (none)
summary: Normalize phone number to E.164 formatHandles common input variations:- Removes spaces, dashes, parentheses- Adds + if missing (assumes US if 10 digits)
params:
- phone — Phone number input
returns: Normalized E.164 format or original if can’t normalize
score: 4

function notifyOrgAdmins

file: src/cores/ce/utils/partnerProgressNotifications.ts:230
kind: function
core: ce
spec: (none)
summary: Batch send notifications to multiple org admins
score: 4

function parseCSV

file: src/cores/ce/utils/csvImport.ts:92
kind: function
core: ce
spec: (none)
summary: Parse CSV text into structured data (uses /platform/csv).
score: 4

function parsePublishError

file: src/cores/ce/wizards/sequences/utils/parsePublishError.ts:84
kind: function
core: ce
spec: (none)
summary: Decode an unknown error from into a structured detail.Regex order matters — more-specific patterns come first.
score: 4

function parseUTMFromURL

file: src/cores/ce/hooks/useLeadAttribution.ts:31
kind: function
core: ce
spec: (none)
summary: Parse UTM parameters from URL
score: 1

function perTrackNextStageOrder

file: src/cores/ce/lib/leadStageOrder.ts:18
kind: function
core: ce
spec: (none)
summary: Smallest non-negative not yet used on this track.General and Recovery Housing may both use 0, 1, 2 independently.
score: 4

function phonesMatch

file: src/cores/ce/utils/sms-phone-utils.ts:67
kind: function
core: ce
spec: (none)
summary: Check if two phone numbers match (handles format variations)
params:
- phone1 — First phone number
- phone2 — Second phone number
returns: True if phones match after normalization
score: 4

function pickDefaultTransferStageId

file: src/cores/ce/lib/pipelineVirtualStages.ts:29
kind: function
core: ce
spec: (none)
summary: CE-64 Phase 2: pick the default destination stage when transferring a leadacross tracks. Prefer a name match against the lead’s current stage; fallback to the first active stage in the destination track; return toindicate the lead should land in the destination track’s Unassigned column.
score: 4

function previewImport

file: src/cores/ce/utils/csvImport.ts:164
kind: function
core: ce
spec: (none)
summary: Validate and preview import data
score: 4

function publicCardUrl

file: src/cores/ce/lib/cardShare.ts:27
kind: function
core: ce
spec: (none)
summary: Build the public URL for a card slug, e.g. .
score: 4

function randomSlugSuffix

file: src/cores/ce/lib/cardSlug.ts:45
kind: function
core: ce
spec: (none)
summary: Generate a short random alphanumeric suffix of chars.
score: 4

function readableForeground

file: src/cores/ce/components/contacts/ContactTagBadge.utils.ts:20
kind: function
core: ce
spec: CE-61
summary: Picks a readable foreground colour for a tag swatch by computing the Rec. 709 perceivedluminance of the given hex and returning the dark token for light backgrounds, the light tokenotherwise.
params:
- hex — Six-digit hex colour (with or without leading ); malformed values fall back to the light foreground.
returns: An foreground token string.
score: 5

function redactDetails

file: src/cores/ce/history/lib/redaction.ts:59
kind: function
core: ce
spec: (none)
summary: Redact a object in place-safe manner. Returns a new object.Any key matching SENSITIVE_FIELD_NAMES is masked when policy denies sensitive view.
score: 4

function referralAttemptListKey

file: src/cores/ce/hooks/useReferralAttempts.ts:33
kind: function
core: ce
spec: (none)
summary: Stable query-key builder so components and tests share one cache namespace.
score: 4

function regenerateCardSlug

file: src/cores/ce/lib/cardSlug.ts:66
kind: function
core: ce
spec: (none)
summary: Regenerate a slug for the SAME display name with a fresh random suffix.Use this on a unique-violation retry so the base stays stable but thecollision is broken. Equivalent to but named for intent.
score: 4

function registerCeSequenceWizardSteps

file: src/cores/ce/wizards/sequences/registerCeSequenceWizardSteps.ts:14
kind: function
core: ce
spec: (none)
summary: Registers CE sequence builder wizard custom step components.
score: 4

function registerPartnerContractWizardSteps

file: src/cores/ce/wizards/partner-contract/registerPartnerContractWizardSteps.ts:14
kind: function
core: ce
spec: (none)
summary: Registers CE partner contract wizard custom step components.
score: 4

function registerScreeningWizardSteps

file: src/cores/ce/wizards/screening/registerScreeningWizardSteps.ts:14
kind: function
core: ce
spec: (none)
summary: Registers CE screening wizard custom step components.
score: 4

function removeQueueItem

file: src/cores/ce/lib/offlineActivityQueue.ts:80
kind: function
core: ce
spec: (none)
summary: Removes a single item by clientId.
score: 4

function removeStorageObject

file: src/cores/ce/lib/document-storage-adapter.ts:145
kind: function
core: ce
spec: (none)
summary: Best-effort removal of a storage object (used on insert-rollback).
score: 4

function requiresTriageAcknowledgment

file: src/cores/ce/utils/screeningTriage.ts:160
kind: function
core: ce
spec: (none)
summary: CE-81 AC-2/FR-3: ANY recommended level of care (not only critical flags) requires anexplicit human acknowledgment before it can inform a disposition. Returns true when thetriage produced a level-of-care recommendation that must be acknowledged.
score: 4

function resolveActiveTriageRuleset

file: src/cores/ce/utils/triageRulesetLoader.ts:60
kind: function
core: ce
spec: (none)
summary: Resolve the active triage ruleset for the org. Never throws — falls back to the seededsystem default, then to the bundled constant, so a triage evaluation always has rules.
score: 4

function resolveAssignmentAction

file: src/cores/ce/utils/leadAssignment.ts:17
kind: function
core: ce
spec: (none)
summary: Classify an assignment transition from the previous and next assignee ids.Mirrors the domain-event naming ( / /) so the toast, the event, and the AC all agree.
score: 4

function resolveEscalation

file: src/cores/ce/lib/escalationEngine.ts:34
kind: function
core: ce
spec: (none)
summary: Resolve which on-call member currently owns the page.Members are sorted by ascending (1 = primary).
score: 4

function resolveInsuranceMemberId

file: src/cores/ce/utils/insurance-mask.ts:33
kind: function
core: ce
spec: (none)
summary: Choose between the unmasked value and its masked form based on the caller’s permission. Centralizes the policy so callers cannotaccidentally pass the raw value into telemetry.
score: 4

function resolvePartnerPrimaryDisplay

file: src/cores/ce/utils/partnerContactDisplay.ts:61
kind: function
core: ce
spec: (none)
summary: CE-66: Resolve the primary contact display for a partner from its rows. Returns when the partner has nopartner-contact rows (i.e. nothing to display).Use this in place of the deprecated / fallback. The legacy / columns were backfilledinto standalone primary partner-contact rows during the CE-66 migration,so this resolver covers the same data without reading the legacy columns.
score: 4

function resolveTaskPushRecipient

file: src/cores/ce/services/calendarTaskPush.ts:20
kind: function
core: ce
spec: (none)
summary: Resolve the target mailbox per CE-73 precedence: per_task_override (explicit) - assigned coordinator - org default.Returns null when nothing resolves. Mirrors the edge function precedence.
score: 4

function resolveTrackIdForNewStage

file: src/cores/ce/lib/leadStageOrder.ts:38
kind: function
core: ce
spec: (none)
summary: Resolve target track for a new stage (explicit id or org default track).
score: 4

function selectHasAlertTag

file: src/cores/ce/hooks/useContactTagsByContacts.ts:28
kind: function
core: ce
spec: (none)
summary: Pure helper exposed for CE-65 tile metadata consumers.
score: 4

function selectPrimaryPartnerContactRow

file: src/cores/ce/utils/partnerContactDisplay.ts:44
kind: function
core: ce
spec: (none)
summary: Pick the primary row from a partner’s collection. is mutually exclusive per partner (DB partial unique index),so at most one row is returned.
score: 4

function sendCheckInReminder

file: src/cores/ce/utils/partnerProgressNotifications.ts:212
kind: function
core: ce
spec: (none)
summary: Send check-in reminder for inactive partners
score: 4

function sendMilestoneNotification

file: src/cores/ce/utils/partnerProgressNotifications.ts:191
kind: function
core: ce
spec: (none)
summary: Send milestone reminder notification
score: 4

function sendPartnerProgressNotification

file: src/cores/ce/utils/partnerProgressNotifications.ts:101
kind: function
core: ce
spec: (none)
summary: Send a partner progress notification via PF-10
score: 4

function shouldNotifyAssignee

file: src/cores/ce/utils/leadAssignment.ts:59
kind: function
core: ce
spec: (none)
summary: AC-5/AC-6 decision: notify the assignee only when a lead is (re)assigned toanother active user. Self-assignment (AC-6) and unassign/no-op produce nonotification — you don’t get pinged about your own action.
score: 4

function shouldNotifyStatusChange

file: src/cores/ce/utils/calculatePartnerStatus.ts:251
kind: function
core: ce
spec: (none)
summary: Determine if status change warrants notification
score: 4

function slugifyName

file: src/cores/ce/lib/cardSlug.ts:31
kind: function
core: ce
spec: (none)
summary: Slugify a free-text name: lowercase, ASCII-fold, collapse non-alphanumericsto single hyphens, trim leading/trailing hyphens. Returns a stable base(without the random suffix).
score: 4

function togglePayerValue

file: src/cores/ce/components/PayerMultiSelect.tsx:14
kind: function
core: ce
spec: (none)
summary: Pure toggle: add value if absent, remove if present.
score: 4

function touchRecentView

file: src/cores/ce/lib/mobileRecentViewsLru.ts:47
kind: function
core: ce
spec: (none)
summary: Touches (upserts) a recent view entry, moving it to the front.Evicts the oldest entry when the 50-slot cap is exceeded.
score: 4

function triageAcknowledgmentSatisfied

file: src/cores/ce/utils/screeningTriage.ts:165
kind: function
core: ce
spec: (none)
summary: Whether the triage step’s acknowledgment gate is satisfied (nothing to ack, or acked).
score: 4

function unassignedStageIdForTrack

file: src/cores/ce/lib/pipelineVirtualStages.ts:11
kind: function
core: ce
spec: (none)
summary: Stable virtual column id for leads with no within a track row.
score: 4

function uploadHandler

file: src/cores/ce/lib/document-storage-adapter.ts:109
kind: function
core: ce
spec: (none)
summary: Upload a file to the CE-59 contact documents bucket.
score: 4

function validateContactType

file: src/cores/ce/utils/csvValidation.ts:95
kind: function
core: ce
spec: (none)
summary: Validate contact type.contact_type values are org-configurable via the ce_contact_type picklist, so thisfunction cannot validate against a fixed allowlist. It maps common import aliasesfor backwards compatibility and passes through any other non-empty value as-is.
score: 4

function validateDateOrdering

file: src/cores/ce/wizards/partner-contract/partnerContractWizardValidation.ts:18
kind: function
core: ce
spec: (none)
summary: Validates date ordering: endDate must be = startDate when both are present.
score: 4

function validateEmail

file: src/cores/ce/utils/csvValidation.ts:24
kind: function
core: ce
spec: (none)
summary: Validate email format
score: 1

function validateFileSize

file: src/cores/ce/lib/document-storage-adapter.ts:95
kind: function
core: ce
spec: (none)
summary: Validate file size against the configured maximum (in MB).
score: 4

function validateFileType

file: src/cores/ce/lib/document-storage-adapter.ts:83
kind: function
core: ce
spec: (none)
summary: Validate file MIME type against the CE-59 allow-list.
score: 4

function validateFinalSubmit

file: src/cores/ce/wizards/partner-contract/partnerContractWizardValidation.ts:54
kind: function
core: ce
spec: (none)
summary: Validates final submission: blocks when status requires a document but none is attached.
score: 4

function validateMergeFields

file: src/cores/ce/utils/merge-fields.ts:287
kind: function
core: ce
spec: (none)
summary: Validate that all merge fields in template are recognized
params:
- template — Template text to validate
returns: Object with valid and invalid field keys
score: 4

function validatePhone

file: src/cores/ce/utils/csvValidation.ts:42
kind: function
core: ce
spec: (none)
summary: Validate phone format
score: 1

function validateRequired

file: src/cores/ce/utils/csvValidation.ts:65
kind: function
core: ce
spec: (none)
summary: Validate required text field
score: 1

function validateRow

file: src/cores/ce/utils/csvValidation.ts:226
kind: function
core: ce
spec: (none)
summary: Validate a single row of CSV data
score: 4

function validateState

file: src/cores/ce/utils/csvValidation.ts:123
kind: function
core: ce
spec: (none)
summary: Validate US state abbreviation.By default enforces US state codes. Pass country=’*’ or any non-US countryto skip state validation for international addresses.
params:
- value — State/province value to validate
- country — Country code (default ‘US’). Use ’*’ or non-US code to skip validation.
score: 4

function validateStep

file: src/cores/ce/wizards/lead-conversion/hooks/useLeadConversionWizard.ts:34
kind: function
core: ce
spec: (none)
summary: Exported for direct unit testing
score: 4

function validateStep

file: src/cores/ce/wizards/partner-progress-review/hooks/usePartnerProgressReview.ts:27
kind: function
core: ce
spec: (none)
summary: Validates a wizard step. Exported for unit testing.
score: 4

function validateText

file: src/cores/ce/utils/csvValidation.ts:78
kind: function
core: ce
spec: (none)
summary: Validate text field with max length
score: 4

function validateZipCode

file: src/cores/ce/utils/csvValidation.ts:206
kind: function
core: ce
spec: (none)
summary: Validate ZIP code
score: 1

function vcardDataUri

file: src/cores/ce/lib/vcard.ts:117
kind: function
core: ce
spec: (none)
summary: Build a URI for the card, suitable as the of adownload anchor ().
score: 4

function wasRedacted

file: src/cores/ce/history/lib/redaction.ts:73
kind: function
core: ce
spec: (none)
summary: True when a redaction was applied to the supplied field or details payload.
score: 4

function writeLeadAssignmentAudit

file: src/cores/ce/utils/leadAssignmentAudit.ts:61
kind: function
core: ce
spec: (none)
summary: Write a CE-60-compatible audit entry for an assignment change.Identifier-only payload — no contact PII or notes.
score: 4

function writeLeadInsurance

file: src/cores/ce/hooks/useLeadInsurance.ts:54
kind: function
core: ce
spec: (none)
summary: CE-71 — single-active-with-soft-history write of a lead’s insurance.This is the ONE canonical write path used by every CE-71 surface (the Add-Leadwizard’s handleSubmit, the lead-profile Insurance card, and any future caller),extracted as a pure function so the AC-1/AC-2 integration tests can exercise theEXACT shape the UI persists against a real, permissioned Supabase client — not are-implementation that could stay green while the UI is broken.OQ-2 semantics: retire any prior active row for (is_active=false, softhistory) before inserting the new active row, so a lead has at most one activeinsurance record. RLS gates the write server-side (ce.leads.insurance.edit); is PHI and is never logged. Trims string inputs to null when blank.
score: 4

Classes

class Part2ConsentError

file: src/cores/ce/utils/part2ConsentGate.ts:21
kind: class
core: ce
spec: (none)
summary: Raised when SUD-screening triage is attempted without a 42 CFR Part 2 consent on record.
score: 4

​ce — Public API surface

​Types & interfaces

​interface ActivitySearchFilters

​type AdminCardUpdate

​interface ApproveIntakeArgs

​type CampaignFormData

​interface CardPreviewData

​interface CEActivityItem

​interface CEDashboardMetrics

​type ConsentChannelType

​type ConsentEvidenceAction

​type ConsentEvidenceMethod

​interface ConsentEvidenceRecord

​interface ContactTagAssignmentFieldProps

​interface ContactTagBadgeProps

​interface ContactTagDialogProps

​type ContractRenewalAction

​interface CreateLeadConversionInput

​interface CreateScreeningInput

​type DbMatchCandidate

​type DbMergeLog

​interface DocumentAdapterError

​interface EmailMatchOptions

​interface EmailMatchResult

​type EmailMatchType

​interface EmailMessageWithMeta

​interface ExtractionSuggestions

​interface FetchContactHistoryArgs

​interface FieldConflict

​interface FormattedPublishError

​interface IdentityMatchedOn

​type IdentityMatchTier

​interface IdentityResolutionMatch

​interface IdentityResolutionPayload

​interface IntakeArtifact

​interface IntakeProposal

​interface IntakeRunStartResult

​interface KeywordMatchResult

​type LeadAssignmentAction

​type LeadStageTransitionKind

​interface MappingPreviewRow

​type MatchCandidateStatus

​interface MatchCandidateWithContacts

​type MergeableField

​interface MergeContactsArgs

​interface MergeContext

​interface MergeFieldDefinition

​interface MergeFieldGroup

​type MergePartner

​type MergeSide

​type MyCardInput

​interface OrgCalendarCapability

​interface PhiPattern

​interface PipelineTrackInput

​type PublishSequenceErrorCategory

​interface PublishSequenceErrorDetail

​interface RecordConsentEvidenceInput

​interface RequestedServicesMultiSelectProps

​interface ScheduleOrgMeetingParams

​type SegmentConditionFormData

​type SegmentCriteriaFormData

​type SegmentFormData

​interface SequenceListFilters

​type ShareSource

​type SmsMessageIntent

​interface SmsNotificationToastProps

​interface TagFilterControlProps

​interface TrackPipelineRowProps

​interface TrendData

​interface TriageCategoryThreshold

​interface TriageFlagPoint

​interface TriageLevelOfCareThreshold

​interface TriageRuleset

​interface TriageScoreWeight

​interface TriageTraceEntry

​interface UpsertSlaConfigInput

​type Urgency

​interface UrgencyAccent

​interface UseActivitiesOptions

​interface UseActivitiesResult

ce — Public API surface

Types & interfaces

interface ActivitySearchFilters

type AdminCardUpdate

interface ApproveIntakeArgs

type CampaignFormData

interface CardPreviewData

interface CEActivityItem

interface CEDashboardMetrics

type ConsentChannelType

type ConsentEvidenceAction

type ConsentEvidenceMethod

interface ConsentEvidenceRecord

interface ContactTagAssignmentFieldProps

interface ContactTagBadgeProps

interface ContactTagDialogProps

type ContractRenewalAction

interface CreateLeadConversionInput

interface CreateScreeningInput

type DbMatchCandidate

type DbMergeLog

interface DocumentAdapterError

interface EmailMatchOptions

interface EmailMatchResult

type EmailMatchType

interface EmailMessageWithMeta

interface ExtractionSuggestions

interface FetchContactHistoryArgs

interface FieldConflict

interface FormattedPublishError

interface IdentityMatchedOn

type IdentityMatchTier

interface IdentityResolutionMatch

interface IdentityResolutionPayload

interface IntakeArtifact

interface IntakeProposal

interface IntakeRunStartResult

interface KeywordMatchResult

type LeadAssignmentAction

type LeadStageTransitionKind

interface MappingPreviewRow

type MatchCandidateStatus

interface MatchCandidateWithContacts

type MergeableField

interface MergeContactsArgs

interface MergeContext

interface MergeFieldDefinition

interface MergeFieldGroup

type MergePartner

type MergeSide

type MyCardInput

interface OrgCalendarCapability

interface PhiPattern

interface PipelineTrackInput

type PublishSequenceErrorCategory

interface PublishSequenceErrorDetail

interface RecordConsentEvidenceInput

interface RequestedServicesMultiSelectProps

interface ScheduleOrgMeetingParams

type SegmentConditionFormData

type SegmentCriteriaFormData

type SegmentFormData

interface SequenceListFilters

type ShareSource

type SmsMessageIntent

interface SmsNotificationToastProps

interface TagFilterControlProps

interface TrackPipelineRowProps

interface TrendData

interface TriageCategoryThreshold

interface TriageFlagPoint

interface TriageLevelOfCareThreshold

interface TriageRuleset

interface TriageScoreWeight

interface TriageTraceEntry

interface UpsertSlaConfigInput

type Urgency

interface UrgencyAccent

interface UseActivitiesOptions

interface UseActivitiesResult