Architecture · LikeC4

SciX Agent

Agent-navigable knowledge layer: turns 32.4M papers + 299M citation edges into MCP-navigable structural topology

built evolving planned research risk

The whole picture

System landscape

The system in context, then opened up into its containers.

SciX — system landscape

SciX — system landscape

index
SciX — containers (over one Postgres + pgvector store)

SciX — containers (over one Postgres + pgvector store)

scixSystem

Agent-navigable knowledge layer: turns 32.4M papers + 299M citation edges into MCP-navigable structural topology

Risks & open questions

Risks & open questions

risks
Research & off-surface tracks

Research & off-surface tracks

research

Inside each box

Containers & components

Each part decomposed into the components that implement it. Every box links to its source in the interactive explorer.

Ingest & sync — components

Ingest & sync — components

ingestContainer

Acquires the corpus from ADS + external sources, normalizes, and loads via COPY with OA/preprint gating

Retrieval stack — hybrid RRF + Qdrant dense lane

Retrieval stack — hybrid RRF + Qdrant dense lane

retrievalContainer

Hybrid search: INDUS dense (Qdrant) + BM25/lexical (ts_rank_cd) fused via RRF, optional cross-encoder rerank

Citation-graph engine — components

Citation-graph engine — components

graphContainer

Graph analytics (PageRank/HITS/Leiden) + citation-context intent, claim provenance, and replication inference

Entity & knowledge layer — components

Entity & knowledge layer — components

entityContainer

LLM + NER extraction, multi-vocabulary concept substrate, and multi-lane entity resolution (~9M entities, 57.7M links)

MCP server — the 15-tool agent surface

MCP server — the 15-tool agent surface

mcpContainer

Agent interface: 15 tools (search, citation, entity, provenance, graph, session) over stdio + HTTP, with a pinned contract

Visualization layer — components

Visualization layer — components

vizContainer

FastAPI JSON API + SSE trace streaming + static dashboards (sankey / heatmap / streamgraph / umap / ego / provenance)

How it runs

Walkthrough flows

Dynamic views — the narrative spine of the system, step by step.

Walkthrough — corpus ingest pipeline

Walkthrough — corpus ingest pipeline

ingestFlow

Metadata harvests universally; body text only through the OA/preprint gate (publisher TDM-clause risk). Validate any new index with a ≤50k scratch build + forced-index-scan smoke test before a multi-hour build.

Walkthrough — hybrid search request

Walkthrough — hybrid search request

searchFlow

RRF (k=60) fuses the INDUS dense lane (Qdrant, ADR-013) with the BM25/lexical lane (ts_rank_cd + body GIN); the cross-encoder rerank is an optional final stage.

Walkthrough — claim_blame provenance

Walkthrough — claim_blame provenance

claimBlameFlow

Walks reverse references over citation_contexts to the earliest non-retracted origin, weighted by citation intent. Structural-citation coverage is sparse, so the hop chain is best-effort over the covered subgraph.

Walkthrough — entity resolution (M13 multi-lane)

Walkthrough — entity resolution (M13 multi-lane)

entityFlow

resolve_entities is the single entry point. The router tries cache, then a 5% local_ner canary, then a bulkheaded live_jit lane, degrading to static-core. local_ner is currently a CPU stub.

Where it runs

Deployment

What runs where, and the process & data boundaries between the pieces.

Deployment — where each piece runs

Deployment — where each piece runs

deployment

Explore it live

The figures above are static exports. The interactive explorer lets you pan, zoom, follow relationships, and jump from any box to the source.