Skip to content
Internals — research note: investigation or findings, not a description of shipped behaviour.
Unverified: This page has not yet been anchored to automated code tests.

SCIENTIA Automated Research: Historical Roles and Extension Research (2026)

SCIENTIA Automated Research: Historical Roles and Extension Research (2026)

Section titled “SCIENTIA Automated Research: Historical Roles and Extension Research (2026)”

Vox SCIENTIA is more than a nanopublication emitter: it is a knowledge platform (vox-scientia) plus publication orchestration (vox-publisher), fed by deep research (vox-research-shim) and hybrid retrieval (vox-search). Nanopubs are one rigor tier on the output ladder — alongside Zenodo deposits, RO-Crate packages, manuscript scaffolds, and syndication — all behind a human-gated review SSOT.

This document:

  1. Maps historical roles of computers and AI in scientific research (1960s–2026) to Vox capabilities and gaps.
  2. Records a severity-ordered code review of the current SCIENTIA + research integration (June 2026).
  3. Proposes a unified research loop that connects coding agents, spontaneous research, and optional gamification.
  4. Sequences extension work aligned with existing plans (Tracks A–E plus Track F: Unified research loop).

Term disambiguation (common voice-transcription confusions):

Spoken / writtenVox canonical
TAN, TANTIVLYTantivy — Rust full-text index behind tantivy-lexical / VOX_SEARCH_TANTIVY_ROOT
Tavily, TavoliTavily — live web retrieval vendor; Rust SDK in vox-search
GraphifyExternal Graphify pipeline + local graphify-out/ convention; P0 status in Vox

External research for §2 used Tavily Research API (2026-06-16) plus NLM/Cochrane/nanopub primary sources. Tavily CLI (tvly) was unavailable in the agent environment; MCP tavily_research was used instead.


2. Historical roles of computers and AI in research

Section titled “2. Historical roles of computers and AI in research”

Five eras structure how automated research evolved and what researchers still expect tools to save.

flowchart TB
subgraph eras [Historical eras]
E1["1960s-80s: IR and bibliographic DBs"]
E2["1990s-2000s: Systematic review and citation graphs"]
E3["2010s: Reproducibility and preregistration"]
E4["2018-2023: Semantic search and ML screening"]
E5["2024-2026: LLM agent deep research"]
end
subgraph vox [Vox SCIENTIA layers]
L1[Signal producers and scout]
L2[Retrieval: CRAG Tavily Tantivy Graphify]
L3[Claim and novelty verdict ladder]
L4[Human gate nanopub RO-Crate]
L5[Scholarly syndication Zenodo]
end
E1 --> L2
E2 --> L3
E3 --> L4
E4 --> L2
E4 --> L3
E5 --> L1
E5 --> L2
YearMilestoneCapabilityResearcher time impactPrimary source
1960sMEDLARS mechanized indexingBatch bibliographic processing at NLMWeeks → days for curated index updatesNLM MEDLARS history
1971MEDLINE online searchInteractive biomedical literature retrievalSearch weeks → minutesNLM Circulating Now
1993Cochrane CollaborationStandardized systematic review methodsReduced ad-hoc duplication; reviews still multi-monthCochrane Handbook Ch. I
2010Nanopublications (Groth et al.)Atomic, signed, RDF-linked scientific assertionsFull paper → citable micro-assertionGroth et al. 2010
2012+OSF registrations / preregistrationTime-stamped, frozen study plansPost-hoc bias → auditable protocolOSF Registrations guide
2015Semantic ScholarAI-enhanced paper discovery and TL;DR summariesManual scan → ranked semantic resultsSemantic Scholar About
2019RO-Crate 1.xFAIR packaging of data, software, metadata (JSON-LD)Manual provenance assembly → structured crateRO-Crate introduction
2023–24Elicit systematic reviewLLM-assisted screening and extraction (PRISMA-oriented)Up to ~80% review time reduction (vendor claim)Elicit systematic review
Feb 2025OpenAI Deep ResearchMulti-step autonomous web research agentTasks framed as days/weeks of human work → minutesOpenAI introducing deep research
2025–26Gemini Deep ResearchPlan → search → read → iterate → cited report (async)Literature review / due diligence accelerationGemini Deep Research API
2026Tavily /research endpointSingle-call multi-hop vendor research for agentsReplaces hand-rolled search loops for integratorsTavily Jan 2026 ship blog
Historical capabilityVox today (shipped)Missing for “more than nano publisher”
Batch literature searchTavily /search Tier 4 + OpenAlex/Crossref/S2 prior artTavily /research, /extract, /crawl; arXiv-native tier; citation-diversity gate
Citation chainingpublication-novelty-fetch federated prior artMandatory embedding path; SPECTER2/Qdrant KNN in novelty scoring
Systematic review screeningclaim_extractor + MiniCheck verdict ladderBatch screening UI; inter-rater export; PRISMA trace
PreregistrationOrchestrator preregistration/ + scientia_prereg tableDoc drift: gap map cites crates/vox-prereg/ (absent); see §8
Reproducibility packagesRO-Crate + replay runner scaffoldMeasured replay score auto-written to worthiness rubric
Semantic literature AISCIENTIA claim pipeline on publication pathAuto-bridge from vox research run sessions
Agent deep researchrun_research + CRAG multi-hop + MCP vox_research_runReliable planner; mesh emission; eval harness
MicropublicationsOffline RSA nanopub + test-server gateAggregate approved claims → IMRaD manuscript (Gap C)
Codebase knowledge graphsGraphify P0 (vox graphify status)P1 lexical ingest + MCP query in retrieval bundle
Model routing observabilityOpenRouter catalog + research Lane G synthesisProvider Atlas → ModelRegistry feedback loop

