fathom-topics.ts

config/fathom-topics.ts

1. /**
2. * Topic buckets for meeting action items: the human-edited knowledge that turns
3. * a flat list into something you can open one piece of.
4. *
5. * A hand-maintained map and not something cleverer: buckets come from a table
6. * a person edits, like the stage taxonomies and rosters already in this
7. * directory. The alternatives were measured and rejected:
8. *
9. * Fathom has no topic field. `FathomActionItem` carries a description, an
10. * assignee, a completion flag and a playback timestamp, nothing categorical.
11. * `FathomMeeting` has a `meeting_type`, but it is unverified against this
12. * account and is dropped at the collector, so nothing downstream has ever
13. * seen it.
14. *
15. * Grouping by meeting title looks free and is not useful: in the observed
16. * window roughly 40% of meetings are called "Impromptu Zoom Meeting", so the
17. * largest button would carry the least meaning.
18. *
19. * Asking a model would put its judgment on the page as though it were data,
20. * and would only refresh on a weekday morning.
21. *
22. * So the rules are visible and wrong-by-hand rather than wrong-by-inference. A
23. * mis-bucketed item is a line in this file somebody can fix, and anything that
24. * matches nothing lands in Uncategorized in full view: never hidden, never
25. * guessed at. That bucket is the report on this file's coverage (a default
26. * that stands in for knowledge has to be surfaced every run).
27. *
28. * Seeded from a real window: the meeting titles and the item vocabulary
29. * actually present, not an imagined taxonomy. It is deliberately
30. * short. A keyword that catches the wrong thing is worse than one that catches
31. * nothing, because Uncategorized is honest and a wrong bucket is not.
32. */
34. export interface Topic {
35. /** Shown on the button. Keep it short; these sit in a row. */
36. label: string
37. /**
38. * Matched case-insensitively as whole words against the item text and its
39. * meeting title. Order within the list does not matter; order of the list
40. * does: first topic to match wins, so put the specific above the general.
41. */
42. keywords: string[]
43. }
45. /**
46. * Order is the tiebreak and it is a human decision. An item saying "send Ines
47. * the logo refs" matches both Creative and Outreach if both list a word in it;
48. * whichever appears first here takes it. Moving a topic up changes what its
49. * neighbours catch, which is why this is a list and not a map.
50. */
51. export const FATHOM_TOPICS: Topic[] = [
52. {
53. label: 'Creative & design',
54. keywords: [
55. 'image', 'images', 'imagery', 'logo', 'icon', 'icons', 'artwork', 'proof',
56. 'mockup', 'layers', 'refs', 'design', 'creative', 'template', 'banner',
57. 'photoshop', 'illustrator', 'kittl', 'render',
58. ],
59. },
60. {
61. label: 'Outreach & winback',
62. keywords: [
63. 'outreach', 'winback', 'campaign', 'sequence', 'prospect', 'cold',
64. 'follow-up', 'followup', 'newsletter', 'blast', 'abandoned',
65. ],
66. },
67. {
68. label: 'AI & automation',
69. keywords: [
70. 'ai', 'claude', 'gpt', 'automation', 'automate', 'prompt', 'agent',
71. 'workflow', 'extension', 'script', 'zapier',
72. ],
73. },
74. {
75. label: 'Pipeline & numbers',
76. keywords: [
77. 'pipeline', 'numbers', 'forecast', 'quota', 'revenue', 'deal', 'deals',
78. 'lead', 'leads', 'metrics', 'report', 'dashboard', 'flywheel',
79. ],
80. },
81. {
82. label: 'Orders & production',
83. keywords: [
84. 'order', 'orders', 'shipment', 'shipping', 'vendor', 'production',
85. 'invoice', 'fulfillment', 'sample', 'reprint', 'sku',
86. ],
87. },
88. {
89. label: 'Website & product',
90. keywords: ['site', 'website', 'page', 'listing', 'catalog', 'checkout', 'seo'],
91. },
92. {
93. label: 'Partner: Northgate',
94. keywords: ['northgate'],
95. },
96. {
97. label: 'People & leadership',
98. keywords: ['headcount', 'comp', 'hiring', 'onboarding', 'review', 'one-on-one', '1:1'],
99. },
100. ]
102. /**
103. * Where anything that matched nothing goes.
104. *
105. * Not a failure state and not hidden. It is how this file reports its own
106. * coverage: a big Uncategorized bucket means the map is behind the work, which
107. * is a thing to fix rather than a thing to conceal. An item never disappears
108. * because nobody wrote a keyword for it.
109. */
110. export const UNCATEGORIZED = 'Uncategorized'
112. /** Attribute- and id-safe key for a label. */
113. export const topicSlug = (label: string): string =>
114. label.toLowerCase().replace(/[^a-z0-9]+/g, '-').replace(/^-|-$/g, '') || 'topic'
116. /**
117. * Whole-word, case-insensitive. Not substring matching, for the same reason
118. * `matchesFilter` refuses it: "ai" inside "email" and "detail",
119. * "comp" inside "complete" and "company". A keyword that catches the wrong
120. * thing is worse than one that catches nothing.
121. */
122. function mentions(haystack: string, keyword: string): boolean {
123. const escaped = keyword.replace(/[.*+?^${}()|[\]\\]/g, '\\$&')
124. return new RegExp(`(?:^|[^a-z0-9])${escaped}(?:[^a-z0-9]|$)`, 'i').test(haystack)
125. }
127. /**
128. * The topic for one item. Matched against the item text and its meeting title,
129. * because "send the refs" in a meeting called Design Review is a creative
130. * item even though its own words say nothing.
131. */
132. export function topicFor(text: string, meeting: string): string {
133. const hay = `${text} ${meeting}`
134. for (const t of FATHOM_TOPICS) {
135. for (const k of t.keywords) if (mentions(hay, k)) return t.label
136. }
137. return UNCATEGORIZED
138. }
140. export interface TopicBucket<T> {
141. label: string
142. slug: string
143. items: T[]
144. }
146. /**
147. * Group items into buckets, ordered as FATHOM_TOPICS is, with Uncategorized
148. * last. Empty topics are omitted: a button for a bucket with nothing in it is
149. * a control that does nothing, and on a per-person surface it would also
150. * advertise topics from meetings this viewer was not in.
151. *
152. * Every item lands in exactly one bucket, so the counts sum to the input length
153. * and the header can say so (a number and the list under it must be able to
154. * account for each other).
155. */
156. export function bucketByTopic<T extends { text: string; meeting: string }>(
157. items: T[],
158. ): TopicBucket<T>[] {
159. const by = new Map<string, T[]>()
160. for (const item of items) {
161. const label = topicFor(item.text, item.meeting)
162. const list = by.get(label)
163. if (list) list.push(item)
164. else by.set(label, [item])
165. }
166. const ordered = [...FATHOM_TOPICS.map((t) => t.label), UNCATEGORIZED]
167. return ordered
168. .filter((label) => by.has(label))
169. .map((label) => ({ label, slug: topicSlug(label), items: by.get(label)! }))
170. }