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-audit-33description: |4 Audit PaperLab books for claim, figure, equation, notebook, citation, and5 unit traceability. Use when a book must become scientifically defensible and6 reproducible, especially for NeqSim-backed quantitative chapters.7last_verified: "2026-09-12"8metadata:9 source: https://skillmd.com/skills/equinor/paperlab-scientific-traceability-audit-310---1112# PaperLab Scientific Traceability Audit1314## When to Use1516USE WHEN: a textbook chapter contains numbers, equations, figures, tables, or17engineering recommendations that depend on calculations, simulations, standards,18or source documents. This skill turns technical content into auditable content.1920Pair with:2122- `neqsim-in-writing` for NeqSim claim markers,23- `neqsim-notebook-patterns` for executable notebooks,24- `neqsim-regression-baselines` for stable examples,25- `neqsim-standard-requirement-extraction` for clause-level standards evidence.2627## Traceability Objects2829Track six object types:3031| Object | Required Evidence |32|--------|-------------------|33| Numeric claim | notebook cell, test, baseline, source table, or citation |34| Figure | source file, notebook, generated script, or approved source document |35| Equation | symbol definitions, units, source citation, and implementation link if used by NeqSim |36| Table | data source, units, and update path |37| Standard statement | standard code, revision, clause or paraphrased requirement |38| Recommendation | preceding evidence that supports the action |3940## Marker Rules4142Use existing `neqsim-in-writing` markers for high-value NeqSim-backed content:4344```markdown45<!-- @neqsim:claim46 test: src/test/java/neqsim/book/<book_slug>/<TestName>.java47 baseline: src/test/resources/baselines/book/<book_slug>/<baseline>.json48-->49```5051```markdown52<!-- @neqsim:figure source=notebooks/<notebook>.ipynb cell=<cell-id-or-index> -->53```5455```markdown56<!-- @neqsim:eq method=neqsim.package.ClassName#methodName -->57```5859Do not mark every sentence. Prioritize values and equations that students will60reuse, cite, or compare in exercises.6162## Audit Workflow63641. Run `book-skill-stack-plan` and inspect traceability dimensions.652. Run `book-evidence-check` and `book-figure-dossier`.663. For each core chapter, identify the top 3 to 5 numerical or equation-based67 claims that deserve markers.684. Confirm every cited notebook exists and has executed output or generated figures.695. Confirm units in prose, tables, and figures match `nomenclature.yaml`.706. For standards-heavy chapters, add clause-level or paraphrased evidence rather71 than broad standard names.7273## Pass Criteria7475A chapter is traceability-ready when:7677- every main figure has source provenance and a discussion block,78- the most important numerical claims have markers or explicit citations,79- all equations define symbols and cite origin or implementation,80- SI units are present in tables and figure axes,81- worked examples have notebooks or tests that can be rerun,82- recommendations are supported by nearby evidence.8384## Output Pattern8586```markdown87## Scientific Traceability Audit: <chapter>8889- Status: ready | needs-markers | needs-validation | blocked90- High-value claims needing markers:91 - <claim and location>92- Figures needing stronger provenance:93 - <figure>94- Equations needing source or implementation link:95 - <equation>96- Unit inconsistencies:97 - <quantity>98- Recommended next edit: <one concrete action>99```100101## Safety Rules102103- Never invent a notebook, test, citation, or standards clause.104- If evidence is missing, mark the claim as unverified or lower confidence.105- Do not claim regulatory compliance from a candidate standards map alone.106- Keep private source filenames out of public outputs unless approved.