Design implication: SCIENTIA should operate as a research OS — discover → retrieve → extract → assess novelty → human approve → emit at chosen rigor — with coding-agent sessions writing into the same ledger as spontaneous literature research.


sequenceDiagram
participant Agent as CodingAgent
participant RS as vox_research_shim
participant VS as vox_search
participant OR as OpenRouter
participant TV as Tavily
participant SC as vox_scientia
participant Human as Researcher
participant Out as NanoPub_Zenodo_Manuscript
Agent->>RS: vox research run
RS->>OR: planner + synthesize
RS->>VS: CRAG multi-hop
VS->>TV: Tier4 search optional
RS->>SC: claim_extractor optional paths
Note over RS,SC: FindingCandidate mesh emission not wired
SC->>Human: discovery inbox review
Human->>SC: ApprovalToken
SC->>Out: nanopub / archive / syndicate

Crate responsibilities:

CrateRole
vox-scientiaClaims, novelty inspect bridge, review flow, nanopub, RO-Crate, producers, manuscript scaffold
vox-publisherPrior art fetch, worthiness, syndication, discovery ranking, research mesh intake
vox-research-shimrun_research pipeline, session persistence, web gather
vox-searchCRAG, web tier, Tavily client, optional Tantivy/Qdrant
vox-research-eventsContract types: FindingCandidateV1, ResearchEvent, mesh broadcast

Human-gated review SSOT: review_flow.rs. Four-layer no-auto-publish design: scientia-micropublication-ssot-and-surfacing-design-2026.md.


Ordered by severity. Status updated after June 2026 implementation waves.

