lauphilip/au-btech-literature-review-agent

1. Overall shape

- This is a single .NET 10 application named AuBtechReviewAgent.

- It combines a Blazor UI with a backend review pipeline for literature synthesis and PRISMA-style reporting.

2. Application entry and UI shell

- Program.cs boots the app and wires services.

- Components/App.razor, Routes.razor, and the layout components define the browser-facing shell.

- MainLayout, NavMenu, and ReconnectModal indicate a stateful interactive UI, with Bootstrap used for styling.

3. Primary user-facing screens

- Home.razor is the main landing/control page.

- SpecMatrix.razor is the most important domain screen: it likely surfaces the structured screening/matrix view for the review process.

- Error.razor and NotFound.razor handle failure and routing boundaries.

4. Core orchestration engine

- PrismaReviewEngine.cs is the central workflow coordinator.

- From the README, the engine’s role is to execute the review pipeline end-to-end: query sources, screen candidates, ingest manuscripts, chunk documents, and synthesize PRISMA-compliant outputs.

5. Source-adapter boundary

- IAcademicSource.cs defines the abstraction for literature providers.

- ArxivSource, ElsevierSource, GoogleScholarSource, IeeeXploreSource, and ResearchGateSource are provider-specific adapters.

- This isolates external source behavior from the rest of the pipeline and makes the ingestion stage pluggable.

6. Document processing and grounding

- DocumentRAGUtility.cs is the document-analysis layer used to turn raw papers into retrievable context for synthesis.

- The README describes a chunking and grounding flow: PDFs are parsed, split into overlapping text windows, and passed into the synthesis stage so outputs are tied back to source evidence rather than free-form text.

7. Review data model

- ReviewModels.cs likely contains the shared domain objects used across the pipeline: papers, screening results, evidence chunks, report items, and trace records.

- This forms the contract between source ingestion, screening, ranking, and reporting.

8. Quality / venue ranking subsystem

- JournalRankingMatcher.cs is a separate enrichment step for mapping venues to quality/ranking data.

- The ScimagoData folder contains year-specific CSVs from 2020–2025, which act as a local reference dataset for journal/venue ranking lookups.

9. State management and UI coordination

- UiStateContainer.cs likely holds shared application state across components, such as current review progress, selected dataset, or generated results.

- This is the main bridge between the review engine and the interactive Blazor views.

10. Outputs and artifacts

- prisma-report.json is a key generated artifact and represents the structured PRISMA checklist/report output.

- The README also describes a disposable workspace containing source PDFs and a process trace, which implies the pipeline produces auditable run artifacts rather than only a final textual summary.

11. Configuration and runtime boundaries

- appsettings.json and appsettings.Development.json hold environment-specific settings for the pipeline and UI.

- Properties/launchSettings.json shows it is intended to run as a local .NET app during development.

- There is no visible database layer; the architecture appears file- and service-driven, with local CSVs and generated JSON artifacts as the main persistence surfaces.

12. End-to-end data flow

- User action in the Blazor UI triggers the review engine.

- The engine queries external academic sources through the provider interfaces.

- Candidate papers are screened and enriched with ranking data.

- PDFs are ingested and chunked for grounded synthesis.

- The final outputs are the PRISMA report and traceable review artifacts, which are then displayed back in the UI.

13. Important architectural boundary

- The key design boundary is between external evidence acquisition and internal synthesis.

- Source adapters and local ranking CSVs collect inputs; the review engine and document utilities transform them into auditable, reproducible report artifacts.