Paper-to-PPTX, Router

Routing protocol

For an edit to an existing deck, reuse its paper source, narrative, terminology, and assets. Change the requested slides and any affected cross-slide references; do not rerun paper intake or rebuild the deck's story unless the request requires it. Inspect changed slides and run the existing final PPTX audit before delivery. A requested outline or explanation alone does not require creating a deck.

For a new task, load the core and matching resources below. Reuse already loaded guidance on follow-ups; load more only when the task needs it.

1. Load the manifest and the core layer

Read manifest.yaml. It declares the paper_type axis, the allowed values, and the file paths each value maps to.

Also read every file listed under always_load. These hold the purpose and core principle, the lean operating mode and toolchain policy, the 9-step workflow spine, and the output/quality rules that apply to every deck, plus the shared Terminology Ledger used to keep technical terms consistent across slides.

2. Classify the paper type

Decide the paper_type value using the manifest's detect: hint and the source:

• discovery, discovery / mechanism papers (question-to-evidence arc). Default.
• methods, methods / AI / tool / algorithm papers (problem-to-solution arc).
• resource, resource / dataset / atlas / omics / benchmark papers (workflow-to-validation arc).
• clinical, clinical / population / intervention studies (design-to-inference arc).
• materials, materials / chemistry / physics / engineering papers (property-to-mechanism / design-to-performance arc).
• review, reviews / perspectives / commentaries / meta-analyses (evidence-map arc).

State the detected value in one short line to the user before designing slides, so they can correct you cheaply.

3. Load the matching fragment