Fixed June 2026: findings 1 (scientia-claims feature), 4 (empty/no-trace → InsufficientEvidence), 6 (planner_degraded + user-visible metadata), 14 (cache store via upsert_knowledge_node). Fixed implementation waves (June 2026 plan): 2 (embedder fail-fast + golden harness), 3 (bundle SSOT unification), 5 (discovery bridge + mesh), 7 (Tavily extract/research tiers), 8 (Graphify P1 lexical leg), 9 (assess_novelty callsite audit), 11 (research kudos when gamify enabled).

  1. Research shim claim path diverges from SCIENTIA claim extractor — FIXED June 2026 (scientia-claims feature routes through claim_extractor first)

    • claims.rs uses LLM cascade when runtime feature is on, else returns empty claims.
    • claim_extractor/pipeline.rs is the real VeriScore → atomic → MiniCheck pipeline.
    • Risk: vox research run can complete with zero claims while publication-extract-claims produces verdicts.
  2. Novelty scoring without embedder degrades to lexical-only — MITIGATED June 2026 (require_embedder_for_online_novelty when VOX_SCIENTIA_REQUIRE_EMBEDDER=1; golden harness added)

  3. Bundle type drift — FIXED June 2026 (NoveltyEvidenceBundleContract alias + parity tests)

    • Hand-written NoveltyEvidenceBundleV1 (publisher) vs typify types in vox-research-events — conversion seams at research_mesh.rs and MCP tools.
  4. Empty query traces still score Novel — FIXED June 2026

    • novelty.rs gates InsufficientEvidence when all traces fail, but bundles with no traces and empty hits remain Novel.
    • Risk: offline runs appear novel when retrieval never executed.
  1. Deep research and SCIENTIA are parallel, not unified — FIXED June 2026 (discovery_bridge.rs persists finding candidates; mesh emission + session telemetry)

    • run_research persists sessions but does not emit FindingCandidateV1 / DiscoverySignal into SCIENTIA mesh (deep-research roadmap §6).
    • Largest researcher time sink: manual re-entry into publication manifests.
  2. Planner silent fallback — FIXED June 2026 (planner_degraded on plan + metadata JSON)

    • planner.rs passthroughs on cascade failure; CRAG multi-hop then runs on a single query.
  3. Tavily /research and /extract unwired — FIXED June 2026 (tavily_extract.rs, tavily_research.rs behind env flags)

  4. Graphify not in retrieval bundle — PARTIAL June 2026 (P1 lexical leg in scientia_prior_art.rs; full MCP query tool still open)

  5. Novelty assess path vs raw scorer — FIXED June 2026 (arch test guards; CLI/GUI/MCP route through assess_novelty)

    • ChronoFilter and EvidenceConflictDetector are wired in assess_novelty(), but not all CLI/GUI paths may call assess_novelty vs raw AtomicNoveltyScorer::score — verify at each callsite before claiming full temporal/conflict coverage.
  1. GUI covers ~10% of scientia CLI — vox-gui-scientia-coverage-audit-2026.md.
  2. Gamification = Console discovery exposure only — PARTIAL June 2026 (research_session_complete kudos when gamify enabled; publication never gated)
  3. Prereg documentation drift — see §8.
  4. graphify-out/ collision with CI artifacts blocks trustworthy P1 ingest.
  5. Pipeline cache always miss — FIXED June 2026 (store + read both use knowledge_nodes via upsert_knowledge_node / list_memories_by_type) — pipeline_cache.rs.
  1. Production nanopub network publish intentionally unimplemented (correct posture).
  2. OpenRouter spend HUD tile contract exists; GUI tile incomplete.
  3. Tantivy behind heavy-retrieval — lean builds lack local lexical corpus.
  • Human-gated review + ApprovalToken in review_flow.rs.
  • InsufficientEvidence verdict + empty bundle with None scores (June 2026 fixes).
  • Contradicted claim verdict reachable via MiniCheck contradiction path.
  • Web gather + CRAG multi-hop shipped; CLI + MCP research surfaces exist.
  • Embedder seam + code-uniqueness producer scaffold for automated discovery.

IntegrationShippedPlanned / stubSSOT
OpenRoutervox_actor_runtime::llm, routing policy, live catalog, research synthesis Lane GUnified model-routing.v1.yaml; GUI spend tilemodel-orchestration-ssot-audit-2026.md
Tavily/search via TavilySearchClient; budget + fail-open/extract, /research, /crawltavily-integration-ssot.md
Tantivylexical_tantivy.rs behind featureDefault-on for research builds; 0.22→0.26 bumpsearch-retrieval-ssot-2026.md
Vox SearchCRAG, web tier, retrieval bundle, run_multi_hop_web_researchWikipedia/arXiv/S2 dedicated tiersSame
GraphifyRegistry + vox graphify status / MCP vox_graphify_statusP1–P3 search + MCP query toolsgraphify-integration-research-2026-06-16.md

All LLM calls must stay on vox_actor_runtime::llm per root AGENTS.md — no direct vendor SDKs at callsites.


6. Researcher time-savings backlog (ranked)

Section titled “6. Researcher time-savings backlog (ranked)”

Priority = estimated hours saved per active researcher per month divided by implementation cost (S/M/L).

