PaperLab Scientific Traceability Audit
When to Use
USE WHEN: a textbook chapter contains numbers, equations, figures, tables, or
engineering recommendations that depend on calculations, simulations, standards,
or source documents. This skill turns technical content into auditable content.
Pair with:
neqsim_in_writing for NeqSim claim markers,neqsim-notebook-patterns for executable notebooks,neqsim-regression-baselines for stable examples,neqsim_standard_requirement_extraction for clause-level standards evidence.
Traceability Objects
Track six object types:
| Object |
Required Evidence |
| Numeric claim |
notebook cell, test, baseline, source table, or citation |
| Figure |
source file, notebook, generated script, or approved source document |
| Equation |
symbol definitions, units, source citation, and implementation link if used by NeqSim |
| Table |
data source, units, and update path |
| Standard statement |
standard code, revision, clause or paraphrased requirement |
| Recommendation |
preceding evidence that supports the action |
Marker Rules
Use existing neqsim_in_writing markers for high-value NeqSim-backed content:
<!-- @neqsim:claim
test: src/test/java/neqsim/book/<book_slug>/<TestName>.java
baseline: src/test/resources/baselines/book/<book_slug>/<baseline>.json
-->
<!-- @neqsim:figure source=notebooks/<notebook>.ipynb cell=<cell-id-or-index> -->
<!-- @neqsim:eq method=neqsim.package.ClassName#methodName -->
Do not mark every sentence. Prioritize values and equations that students will
reuse, cite, or compare in exercises.
Audit Workflow
- Run
book-skill-stack-plan and inspect traceability dimensions.
- Run
book-evidence-check and book-figure-dossier.
- For each core chapter, identify the top 3 to 5 numerical or equation-based
claims that deserve markers.
- Confirm every cited notebook exists and has executed output or generated figures.
- Confirm units in prose, tables, and figures match
nomenclature.yaml.
- For standards-heavy chapters, add clause-level or paraphrased evidence rather
than broad standard names.
Pass Criteria
A chapter is traceability-ready when:
- every main figure has source provenance and a discussion block,
- the most important numerical claims have markers or explicit citations,
- all equations define symbols and cite origin or implementation,
- SI units are present in tables and figure axes,
- worked examples have notebooks or tests that can be rerun,
- recommendations are supported by nearby evidence.
Output Pattern
## Scientific Traceability Audit: <chapter>
- Status: ready | needs-markers | needs-validation | blocked
- High-value claims needing markers:
- <claim and location>
- Figures needing stronger provenance:
- <figure>
- Equations needing source or implementation link:
- <equation>
- Unit inconsistencies:
- <quantity>
- Recommended next edit: <one concrete action>
Safety Rules
- Never invent a notebook, test, citation, or standards clause.
- If evidence is missing, mark the claim as unverified or lower confidence.
- Do not claim regulatory compliance from a candidate standards map alone.
- Keep private source filenames out of public outputs unless approved.
1---2name: paperlab-scientific-traceability-audit3description: Audit PaperLab books for claim, figure, equation, notebook, citation, and unit traceability. Use when a book must become scientifically defensible and reproducible, especially for NeqSim-backed quantitative chapters.4---56# PaperLab Scientific Traceability Audit78## When to Use910USE WHEN: a textbook chapter contains numbers, equations, figures, tables, or11engineering recommendations that depend on calculations, simulations, standards,12or source documents. This skill turns technical content into auditable content.1314Pair with:1516- `neqsim_in_writing` for NeqSim claim markers,17- `neqsim-notebook-patterns` for executable notebooks,18- `neqsim-regression-baselines` for stable examples,19- `neqsim_standard_requirement_extraction` for clause-level standards evidence.2021## Traceability Objects2223Track six object types:2425| Object | Required Evidence |26|--------|-------------------|27| Numeric claim | notebook cell, test, baseline, source table, or citation |28| Figure | source file, notebook, generated script, or approved source document |29| Equation | symbol definitions, units, source citation, and implementation link if used by NeqSim |30| Table | data source, units, and update path |31| Standard statement | standard code, revision, clause or paraphrased requirement |32| Recommendation | preceding evidence that supports the action |3334## Marker Rules3536Use existing `neqsim_in_writing` markers for high-value NeqSim-backed content:3738```markdown39<!-- @neqsim:claim40 test: src/test/java/neqsim/book/<book_slug>/<TestName>.java41 baseline: src/test/resources/baselines/book/<book_slug>/<baseline>.json42-->43```4445```markdown46<!-- @neqsim:figure source=notebooks/<notebook>.ipynb cell=<cell-id-or-index> -->47```4849```markdown50<!-- @neqsim:eq method=neqsim.package.ClassName#methodName -->51```5253Do not mark every sentence. Prioritize values and equations that students will54reuse, cite, or compare in exercises.5556## Audit Workflow57581. Run `book-skill-stack-plan` and inspect traceability dimensions.592. Run `book-evidence-check` and `book-figure-dossier`.603. For each core chapter, identify the top 3 to 5 numerical or equation-based61 claims that deserve markers.624. Confirm every cited notebook exists and has executed output or generated figures.635. Confirm units in prose, tables, and figures match `nomenclature.yaml`.646. For standards-heavy chapters, add clause-level or paraphrased evidence rather65 than broad standard names.6667## Pass Criteria6869A chapter is traceability-ready when:7071- every main figure has source provenance and a discussion block,72- the most important numerical claims have markers or explicit citations,73- all equations define symbols and cite origin or implementation,74- SI units are present in tables and figure axes,75- worked examples have notebooks or tests that can be rerun,76- recommendations are supported by nearby evidence.7778## Output Pattern7980```markdown81## Scientific Traceability Audit: <chapter>8283- Status: ready | needs-markers | needs-validation | blocked84- High-value claims needing markers:85 - <claim and location>86- Figures needing stronger provenance:87 - <figure>88- Equations needing source or implementation link:89 - <equation>90- Unit inconsistencies:91 - <quantity>92- Recommended next edit: <one concrete action>93```9495## Safety Rules9697- Never invent a notebook, test, citation, or standards clause.98- If evidence is missing, mark the claim as unverified or lower confidence.99- Do not claim regulatory compliance from a candidate standards map alone.100- Keep private source filenames out of public outputs unless approved.
equinor