# ZoneGaze Research Module

## Role

First-party shared Matrix capability for Deep Research workflows and reusable evidence artifacts.
Research is not a left-rail tab, Marketplace card, or standalone plugin surface. Users reach it
through other plugins, with Chat as the first supported entry point.

## Source Boundaries

- Product/module catalog: `flow/contracts/src/zonegaze-products.ts`
- Capability manifest: `flow/common/src/plugin-services.ts`
- Internal research UI components: `flow/web/src/components/plugins/matrix-research-plugin-panel.tsx`
- Runtime services: `flow/runtime/src/research/`
- CLI and operational commands: `flow/runtime/src/commands/research.ts`
- Local infrastructure: `infra/deep-research/`

## Important Current-State Note

The product catalog currently records source path `plugins/research/`, but Research is not
installable or directly openable in the Matrix shell. The active implementation still lives in
shared `flow/web`, `flow/runtime`, and `infra/deep-research` surfaces. Treat it as a shared
capability module with a not-yet-extracted package boundary.

## Current Capability Signals

- Capability registry: `deep-research`
- Runtime/package status: `ready`

## Major Features

- Create and queue research sessions
- Save cited sources, findings, reports, and artifact bundles
- Verify and export saved research sessions
- Attach research artifacts to chat and future Matrix modules
- Run local infrastructure through a wrapper, Local Deep Research, SearXNG, and optional local
  model/crawler services

## Current Matrix Coordination

- `Chat`: this is the strongest current integration. Research sessions can be attached to chats,
  displayed as evidence cards, refreshed, and reused with citation metadata.
- `Flow`: research sessions are workspace/project-scoped and can be attached to a project today.
- `Joplin`: exported reports and findings are a practical current path for durable project memory.
- `Open Design`: cited research is a strong design input today, but much of that reuse is still a
  deliberate handoff rather than automatic artifact wiring.
- `Code`: research findings can guide implementation work now; broader direct code-surface handoff
  is still a future coordination target.
- `Exo`: Research can coexist with local-model infrastructure, but Research does not universally use
  Exo as its runtime path today.

## Related Docs

- [Deep Research infrastructure](../../infra/deep-research/README.md)
- [Matrix feature catalog](../features/matrix-feature-catalog.md)
- [Open-source projects and upstreams](../reference/open-source-projects.md)
- [Matrix plugin coordination](plugin-coordination.md)
