Skip to article frontmatterSkip to article content
Site not loading correctly?

This may be due to an incorrect BASE_URL configuration. See the MyST Documentation for reference.

Methods

Overview of the 21-phase Expert Review Pipeline v29. Green boxes indicate LITREVIEW agents (scientific judgment), blue boxes indicate DATAML agents (mechanical work), and the gray box is the coordinator. Red dashed lines mark information barriers where actor-critic separation is enforced. Orange diamonds indicate gate checkpoints where the coordinator verifies compliance before advancing. Phase 21 (Deploy Polish) is the post-deployment UX gate — runs after the Phase 20 push to main confirms a green build.

Figure 1:Overview of the 21-phase Expert Review Pipeline v29. Green boxes indicate LITREVIEW agents (scientific judgment), blue boxes indicate DATAML agents (mechanical work), and the gray box is the coordinator. Red dashed lines mark information barriers where actor-critic separation is enforced. Orange diamonds indicate gate checkpoints where the coordinator verifies compliance before advancing. Phase 21 (Deploy Polish) is the post-deployment UX gate — runs after the Phase 20 push to main confirms a green build.

This review was produced through a structured, multi-phase computational pipeline. All claims in this section are derived from recorded pipeline metadata and gate artifacts; no post-hoc characterizations have been added.

Review Request

This review was initiated by a single user request that fixed the topic, scope, and high-level argument arc. The full text of that request is preserved verbatim in provenance/review_request.md and quoted below. Phase 1 (Scope and Thesis) translated this request into the structured gate_scope.json (title, audience, target paper count, cluster definitions, and table of contents) that drove all subsequent phases.

[PIPELINE INSERTS THE USER’S TASK DESCRIPTION HERE, VERBATIM, AS A BLOCKQUOTE. NO PARAPHRASING, NO SUMMARIZATION, NO REORDERING. The only permitted edits are mechanical re-flow of whitespace that the chat client stripped — split a run-together TOC back into a numbered list; convert a run-together skills-list into a bullet list. The Editorial note section below MUST document any such mechanical change.]


Literature searches were conducted across four databases: PubMed, Europe PMC, OpenAlex, and bioRxiv. Searches were organized around topic clusters defined in the scope document, each corresponding to a body section of the review:

ClusterTopicPapers RetrievedFull-Text Obtained
1[PIPELINE FILLS THIS]
Total

Paper counts above are pre-deduplication totals across all clusters.

Inclusion and Exclusion Criteria

The scope document specified the following inclusion criteria:

Papers were excluded if they did not address the review topic or related circuit mechanisms. Preprint–journal duplicate pairs were resolved during integration by replacing preprints with their published journal versions where identified.

Full-Text Retrieval

Full-text retrieval was attempted for all retrieved papers using open-access sources (Unpaywall, Semantic Scholar, PubMed Central), publisher APIs (Elsevier, Springer Nature), and institutional proxy access. The overall full-text retrieval rate was [PIPELINE FILLS THIS].

Evidence Extraction

Structured evidence extraction was performed for each cluster, producing evidence packages containing:

MetricCount
Total findings[PIPELINE FILLS THIS]
Total conflicts[PIPELINE FILLS THIS]
Total figure comparisons[PIPELINE FILLS THIS]

Each evidence package was stored as a versioned artifact linked to its cluster, enabling traceability from any claim in the review back to its source evidence.

Citation Verification

[PIPELINE FILLS THIS — citation verification results from Phase 16]

Pipeline Execution

The review was produced through a 21-phase pipeline. Key execution metadata from completed phases:

PhaseDescriptionStatusKey Outputs
1Scope definitionPending
2Evidence gathering & compliancePending
3Citation infrastructure (citation_key_map, author_name_table)Pending
4Scaffold approvalPending
5Per-section evidence curationPending
6Figure auditPending
7Section draftingPending
8Critic reviewPending
9Bibliography assemblyPending
10IntegrationPending
11Introduction & ConclusionPending
12Bookend CriticPending
13MethodsPending
14–20Remaining phasesPending

