Sci Paper Manager

SCI Paper Manager

Turn verified project evidence into auditable supporting plans and status artifacts. Follow project-local and research lifecycle evidence rules; involve academic-manuscript-writing when actual manuscript integration is in scope.

Separate artifact layers from manuscript stages

Maintain two artifact layers when the project uses them:

1. draft_core: venue-neutral story, claims, sections, figures, tables, and evidence.
2. submission_targets/<target>: official template, manuscript, figures/tables, supplementary files, declarations, cover letter, checklist, compliance report, submitted versions, and revisions.

These are storage layers, not manuscript lifecycle stages. academic-manuscript-writing selects the writing/revision stage and owns prose, mainline, response content, and canonical integration. For a new draft, prefer a coherent argument before venue-specific packaging; preserve an existing venue-bound or submitted manuscript without requiring a new draft-core tree.

Ground every paper-facing claim

For claim-bearing changes to a claim map, status ledger, or figure/table plan:

1. Read project handoff and paper status.
2. Read the claim-evidence map.
3. Read only cards/raw artifacts tied to the claims in scope.
4. Classify claim strength as main_claim, trend_only, diagnostic_only, negative_boundary, internal_exploration, or unsupported.
5. Record contrary evidence, protocol compatibility, and missing validation.

Do not treat old prose as evidence. Report any mainline discrepancy to the manuscript owner instead of rewriting the prose here.

For a supplied frozen package inventory, inspect file identity and required metadata within that task; do not repeat full scientific claim reconciliation merely to list files. Mark missing verification rather than implying the inventory establishes submission readiness.

Maintain paper artifacts

Use the bundled templates when the project lacks equivalents:

• PAPER_STATUS.md
• CLAIM_EVIDENCE_MAP.md
• FIGURE_PLAN.md
• TABLE_PLAN.md
• submission_checklist.md
• guideline_notes.md
• format_compliance_report.md

Keep experiment numbers in cards/registries and link to them rather than duplicating mutable tables across status files.

Verify target-venue requirements

Before changing a submission package, read cached guideline_notes.md. If missing, stale, or conflicting, verify current official author guidelines, template, article type, limits, structure, figures/tables, references, supplementary material, declarations, data/code availability, anonymity, and upload rules. Record source URL/path and access date.

Never guess a requirement. Mark ambiguity needs_verification.

Reconcile before submission

Check that manuscript, figures/tables, raw results, claim map, supplementary files, public code, and data/code statements use one compatible protocol and frozen version. Label mismatches protocol_mismatch; do not claim full reproducibility until resolved.

Return updated claim maps, plans, requirement notes, checklists, or package inventories to the current requester. A direct artifact task can finish without invoking a writing or research owner. For actual manuscript integration, return to the already active writing owner; route unsettled evidence to the research owner, and use sci-result-auditor for a needed bounded consistency check. Do not decide final readiness, broaden claims, rewrite manuscript prose, or perform an irreversible submission action.