Discovery & Intelligence

One logical worker: evidence-backed product, market, technology, and user intelligence · Discovery recommends. Hermes coordinates. Ari decides.
DCP READ-ONLY: CONNECTED DEVELOPMENT / UI PREVIEW DCP BATCH 5/6 SOAK IN PROGRESS TELEMETRY: UNKNOWN COMMAND EXECUTION LOCKED

DISCOVERY INBOX

On-demand Discovery · Continuous Intelligence (data model + UI only in V1)
Discovery recommends. Hermes coordinates. Ari decides.
New
4
from loaded data only
Reviewed
1
from loaded data only
Promoted
1
from loaded data only
Conflicting Evidence
1
from loaded data only

Filters

Simple attribute filters only — no semantic search, no vector DB.

Project

Allexample-crm-toolexample-inventoryexample-note-app

Type

AllFACTUSER COMPLAINTTRENDASSUMPTIONOPPORTUNITY

Confidence

AllLOWMEDIUMHIGH

Relevance

AllLOWMEDIUMHIGH

Mode

AllON DEMANDCONTINUOUS

Status

AllNEWREVIEWEDPROMOTEDDISMISSED

Evidence discipline

Every finding visibly distinguishes FACT / USER COMPLAINT / TREND / ASSUMPTION / OPPORTUNITY and shows source, URL (if present), date, confidence and provenance. UNKNOWN or missing evidence never silently becomes HIGH confidence. Contradictions are shown as CONFLICTING EVIDENCE and are never auto-resolved. Opportunity level (LOW/MEDIUM/HIGH) considers: user pain, evidence strength, strategic relevance, implementation burden, differentiation potential. It remains an assessment, not mathematical truth.

A CONTINUOUS finding is escalated to Hermes only when it is relevant, materially useful, evidence-backed, and not trending noise.

Findings (0 of 7 shown · MOCK/STATIC fixtures — not real current research)

All findings below are clearly-labelled MOCK/STATIC examples with generic placeholder content. None are live research results.

No findings match the current filters.

Promotion to Product Planning (conceptual handoff)

Discovery Finding→Hermes Review→Product Architect / Product Critic→

UI semantics only. V1 has no write API: promotion/dismissal is LOCKED preview. A promoted finding is reviewed by Hermes before the Product Architect / Product Critic act on it — discovery never bypasses the Planning Cell and never creates build tasks from weak signals.