CUMCM 2026 Submission Compliance and Packaging

This skill is used only when

competition_mode: CUMCM_2026

. First read

../_references/CUMCM_2026_RULES.md

in full, with the latest official notice from the National Organizing Committee taking the highest priority.

This stage finalizes the submission files. It does not remodel the problem, alter the results, or pass manual review on behalf of the participating team. If substantive errors are found, return them upstream through the

6verity

issue-routing process and rerun the affected stages after the issues are fixed.

Prerequisites

Before starting, confirm the existence of:

A compiled single-paper PDF and the corresponding Typst/LaTeX source files;
```
reports/VERIFY_REPORT.md
```
;

compliance/AI_USAGE_LOG.md

HUMAN_REVIEW_LOG.md

, and

SOURCE_LOG.md

;

```
code/run_all.py
```
, the environment manifest, and all necessary source code;
```
results/final_results.json
```
and constraint/validity check records;
```
compliance/private_identity_terms.txt
```
, for local scanning only.

If any of H1–H4 has not been confirmed as

HUMAN_APPROVED

by the participating team, or if the standard acceptance checks still contain a hard failure, stop packaging and write

SUBMISSION_READY = false

. Approval status must not be filled in on the team's behalf.

1. Paper Hard Gates

Cross-check the source files, PDF text, PDF metadata, and rendered output from every page:

Page 1 must be a dedicated abstract page containing the title, abstract, and keywords; there must be no commitment letter or dedicated identification page.
In principle, the abstract must occupy only page 1. Page numbering must start at 1 on the abstract page and continue consecutively at the center of the footer.
There must be no table of contents or table-of-contents command.
The document must use A4 paper, with margins of at least 2.5 cm on all sides. The main text must appear after the abstract and before the appendix and must not exceed 30 pages. Appendices do not count toward the main-text limit.
The PDF must not exceed 20 MiB.
The “AI工具使用声明” must use the official wording verbatim and appear before the references.
The appendix file list must match the actual supporting materials and include all complete, runnable source code or the official no-program statement.

The

CUMCM_BODY_START

CUMCM_BODY_END

markers in the source files only help locate the main-text boundaries. The final page count must be verified against the compiled PDF; the total number of PDF pages cannot be used as a substitute for the main-text page count.

2. Generate and Reconcile AI Usage Details

First append the AI-assisted compliance scanning, anonymity checks, detail aggregation, and packaging operations performed in this stage to

AI_USAGE_LOG.md

, and then generate the details PDF, ensuring that the log covers the complete workflow. If AI participates in repairs or repackaging after the details PDF has been generated, update the log and regenerate the details PDF.

Use the actual

AI_USAGE_LOG.md

and

HUMAN_REVIEW_LOG.md

to generate

support_materials/AI工具使用详情.pdf

. It must cover at least:

The name and version or model of every AI tool;
The specific purpose and stage of use;
The primary prompting method and usage process, with typical interactions optionally included;
Whether outputs were adopted or rejected, and any human modifications and human verification; language polishing is exempt.

Runnable:

bash

python3 <skill-dir>/scripts/build_ai_details.py \
  --ai-log compliance/AI_USAGE_LOG.md \
  --human-log compliance/HUMAN_REVIEW_LOG.md \
  --output support_materials/AI工具使用详情.pdf

The script uses XeLaTeX to generate the PDF. If

xelatex

is unavailable in the environment, it retains the compilable

.tex

file and stops. In that case, use an available document/PDF tool to generate the PDF with the same filename. Do not fabricate tool versions, prompts, or human verification merely to pass the checks.

Compare the logs, the paper declaration, and the details. The tool lists, purposes, and human reviews must be consistent. Use of this Agent constitutes AI use, and the paper must not claim that no AI was used.

3. Anonymity Scan

Use the private term list to scan the paper, source code, data filenames, supporting materials, archive member names, PDF text, and readable metadata:

bash

python3 <skill-dir>/scripts/check_anonymity.py \
  --terms compliance/private_identity_terms.txt \
  paper support_materials code results

Check full names and abbreviations of individuals, schools, colleges, advisors, regional divisions, student IDs, email addresses, phone numbers, usernames, absolute paths, and PDF/image/Office metadata. Neither the term list nor the scan report may be included in the submission package. Any confirmed identity match is a hard failure; do not delete logs to conceal matches.

4. Source Discipline Check

Read

SOURCE_LOG.md

. In formal competition mode, if current competition answers, ideas, code, papers, or discussions are found on communication platforms, record

POTENTIAL_COMPETITION_RULE_VIOLATION

, suspend the submission-ready determination, and refer the matter to the participating team. Do not automatically clean up, delete, or rewrite source evidence.

5. Organize Supporting Materials

support_materials/

must contain at least the following items that were actually used:

text

AI工具使用详情.pdf
code/                  # 全部可运行源码与统一入口
source_data/           # 自主查阅使用且允许提交的数据
result_tables/         # 必要的大篇幅中间结果
README.txt             # 最小复现说明

Generate

compliance/SUBMISSION_MANIFEST.md

from the appendix file list in the paper, and verify each file path, purpose, size, and checksum. Ensure that the package does not mistakenly include the original competition attachments, commitment letter, dedicated identification page, identity term list, private logs, caches, temporary files, absolute paths, or irrelevant environment files.

Generate the ZIP archive:

bash

python3 <skill-dir>/scripts/build_support_package.py \
  --support-dir support_materials \
  --output submission/support_materials.zip \
  --manifest compliance/SUBMISSION_MANIFEST.md

If the archive exceeds 20 MiB, it may only be reduced by removing irrelevant files, compressing substitutable large charts, or improving file formats. Required source code, AI details, or supporting evidence must not be deleted.

6. Automated Preflight and Manual Visual Confirmation

Run:

bash

python3 <skill-dir>/scripts/check_submission.py \
  --root . \
  --paper paper/paper.pdf \
  --archive submission/support_materials.zip \
  --identity-terms compliance/private_identity_terms.txt

Automated checks cannot reliably determine whether the abstract is visually confined to exactly one page, whether page numbers are positioned at the center of the footer, the main-text boundary page count, or every layout detail. The PDF must be rendered page by page, and the participating team must complete the final visual confirmation. Record the evidence in

CUMCM_2026_CHECKLIST.md

7. Final Conclusion

Update:

```
compliance/CUMCM_2026_CHECKLIST.md
```
```
compliance/SUBMISSION_MANIFEST.md
```
```
reports/VERIFY_REPORT.md
```

Only when all conditions in the rules reference, the automated checks, and the participating team's visual confirmation have passed may the following be written:

text

SUBMISSION_READY = true

Any failure, pending manual confirmation, unexecuted check, or disciplinary risk must result in

SUBMISSION_READY = false

, accompanied by evidence and the stage to which the issue should be returned.

7cumcm-submit

NPX Install

Tags

SKILL.md Content (Chinese)

CUMCM 2026 Submission Compliance and Packaging

Prerequisites

1. Paper Hard Gates

2. Generate and Reconcile AI Usage Details

3. Anonymity Scan

4. Source Discipline Check

5. Organize Supporting Materials

6. Automated Preflight and Manual Visual Confirmation

7. Final Conclusion