computing-paperlisted

# computing-paper Produces an **ACM/IEEE computing conference or journal paper**: a formal systems/engineering research write-up aimed at program-committee reviewers and practitioners, built around a described approach or system and an explicit, falsifiable **Evaluation**. Its center of gravity is the evaluation evidence — the paper earns its Conclusion from what the Evaluation actually shows, not from an asserted claim up front. This genre is **distinct from `academic`** (the APA/IMRaD empirical-paper structure: Method → Findings → Discussion, author-date citations) and from `engineering` (a practitioner decision report whose mandatory matter is an options-vs-criteria Trade-offs table, not CCS Concepts or an Evaluation section). Choose `computing-paper` for systems and engineering research targeting an ACM or IEEE program committee. ## Pattern (industry: ACM/IEEE computing conference/journal paper) 1. **Abstract** — 150-250 words: problem, approach, principal results, conclusion. 2. **Introduction** — the problem, why it matters, the contribution, and a roadmap of the rest of the paper. 3. **Related Work** — prior systems and approaches, and how this work differs from each. 4. **Approach / System Design / Method** — the design or method under study, in enough detail that a reviewer could reproduce it. 5. **Evaluation** — experimental setup (datasets, baselines, metrics, environment) and results. Every result claim cites its source; a results table or fi