Architecture

A selected high-level view of NeuralScio areas, modeled workflows, data stores, boundaries, and lifecycles.

This page presents selected high-level architecture from the public Architecture view. It is not a complete map of every NeuralScio capability.

Product areas

Local AI runtime (domain)

  • Document assistant
  • External research tools

NeuralScio desktop (domain)

  • Article viewing
  • Desktop application shell
  • Saved article access

Key flows

Ask a question about a document

Selected high-level steps:

  1. Question submitted
  2. Assistant request accepted

Participants: Document assistant.

Related documentation: AI Features.

Use an external research tool

Selected high-level steps:

  1. Tool request received
  2. Tool response prepared

Participants: External research tools.

Related documentation: MCP & Headless.

Open a saved article

Selected high-level steps:

  1. Saved article selected
  2. Available cached PDF opened

Participants: Article viewing, Saved article access.

Related documentation: PDF Viewer.

Create and select a Research Project

Selected high-level steps:

  1. Project details submitted
  2. New project selected

Participants: Research Project lifecycle, Research Projects.

Related documentation: Research Projects.

Components and capabilities

Document assistant (component)

External research tools (component)

Saved article access (component)

Article viewing (component)

Desktop application shell (component)

Research Project lifecycle (component)

Research Projects (component)

Data and storage

Document retrieval index (data store)

Persistence classification: persistent.

Article PDF cache (data store)

Persistence classification: cache.

Saved article library (data store)

Persistence classification: persistent.

Research Project records (data store)

Persistence classification: persistent.

Boundaries

Local AI processing (boundary contract)

Status: local.

External research tools (boundary contract)

Status: external.

Remote article access (boundary contract)

Status: external.

Lifecycles

Current Research Project workspace selection

States named in this model: no-project-selected, project-selected.

Explicit transitions:

  • no-project-selected → project-selected — A visible Research Project is selected and its persisted record is loaded

Research Project record status

States named in this model: active, archived, draft.

Explicit transitions:

  • draft → active — Project contract update sets Active status
  • active → draft — Project contract update sets Draft status
  • draft → archived — Project is archived
  • active → archived — Project is archived
  • archived → draft — Project is unarchived