podc-artifact-evaluationUse when an author expects an artifact-evaluation or badge track at ACM PODC and needs redirecting — PODC has NO artifact track and no ACM badges. This skill converts artifact-culture instincts into what PODC actually evaluates: proof-appendix completeness, model/assumption rigor, and the honest, op
podc-author-responseUse when writing an ACM PODC rebuttal/author response, if the cycle runs one — covering how to correct a proof misreading, supply a missing lemma or bound within the anonymity envelope, prioritize soundness questions over taste, and behave correctly given that PODC has no revision round to fall back
podc-camera-readyUse when preparing an accepted ACM PODC paper for the proceedings — de-anonymizing after lightweight double-blind, compressing to the 10-page two-column ACM proceedings format without losing the proof map, completing ACM rights/eRights metadata and CCS concepts, and posting the synchronized full ver
podc-experimentsUse when building the evidence for an ACM PODC paper — where "evidence" is a proof, not a benchmark. Covers matching upper and lower bounds, tightness arguments, model and assumption stress-tests, adversary-strength calibration, and the honest, clearly-optional role of any simulation in a distribute
podc-related-workUse when writing the related-work and positioning of an ACM PODC paper — covering the distributed-computing literature lanes (PODC/DISC/SPAA and the JACM / Distributed Computing journals), writing a model-and-bound-precise delta over prior results, distinguishing your model from neighboring ones, an
podc-reproducibilityUse when making an ACM PODC paper's result independently checkable — reproducibility for a proofs venue, not an artifact venue. Covers a self-contained proof appendix, an explicit and checkable model/assumption box, honest handling of any optional simulation, and keeping the full version (with proof
podc-review-processUse when reasoning about how an ACM PODC submission is evaluated — covering lightweight double-blind review, a program committee that reads proofs, the accept/reject decision with no journal-style revision round, the Brief Announcements track's lighter bar, and how PODC's process differs from DISC,
podc-submissionUse when auditing an ACM PODC submission for HotCRP readiness, covering the two-step abstract-registration then full-paper deadline, the ACM Master template with the 10-page-merits budget and unbounded full version, lightweight double-blind anonymization, the regular-paper-vs-Brief-Announcement choi
podc-supplementaryUse when deciding what goes in the first 10 read-guaranteed pages of an ACM PODC submission versus the full version / appendix, and when choosing between a regular paper and a Brief Announcement — so that nothing which decides acceptance lives past page 10 and every deferred proof remains reachable.
podc-topic-selectionUse when deciding whether a distributed-computing result belongs at ACM PODC or should be routed to DISC, SPAA, OPODIS/SIROCCO/SSS, STOC/FOCS/SODA, a systems venue (ICDCS/DSN/OSDI/NSDI), a blockchain-theory venue (AFT/FC), or a journal (JACM / Distributed Computing) — and how to avoid the PODC-vs-PO
podc-workflowUse when planning an ACM PODC campaign end to end — running the single annual cycle backward from the February deadline through abstract registration, lightweight double-blind review, the late-April notification, the May camera-ready, and the arXiv full version — and coordinating the regular-paper-v
podc-writing-styleUse when drafting or revising the body of an ACM PODC paper — building the distributed-theory skeleton (an explicit model box, the result stated as a theorem up front, a proof architecture the reader can navigate, and the 10-page-merits discipline) so the merits case lands within the first 10 pages