Academic paper: AI-assisted development disclosure section
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 23
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Description
Draft the methodology/acknowledgments disclosure a journal would expect,
distinct from CONTRIBUTING.md's "On AI-assisted development" section
(that one is dev-facing; this one needs to satisfy a journal's disclosure
policy).
Framing to keep consistent with CONTRIBUTING.md and the project's public
community replies: credit human direction and ownership as the primary
frame, be specific about what was AI-assisted (implementation scaffolding,
multi-platform validation runs, sanitizer testing, documentation) versus
human-directed (architecture decisions, the underlying math, validation
methodology, and the citation audit in #88), and don't oversell AI's share
of the work.
Sepand flagged this as one of two things that matter most before adding
more depth to the project, alongside the citation audit (#88). A voice
message with more journal-specific guidance is expected as a follow-up.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading CONTRIBUTING.md and the project’s public community replies to align the disclosure’s framing. Draft a journal-ready methodology or acknowledgments section that separates AI-assisted activities from human-directed work, including the citation audit in #88. Check the expected voice message for journal-specific guidance before considering it done.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 62/100