domains / families / science / itcs-artifact-evaluation

itcs-artifact-evaluation

separate

Use to adapt the idea of an "artifact" to a pure-theory venue — at ITCS there is no artifact-evaluation track, no code, and no badges; the analogue is making every claim independently verifiable through complete proofs in the submitted PDF and a matching public full version, plus checkable finite objects for any computational content.

When to use

• ITCS artifact evaluation
• verifying mathematical proofs
• checking computational content
• ITCS verifiability checklist
• managing public full versions
• auditing borrowed theorems

When not to use

• empirical CS artifact tracks
• code submission
• Docker image creation
• build script generation
• environment pinning
• post-acceptance artifact submission

Skill page

Source