--- name: voltpeer-submission description: Match a battery Review to a journal and audit its proposal, cover letter, files, rights, and declarations against current official article-type rules. --- # Journal selection and submission preflight For model/tool adaptation or resuming a task, read [the execution guide](references/EXECUTION.md). DeepSeek Flash uses short stages and checkpoints; DeepSeek Pro can plan larger text/evidence batches, with the same scientific checks. Reply in the user's language with the result, usable result/preview links and material unresolved questions. Keep mappings, configuration, logs and recovery records inside the project's `.voltpeer/` folder; do not link them in a normal final reply. Provide the corresponding source record only when the user explicitly requests provenance. Use only capabilities actually available in the current model and host. Use this when the user is selecting a journal, preparing a proposal, cover letter, or submission package, or asking whether a Review is ready to submit. Journal rules are time-sensitive. Check the official journal and publisher pages for the *exact article type* and record each URL and access date in a journal ledger. Use [JOURNAL_CHECK.md](assets/templates/JOURNAL_CHECK.md) if there is no existing checklist. ## Choose the target using the manuscript Compare audience, article type, scope, expected level of critical synthesis, invitation/proposal rules, length, display-item limits, reference style, open-access policy and cost, and recent comparable Reviews. Identify the manuscript changes required for each plausible venue. A prestige ranking by itself is not a fit analysis. If a proposal or editor inquiry is required or prudent, prepare a concrete synopsis and evidence of differentiation first. ## Official-rule ledger For each requirement record: article type, requirement, status (`checked`, `not applicable`, `unresolved`), official URL, access date, exact supporting passage or section, file/location checked, and owner of any open action. Re-check close to submission; instructions for another article type or an older cached page do not settle a conflict. If two sources disagree, record both and escalate the unresolved interpretation to the corresponding author or journal rather than declaring a pass. Typical items include title/abstract/keywords, word and reference limits, figure/table count and specifications, graphical abstract or highlights, broader-context or significance text, review proposal form, data/code availability, competing interests, funding, author contributions, ethics and AI-use declarations where required, cover letter, permissions, supplementary material, and file naming. Check author names/order and affiliations with the authors; a task assignment is not an authorship decision. ## Package gate Check that the cover letter names the actual journal and article type, the manuscript and supplemental files are current and internally consistent, figure citations and captions match files, references resolve, permissions are documented, and the submission portal's requested statements are present. For reused artwork, a correct credit line does not replace a permission grant or compatible license. Check *effective* image resolution at final print size. Separate `ready`, `ready with named author decision`, and `blocked` items. A package is ready only when every applicable requirement is checked and the authors have approved the science and authorship. If the user has authorized submission, use the approved files; otherwise deliver the reviewable package and ledger. Do not send editor inquiries or submit a manuscript on the strength of a checklist alone.