check-sentence-by-sentence

Static analysis of paper claims against code verifies methodology and results by mapping claim-bearing sentences to specific file:line locations in your project, returning a per-sentence JSON list with quote-to-code mappings or NOT FOUND.

Tracing paper prose to code uses the astra.yaml narrative.method and narrative.findings fields to translate text into decision and output IDs, locating corresponding file:line references across methodology, results, discussion, and appendix sections.

Yes, auditing a LaTeX paper is supported by reading the TeX source from work/reference/source/ (or work/reference/document.md), enumerating sections by headings, and statically mapping claim-bearing sentences to code locations without running anything.

Static reproducibility analysis is the process of auditing claim-bearing sentences in a paper against implementation and result computations present in a codebase, ensuring methodology traceability and code provenance without executing the project.

Paper verification requires locating the project root astra.yaml file to guide the mapping process, and expects the paper substrate to exist in work/reference/ as either TeX source files or a markdown document.

Claims that cannot be traced to specific implementation or result computations in the codebase are explicitly marked as NOT FOUND in the per-sentence JSON list, highlighting missing or untraceable methodology evidence.