Noetis Scientific Review · Business engine

Research Paper Review Engine

Critically reviews a supplied research paper or study package.

Answers: "Can an engine critique a study's methods and conclusions?" For researchers and research funders.

Reviews a single supplied study. For multi-document synthesis use the Research engine. Not a substitute for peer review.

Available today

Implemented

Implemented: runs on the shared runtime with supplied material. One bounded development check on 2026-10-12 took 127.9s with 15 model calls and ended "incomplete". That is a development signal, not an evaluation. Customer access is by approved account.

What you send

  • Question
  • Supplied text material
  • Text material up to 150,000 characters per run

What comes back

  • Structured scientific critique with source references.
  • Findings with the located quote and a support status from claim review
  • Release status: released, incomplete with reasons, or failed
  • Executed roles, usage and measured cost

Sample

Authored illustration. Written by Encevra to show the workflow. Not customer data and not a recorded model output.

Critique this study summary.

Hypothesis: app use reduces anxiety. Design: 40 volunteers, no control group, 2 weeks. Result: anxiety score fell from 18 to 15 (p=0.04, one of 12 outcomes tested). Conclusion: "the app treats anxiety".

The real response shape is documented in the API reference.

How the workflow operates

Each role is a responsibility in the workflow, served by a third party language model. More roles are not automatically better; depth and routing decide which run.

Built with

  • OpenAI
  • Anthropic

Models this engine uses: OpenAI (GPT), Anthropic (Claude). Specialists run on OpenAI models and the claim review and final brief on Anthropic models. If a provider has a temporary failure, the step can fall back to an OpenAI model, and the run records that.

Question and Design Analyst

Examine the hypothesis and study design.

Methods Reviewer

Evaluate methods and reproducibility information.

Statistical Reviewer

Check analyses and uncertainty.

Results Reviewer

Compare conclusions with reported findings.

Literature Context Analystruns only when needed

Compare relevant literature when retrieval is available.

Limitations Reviewer

Identify bias, alternative explanations and replication needs.

Evidence and deployment

Evidence

This engine reads the text you send in the request. Each released finding carries the exact quote and its character span in that text, located mechanically before release. Quotes that cannot be located are labelled Insufficient evidence and never shown as source verified. Interpretation is reviewed as a separate step, and gaps such as a missing clause describe what was searched instead of citing text that is not there.

Deployment

Runs on Encevra hosted infrastructure using the third party models listed above. Every model call and fallback is checked against the deployment policy first. Private cloud and air-gapped deployment are planned; discuss deployment requirements.

What it does not handle

  • Clinical diagnosis
  • Treatment recommendations
  • Claims of completed peer review
  • Authorized source retrieval is not available: Not built. Engines read only supplied material.
  • Uses only supplied material. No freshness guarantee beyond the documents provided.
  • Required for every output during trials.

How to integrate

Send "engine": "scientific-review" with your question and material from your server. Keys stay server side.

How to evaluate it

No published result for this workflow yet. Build a small answer key from your own work and compare against a strong single model baseline. See the evaluation checklist and method.

Cost and rights: pricing and licensing. Showing outputs to your own customers needs a written agreement.

Optional technical details

We reply by email. No newsletter.

Related engines

Content reviewed 2026-10-12 by the Encevra engine team. Engine version 0.1.0 on noetis-core-1.