RankGapEst. time savedCostTrack
1Unified research → SCIENTIA mesh emission4–8 h/mo (no manual re-entry)MF
2Route vox research run claims through vox-scientia extractor2–4 h/mo (consistent verdicts)SF
3Mandatory embedder on novelty-fetch1–3 h/mo (fewer false novelty decisions)SA
4Tavily /extract for weak snippets1–2 h/mo (less manual page reading)MPhase 3
5Graphify P1 in retrieval bundle1–2 h/mo (structural codebase answers)LPhase 3
6Novelty eval harness (precision/recall)Prevents costly false publishesMA
7Collated results dashboard (session → archive)1 h/mo (status visibility)MPhase 4
8IMRaD manuscript scaffold from approved claims2–5 h per publicationLPhase 4
9Optional gamify kudos for research milestonesEngagement; not blockingSPhase 5
10Pipeline cache for identical queriesAPI cost; marginal wall-clockMOps

When Socrates policy or explicit vox research run triggers:

  1. Plan — OpenRouter cascade in planner.rs (must surface failure to user, not silent passthrough).
  2. Retrieve — vox-search CRAG loop; Tavily when policy enables; future Tantivy for repo-local legs.
  3. Ground — vox_scientia::claim_extractor on synthesis + evidence passages.
  4. Assess — assess_novelty() with embedder + chrono/conflict on candidate claims.
  5. Surface — emit FindingCandidateV1 to mesh → GUI DiscoveryInbox + WS scientia.discovery.surfaced.
  6. Human gate — record_claim_review() → ApprovalToken.
  7. Emit — user-selected rigor: nanopub build, Zenodo archive run, manuscript draft, syndication.

One publication session (publication_session_id from review_flow.rs) should aggregate:

  • Research session IDs (scientia_research_sessions)
  • NoveltyEvidenceBundle artifacts
  • Claim verdicts
  • Review decisions
  • Archive status (Zenodo / SWH / nanopub test server)

Extend ScientiaDashboard.tsx rather than adding a parallel surface.

When [gamify] is enabled:

  • Emit mesh kudos (not XP inflation) for research_session_complete, novelty_assessed, publication_approved.
  • Reuse Console discovery ledger pattern (vox.scientia.review action id) — surface streaks in StatusBar only; never gate publication on gamify state.

Three sources disagree on prereg location:

SourceClaim
scientia-self-publication-gap-map-2026.md §0crates/vox-prereg/ complete
where-things-live.mdPoints to crates/vox-prereg/
vox-scientia/src/lib.rsComment: prereg still planned in this crate
Workspace reality (2026-06-16)No vox-prereg crate in root Cargo.toml; implementation lives under vox-orchestrator/src/preregistration/ + scientia_prereg DDL in vox-db

Follow-up: Update gap map and where-things-live.md in a dedicated doc-hygiene PR; wire orchestrator prereg gate to SCIENTIA publication CLI where still missing.


Align with 2026-06-12-scientia-research-pipeline-upgrade.md Tracks A–E. Add Track F: Unified research loop.

PhaseFocusKey deliverables
0Doc hygiene (this file) + prereg drift ticketResearch index link; gap map correction PR
1Track A remainderMandatory embedder; bundle SSOT unification; novelty eval harness; callsite audit for assess_novelty
2Track F (highest ROI)Mesh emission from run_research; scientia claim extractor in shim; discovery inbox auto-fill
3Retrieval depthTavily extract/research eval; Tantivy corpus row; Graphify P1
4Beyond nanopubIMRaD scaffold; collated dashboard; Provider Atlas → model registry
5Gamify optionalKudos events; StatusBar streaks

Explicitly out of scope: production nanopub network publish; live arXiv API submission; new shell glue scripts (VoxScript-first policy).


CheckCommand
Research pipeline compilescargo check -p vox-research-shim -p vox-scientia -p vox-search
Novelty unit testscargo test -p vox-scientia inspect_bridge::novelty
Prior art testscargo test -p vox-publisher scientia_prior_art
Novelty golden harnesscargo test -p vox-publisher novelty_golden_harness
Research CLI previewvox research preview "test query"
Graphify statusvox graphify status --json
Doc frontmattercargo run -p vox-doc-pipeline -- --lint-only --paths docs/src/architecture/scientia-automated-research-historical-extension-research-2026.md


Appendix A — Tavily research request metadata

Section titled “Appendix A — Tavily research request metadata”
  • Request ID: 2339f716-ebaf-4b7a-977b-5783ee7347a0
  • Date: 2026-06-16
  • Model: mini
  • Response time: ~60s
  • Method: MCP tavily_research (CLI tvly not on PATH)