Figure Reproducibility

[PIPELINE FILLS THIS — figure reproducibility details from pipeline execution]

Figure generation notebooks are preserved in figures/notebooks/ and can be re-executed against the archived evidence packages to reproduce all figures.

Pipeline Skills

The full pipeline is encoded as nineteen version-controlled skill files committed to this repository under skills/: thirteen worker skills that produce content and seven validator skills that gate each phase with named pass/fail checks. Each skill is a markdown specification that was loaded by the relevant agent at the relevant phase — re-running a phase from scratch requires only the skill plus the upstream artifacts. Information barriers are enforced by omission: writer agents cannot see critic rubrics, figure auditors cannot see the argument arc, and citation verifiers cannot see the fix protocol. Validator skills are loaded only by their gate frames and never by the actor frames they evaluate.

SkillRolePhase(s)
comprev-orchestrator-v29.mdCoordinator protocol governing phase routing, delegation, and gate artifacts0–21 (all)
comprev-scoping.mdWorker protocol for LITREVIEW scoping: clusters, sections, length targets, evidence parameters, plan content1
comprev-evidence-gathering.mdWorker protocol for LITREVIEW evidence-gathering frames (one per topic cluster)2
comprev-reviewer-agent.mdUniversal LITREVIEW core — how to evaluate literature and write review prose2, 4, 6–8, 10–12, 16, 18
comprev-scaffold.mdScaffold construction: argument arc, section plans, figure specs, style guide4
comprev-figure-construction.mdWorker skill for producing publication-quality figures from figure_data JSON7
comprev-figure-audit.mdBlinded figure-auditor protocol — cross-study comparison validity6
comprev-section-writing.mdWriter protocol: MyST formatting, citation discipline, synthesis rules7
comprev-critic.mdBlinded section-critic protocol — unsupported claims, misrepresented evidence8, 12
comprev-integration.mdCross-section integration passes; Introduction, Conclusion, and Abstract drafting10, 11
comprev-verification.mdCitation-triple verification against CrossRef and full-text sources15–17
comprev-fix-execution.mdFix-application protocol: replace bib entries, correct claim sentences18
comprev-dataml-phases.mdWorker protocol for DATAML agents — Phase 1 materialisation, citation infrastructure, BibTeX, CrossRef1, 3, 5, 9, 13–15, 17, 19–20
comprev-scoping-validator.mdPhase 1 scope JSON, evidence-parameters consistency, plan structure, prompt-verbatim provenance gate1V
comprev-evidence-validator.mdEvidence-package schema and coverage gate2V
comprev-curation-validator.mdPer-section evidence package size and content gate5V
comprev-citation-validator.mdcitation_key_map (Phase 3) and BibTeX (Phase 9) — DOI resolution, CrossRef matching, key uniqueness, author match3V, 9V
comprev-triples-validator.mdCitation-triples extraction-completeness gate15V
comprev-myst-validator.mdMyST build, structural, figure, heading, plugin-directive, and evidence-population gate; directive whitelist, repo-wide forbidden-lexicon, and author-identity placeholder checks7V, 14V, 19V, 20V
comprev-deploy-polish.mdPost-deployment UX gate: tier-A static checks (forbidden lexicon, author identity, directive rendering, frontmatter leak, figure dropdown, asset paths, plugin data, internal links) run against the built Pages-artifact tarball; tier-B live-URL checks (per-page HTTP, external link health) with manual-checklist fallback when the deployed site is sandbox-inaccessible21

To re-run this pipeline against a different topic, clone the ComputationalReviewTemplate repository (which ships these same nineteen skills), update myst.yml with a new title and table of contents, and issue a single coordinator prompt — the orchestrator skill then drives all twenty phases to completion.

Reproducibility Statement

All pipeline artifacts are preserved and versioned, enabling full reproduction of this review:

The pipeline used no manual curation steps. All evidence extraction, section drafting, critic review, and integration were performed computationally, with gate artifacts serving as checkpoints between phases.