Intelligence Hub
Overview
The Intelligence Hub is where all customer signals land after being collected from your Feedback Channels — and where the AI clustering worker drafts Insights: distilled, actionable items ready for product triage. Think of it as the morning briefing the system runs for you overnight.
How to get there: Click Intelligence Hub in the left sidebar (between Ask Mind and Competitive Intel).
Note: internally the bucket value is still radar (you may see this in CSV exports or MCP responses). The user-facing name is always "Intelligence Hub".
The Five Tabs
Active Insights awaiting your decision
Each Insight is an AI-drafted brief with attached customer signals, a recommended action, and structured metadata. Start here.
Acknowledged but no engineering action
Insights you've marked as Noted (strategic intel) or Addressed (ops/comms handled). Searchable for future reference; logged to the MIND Ledger.
Dismissed Insights
Insights you've dismissed as not relevant. Recoverable but out of your active triage view.
Themes ranked by volume or growth
The nightly clustering worker groups related signals into themes that persist over time. Sort by Volume (most signals in last 30 days) or Growth (week-over-week velocity). Click any theme to open a drill-down drawer with the underlying signals, then promote it into a Radar feature in one click. See the Trending Themes section below for details.
Every individual signal before clustering
Searchable, filterable list of raw signals — for inspection, ad-hoc linking, semantic search, or when you want to dig into the evidence directly rather than work from AI-drafted Insights.
What is an Insight?
An Insight is what the nightly clustering worker produces from a cluster of related signals. Each Insight carries:
- Title + Summary — what the customer/market is asking for
- Insight Brief — a 6-section narrative the AI drafts: What customers want / Why it matters / Suggested approach / Notable quotes / Evidence breakdown / Suggested next step. This is what you read to triage.
- Intelligence Type — gates the Accept flow (see next section)
- Capability Group — the functional area (e.g. "Mobile Application Reliability")
- Business Areas — multi-tag from a controlled vocabulary: acquisition, activation, retention, revenue, support, quality
- Linked Signals — the actual customer feedback backing the Insight
- Competitive Context — when the Insight came from competitor/market signals
Intelligence Types
The AI tags every Insight with a type that determines which action you take. The primary button on each Insight changes label automatically — you don't have to remember the mapping.
| Type | What it is | Primary Action |
|---|---|---|
| Feature Proposal | A buildable feature the AI thinks you should ship | Accept → Roadmap |
| Change Request | A tweak/enhancement to a capability you already have | Accept → Roadmap (as change) |
| Strategic Signal | Pricing / positioning / pivot / segment intelligence — not buildable | Mark as Noted |
| Ops Awareness | Doc gap, comms one-off, internal awareness item | Mark as Addressed |
The Four Terminal Actions
Every Insight has four buttons (the primary one varies by type above):
- Accept / Mark as Noted / Mark as Addressed — type-aware primary action.
- Dismiss — moves to Archive. Use when the Insight is spam, irrelevant, or doesn't fit your product.
- Mark as Closed — generic acknowledgment ("we saw this, handled elsewhere"); moves to Closed.
- Merge → existing feature — re-attaches the Insight's signals onto an existing Roadmap feature and removes the Insight. Use when the AI proposed something already on your Roadmap.
When you Accept a feature_proposal or change_request, the full Insight Brief carries over to the Roadmap drawer's Evidence tab — so downstream PRD/Story generation respects the original customer/market framing.
Auto-AI on Accept
Under Product Settings → "Auto-generate on Accept", you can enable automatic PRD + Estimation generation whenever you Accept an Insight to the Roadmap. Off by default (PRD generation costs 10 AI credits, Estimation costs 1).
Trending Themes
The Trending tab shows clusters of related signals as themes. Each theme card carries a trend badge:
- NEW — first observed in the last 14 days.
- ↑ x% — week-over-week growth in signal count (Growth sort).
- ↓ x% — declining theme; usually safe to deprioritize.
- 🔥 Spiking — unusually large jump from prior period; worth a look today.
The card also shows the signal count for the last 30 days, the last 7 days, plus the dominant intent and impacted area. Two ranking modes:
| Sort | Ranks by | Best for |
|---|---|---|
| Volume | Signal count (30d), recency tiebreaker | "What are people talking about most right now?" |
| Growth | Velocity % (with prior-period baseline), recency tiebreaker | "What's getting louder?" — surfaces emerging signals before they dominate volume |
Click any theme to open a drawer with the underlying signals (paginated, 20 per page). From the drawer, hit Create feature to spin up a Radar feature pre-populated with the theme's title, summary, impacted area, and all linked signals already attached as evidence. The theme is then archived so it doesn't double-promote.
A nightly worker runs HDBSCAN clustering on signal embeddings, then an LLM titles each new cluster. Themes that already exist get matched and updated (no re-titling unless the underlying signal mix changes meaningfully). Themes with no signals in 60 days are auto-archived.
Raw Feed
For each individual signal in the Raw Feed, you can:
- View Details — original text, AI summary, classification, sentiment
- Link to Feature — attach signal as evidence to an existing Roadmap feature or Insight
- Unlink — remove a previous link
- Semantic Search — natural-language search across all signals
- Delete — remove from the system
Each signal shows: source channel, author info if available, timestamp, and whether the AI has auto-linked it.
Best Practices
- Triage Insights daily, not signals — Work from the New tab. Let clustering do the heavy lifting; only drop to Raw Feed when you want to dig into the evidence.
- Trust the type — When an Insight is tagged strategic_signal, the right action is Mark as Noted, not "build it." Push it to the MIND Ledger as intel and move on.
- Merge when it fits — If an Insight overlaps with a Roadmap feature you already have, Merge re-attaches the signals so you don't lose evidence.
- Use Dismiss for spam, not low-priority — Dismissed Insights go to Archive (out of active view). For "we've handled this elsewhere," use Mark as Closed.