Use when building the evidence for an ACM PODC paper — where "evidence" is a proof, not a benchmark.
Use when writing the related-work and positioning of an ACM PODC paper — covering the distributed-computing literature lanes…
Use when making an ACM PODC paper's result independently checkable — reproducibility for a proofs venue, not an artifact venue.
Use when reasoning about how an ACM PODC submission is evaluated — covering lightweight double-blind review, a program committee that…
Use when deciding whether a distributed-computing result belongs at ACM PODC or should be routed to DISC, SPAA, OPODIS/SIROCCO/SSS…
Use when drafting or revising the body of an ACM PODC paper — building the distributed-theory skeleton (an explicit model box, the result…
Transforms podcast or video transcripts into structured show notes with timestamps, key takeaways, resource links, guest bios, pull…
Use for the PODS analogue of artifact evaluation — there is no systems artifact track at this theory symposium, so this skill covers…
Use when drafting ACM PODS author responses, covering the short ~48-hour double-anonymous rebuttal that corrects misreadings of proofs and…
Use when positioning an ACM PODS submission against the database-theory literature across PODS, ICDT, LICS, and the journals (TODS, LMCS…
Use when strengthening the verifiability of an ACM PODS paper — a complete claim-to-proof map, self-contained proofs in the at-submission…
Use when reasoning about how an ACM PODS submission is evaluated, covering lightweight double-anonymous review, the multi-cycle-per-year…
Use when deciding what belongs in an ACM PODS paper body versus its at-submission appendix, covering the acmsmall 15-page budget, the rule…
Use when deciding whether a data-management project belongs at ACM PODS (the database-theory symposium) or should be routed to…
Use when revising an ACM PODS paper for a precise model and result on the first page, exact theorem statements with matching bounds…
Use when articulating the real-world, policy, and practice implications of a Global Environmental Change (GEC) manuscript.
Use when packaging a POPL artifact — above all a mechanized proof development in Rocq/Coq, Lean, Agda, or Isabelle — for the…
Use when positioning a POPL paper in the semantics, type-systems, and verification literature — stating per-line technical deltas against…
Use when deciding whether a project is POPL-shaped — a principle about programming languages carried by definitions and theorems — or…
Use when drafting or revising POPL prose — building the informal-to-formal ramp from a motivating program to definitions to a sharply…
Use when revising a Perspectives on Psychological Science (PoPS) piece for the PoPS voice — broad, provocative, accessible to…