Skip to content

[v4] Align recommendations with COPE investigation flowcharts #9

Description

@cpitzi

Summary

Structure the auditor's recommendations for flagged references to map directly to COPE (Committee on Publication Ethics) investigation procedures.

See roadmap/v4-features.md (Priority 5) for full specification.

Why This Matters

When a managing editor finds a problem, the next question is "what do I do about it?" COPE flowcharts provide standardized investigation procedures. If the auditor's output already maps to COPE procedures, the editor can move from detection to action without a separate triage step.

Key COPE Flowcharts to Map

  • Suspected fabricated data in a submitted manuscript
  • Suspected fabricated data in a published article
  • Suspected redundant (duplicate) publication
  • Authorship disputes
  • Suspected ghost/gift/guest authorship

Implementation Approach

  1. Research and document relevant COPE flowcharts (they're publicly available)
  2. Map each risk classification tier to specific COPE procedures
  3. Add COPE flowchart references to the prompt's recommendation output
  4. Include concrete next-step language in forensic notes

Acceptance Criteria

  • High-risk references include specific COPE flowchart reference
  • Recommendations include concrete next steps per COPE procedures
  • Output distinguishes author query, editorial investigation, and publisher notification
  • Forensic Appendix includes COPE methodology reference
  • Language is appropriate for managing editor audience (not legal/compliance jargon)

Dependencies

  • Requires reviewing COPE flowchart documentation
  • Add docs/cope-alignment.md with the mapping

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    documentationREADMEs, CLAUDE.md, and other proseprompt-engineeringPrompt design and optimizationv4Planned for v4

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions