AIPR Overview Generator STEP 2 v1.74


You will receive 1 attached paper file.

Produce a single standardized paper overview in a clean-room environment.
Base your output exclusively on the contents of the attached file.
Do not reference any external evaluations, metrics, prior scores, citation counts, reputation signals, institutional standing, or publication prestige.

Before generating the overview:
Confirm that the entire manuscript, including appendices, is accessible and readable.
If any portion cannot be accessed or parsed, retry ingestion up to two additional times.
If full access cannot be confirmed after three attempts, output exactly:
Evaluation Aborted: Full manuscript access not confirmed.

Write in a neutral, declarative academic tone.
No references to the attached file except through the header metadata fields.
No promotional language.
No consensus framing.
No comparative ranking.
No weaknesses or criticisms.
No speculation beyond what is explicitly stated in the manuscript.
No em dashes.


OUTPUT FORMAT (exact)
Return the entire overview inside a single triple-backtick code block. Do not include any text before or after the code block. Version evaluated refers to the specific document artifact used during analysis 
(e.g., repository version, publisher PDF, archived manuscript copy, or author manuscript).


Title:
Author(s): <last, first when possible>
Publication date: <YYYY-MM-DD if available>
Version:
Version evaluated:
DOI:

OVERVIEW
[350–600 words, plain paragraphs with short section headings allowed.
Maximum 600 words.

Begin with a clear summary paragraph that reflects the primary emphasis of the manuscript and is accessible to an educated science reader. Explain the central problem addressed and describe the main contribution or development presented.

After the opening paragraph, organize the remainder using short neutral section headings where appropriate. Headings may include, but are not limited to:

Core Framework
Governing Equation
Fundamental Objects
Derived Mechanisms
Mathematical Structure
Simulation Architecture
Key Results
Limiting Regimes
Empirical, Experimental, or Computational Interface

Use only headings that are explicitly supported by the manuscript. Omit categories that do not apply. Do not insert placeholder statements such as “none provided.”

If the manuscript presents testable predictions, falsifiability criteria, experimental comparisons, numerical validation, or measurable deviations, describe them factually without assessing feasibility, significance, or likelihood. If the manuscript does not include such content, omit this section entirely.

Construct Fidelity Rules:
- If the manuscript defines a central wave function, operator, tensor, equation, principle, dataset, algorithm, or architecture by name or acronym, it must be named exactly as labeled.
- Do not replace named constructs with generic paraphrases.
- At first appearance, define each named construct in plain technical language and explain its structural role before presenting formal expression.
- Limit symbolic expressions to no more than three inline expressions.
- Avoid stacking multiple operator or tensor definitions in a single sentence.

Narrative Discipline:
- Maintain explanatory clarity without promotional tone.
- Integrate structural details into the narrative rather than listing isolated terms.
- Do not append bullet lists of technical nouns.
- Do not include calls to action.
- Do not include external links or references beyond what appears in the manuscript.

Conclude with a short synthesis paragraph summarizing what the paper formally establishes, derives, computes, or demonstrates, and under what stated assumptions or regimes.]

At the very end of the output, include the following delimiter exactly as written:

=============================