pods-artifact-evaluationUse for the PODS analogue of artifact evaluation — there is no systems artifact track at this theory symposium, so this skill covers formal-claims verification instead: a complete at-submission proof appendix, a claim-to-proof mapping reviewers can check, the full-version-on-arXiv norm, and, only wh
pods-author-responseUse when drafting ACM PODS author responses, covering the short ~48-hour double-anonymous rebuttal that corrects misreadings of proofs and definitions, and — distinctively — the shepherded revision cover letter that maps every required item to a concrete change in the resubmitted paper and survives
pods-camera-readyUse when preparing an accepted ACM PODS paper for its PACMMOD-track camera-ready, covering de-anonymization, the final acmsmall format and PACMMOD journal metadata (DOI, ORCID, CCS concepts), integrating shepherd-required revision items without overclaiming, posting and DOI-linking the arXiv full ve
pods-experimentsUse when designing or auditing the analytical "evidence" of an ACM PODS paper — worst-case and average-case analyses, matching upper and lower bounds, dichotomy completeness, correct complexity assumptions, and the occasional empirical validation when a theory paper claims practicality — matching th
pods-related-workUse when positioning an ACM PODS submission against the database-theory literature across PODS, ICDT, LICS, and the journals (TODS, LMCS, JACM, VLDBJ), writing delta-first contrast that compares results rather than cataloging citations, keeping self-citations double-anonymous, and handling concurren
pods-reproducibilityUse when strengthening the verifiability of an ACM PODS paper — a complete claim-to-proof map, self-contained proofs in the at-submission appendix (no external appendices), correctly stated assumptions, honest scope and open cases, the full-version-on-arXiv norm, and consistency between what the pap
pods-review-processUse when reasoning about how an ACM PODS submission is evaluated, covering lightweight double-anonymous review, the multi-cycle-per-year calendar, the two reviewing rounds within a cycle, the 48-hour rebuttal, the accept/reject/revision decision with a shepherded revision, PACMMOD-track publication,
pods-submissionUse when auditing an ACM PODS research submission for EasyChair readiness, covering the chosen cycle's abstract-then-paper deadlines, the acmsmall[review,anonymous] format and 15-page budget, the at-submission proof appendix, lightweight double-anonymity, the declared conflicts of interest, PACMMOD-
pods-supplementaryUse when deciding what belongs in an ACM PODS paper body versus its at-submission appendix, covering the acmsmall 15-page budget, the rule that PODS forbids online/external appendices so all proofs ship with the submission, the body/appendix split for a theory paper, and double-anonymous supplementa
pods-topic-selectionUse when deciding whether a data-management project belongs at ACM PODS (the database-theory symposium) or should be routed to SIGMOD/VLDB/ICDE (systems), ICDT (its sister theory venue), LICS/ICALP/STOC (pure theory), or a journal (TODS/LMCS/JACM), by contribution shape, the result-swap test, and th
pods-workflowUse when planning an ACM PODS project timeline across its multiple submission cycles per year, from venue fit through the EasyChair abstract-then-paper deadlines, the 48-hour rebuttal, the accept/reject/revision decision and shepherded revision round, PACMMOD-track publication, the arXiv full versio
pods-writing-styleUse when revising an ACM PODS paper for a precise model and result on the first page, exact theorem statements with matching bounds, complete and self-contained proofs (body plus at-submission appendix), honest assumptions and open cases, double-anonymous wording, and disciplined use of the acmsmall