Skill: PaperLab Book Knowledge Graph
Purpose
Build a review graph for a PaperLab book so editors can see how chapters,
figures, notebooks, standards, source folders, and skills connect. Use this
when a book needs gap analysis, traceability review, duplicate-concept review,
or a visual map of the editorial workflow.
Inputs
Use the book artifacts when they exist:
book.yamlcoverage_matrix.mdsource_manifest.jsonfigure_dossier.jsonstandards_map.jsonskill_stack_plan.json- chapter notebooks and figures
Workflow
- Run the prerequisite audits:
book-source-inventory, book-figure-dossier, book-standards-map, and
book-skill-stack-plan.
- Run
python paperflow.py book-knowledge-graph <book_dir>.
- Open
book_knowledge_graph.html and review isolated nodes, missing skill
links, figures without discussion, chapters without notebooks, and standards
that appear in text but have no clause-level evidence.
- Use the graph during adversarial review to decide which chapters need
synthesis, source retrieval, or de-duplication.
Output
book_knowledge_graph.json with nodes[] and edges[].book_knowledge_graph.html as a self-contained review page.
Review Questions
- Does every figure-heavy chapter connect to
technical_figure_understanding
and figure-discussion?
- Do equipment chapters connect to standards and safety skills?
- Do notebook-heavy chapters have traceability markers?
- Are case-study chapters connected to source documents and skills?
Safety Rules
- Treat the graph as an editorial map, not proof of standards compliance.
- Do not expose private source documents in a public graph; include only path
labels and high-level source areas unless the source is public.
- Regenerate after chapter order, figure, source, or standards-map changes.
1---2name: paperlab-book-knowledge-graph3description: Skill: PaperLab Book Knowledge Graph4---5# Skill: PaperLab Book Knowledge Graph67## Purpose89Build a review graph for a PaperLab book so editors can see how chapters,10figures, notebooks, standards, source folders, and skills connect. Use this11when a book needs gap analysis, traceability review, duplicate-concept review,12or a visual map of the editorial workflow.1314## Inputs1516Use the book artifacts when they exist:1718- `book.yaml`19- `coverage_matrix.md`20- `source_manifest.json`21- `figure_dossier.json`22- `standards_map.json`23- `skill_stack_plan.json`24- chapter notebooks and figures2526## Workflow27281. Run the prerequisite audits:29 `book-source-inventory`, `book-figure-dossier`, `book-standards-map`, and30 `book-skill-stack-plan`.312. Run `python paperflow.py book-knowledge-graph <book_dir>`.323. Open `book_knowledge_graph.html` and review isolated nodes, missing skill33 links, figures without discussion, chapters without notebooks, and standards34 that appear in text but have no clause-level evidence.354. Use the graph during adversarial review to decide which chapters need36 synthesis, source retrieval, or de-duplication.3738## Output3940- `book_knowledge_graph.json` with `nodes[]` and `edges[]`.41- `book_knowledge_graph.html` as a self-contained review page.4243## Review Questions4445- Does every figure-heavy chapter connect to `technical_figure_understanding`46 and `figure-discussion`?47- Do equipment chapters connect to standards and safety skills?48- Do notebook-heavy chapters have traceability markers?49- Are case-study chapters connected to source documents and skills?5051## Safety Rules5253- Treat the graph as an editorial map, not proof of standards compliance.54- Do not expose private source documents in a public graph; include only path55 labels and high-level source areas unless the source is public.56- Regenerate after chapter order, figure, source, or standards-map changes.
equinor