paper-narrative

Paper Narrative — manuscript → brief → figure arc → editorial loop

paper-narrative is the outermost figure workflow. It judges the paper-level story before figure-composer designs any one figure. The inputs are the work itself: a manuscript (or abstract), figure captions, and the current full deck.

Open Science Notebook call

Every notebook_execute request whose code uses a function named in this skill includes this skill ID:

{ "kernelSkillIds": ["paper-narrative"], "code": "print(paper_brief_schema())" }

kernelSkillIds contains the skill ID; function calls belong in code. This request is complete as written: call the named functions directly and do not add an import or discovery step.

Required inputs and trust labels

Keep these inputs distinct throughout the workflow:

• manuscriptVersionId: immutable manuscript Artifact Version (an abstract-only manuscript is allowed) and the reviewed manuscript text read from it.
• abstractText: reviewed abstract text when available; use it for bounded brief reasoning while retaining the full manuscript Version as source provenance.
• captionsVersionId: immutable captions Artifact Version and the reviewed per-figure caption or claim text read from it.
• deckVersionId: immutable deck Artifact Version containing every current figure in review order.
• rulesVersionId: immutable design-rules Artifact Version, used only as a reference so the editor judges story rather than visual craft.
• figureDataVersionIds: immutable data Artifact Versions grouped by figure.
• figureWidthMmByFigure: reviewed positive venue width for each figure; the downstream composer must not invent this physical output constraint.

Manuscript, captions, deck, and data are source inputs. Every brief, review, arc, move, omission, and proposed analysis is model-generated and requires human review. Never describe generated text as manuscript evidence or source data. Preserve the input Version identities when publishing or delegating downstream work.