paperlint 6.3.0 → 7.0.0

package/src/tex-requirements.ts

@@ -165,15 +165,28 @@ export interface RequiredSection {
   readonly position: "last" | null;
 }
 
+/**
+ * What a preset file IS, as its `type` declares it. A venue names itself and its call for papers; a
+ * template family and the base set name no venue, so they cannot carry either — the union has no
+ * field to put them in, the way the schema refuses them.
+ */
+export type PresetIdentity =
+  | { readonly type: "venue"; readonly name: string; readonly url: string }
+  | { readonly type: "family" }
+  | { readonly type: "base" };
+
+/** A preset's kind of file: `venue`, `family` or `base`. */
+export type PresetType = PresetIdentity["type"];
+
 /**
  * One preset FILE, parsed — before its `extends` chain is resolved (`src/presets.ts` does that).
- * A preset is a venue or a template family: `{ extends?, name?, template?, format?, tex?, rules? }`.
+ * A preset is a venue, a template family, or the TeX base set (`identity`).
  */
 export interface PresetFile {
+  /** What the file is, and for a venue, its name and call for papers. */
+  readonly identity: PresetIdentity;
   /** The preset this one builds on: `paperlint:<name>` or a relative path. */
   readonly extends: string | null;
-  /** A display name for messages; the file name otherwise. */
-  readonly name: string | null;
   /** The `\\documentclass` the venue's template uses, as the file spells it; null when it names none. */
   readonly template: string | null;
   /** Other names the venue goes by in a paper's text; empty when the file names none. */
@@ -217,10 +230,19 @@ interface FormatJson {
   readonly kinds?: KindsJson;
 }
 
-/** The preset's JSON after the schema accepted it — the shape `venue-profile.schema.json` allows. */
-interface PresetJson {
+/**
+ * The preset's JSON after the schema accepted it — the shape `venue-profile.schema.json` allows,
+ * the identity included: a venue has its `name` and `url`, a family and the base set have neither.
+ */
+type PresetJson = PresetBodyJson &
+  (
+    | { readonly type: "venue"; readonly name: string; readonly url: string }
+    | { readonly type: "family" | "base" }
+  );
+
+/** Every key of a preset but its identity. */
+interface PresetBodyJson {
   readonly extends?: string;
-  readonly name?: string;
   readonly template?: string;
   readonly aliases?: readonly string[];
   readonly blind?: boolean;
@@ -282,6 +304,46 @@ const sectionsOf = (
     ? null
     : r.map((x) => ({ title: x.title, position: orNull(x.position) }));
 
+/** The identity a preset's `type` declares. Pure. */
+const identityOf = (j: PresetJson): PresetIdentity =>
+  j.type === "venue"
+    ? { type: "venue", name: j.name, url: j.url }
+    : { type: j.type };
+
+/** One ajv error, as far as the hints read it. */
+interface SchemaError {
+  readonly keyword: string;
+  readonly dataPath: string;
+  readonly params: object;
+}
+
+/**
+ * What to write instead, for the violations of a preset's identity — ajv's own words for them
+ * ("should have required property 'url'", "boolean schema is false") name the key but not why.
+ * Read off the error's keyword and parameters, never its message text. Pure.
+ */
+export function identityHint(e: SchemaError): string | null {
+  const missing = fieldOf(e.params, "missingProperty");
+  if (e.keyword === "required" && missing === "type")
+    return 'say what this preset is: "type": "venue" (one venue\'s call for papers), "family" (a publisher\'s template that venues extend) or "base" (the TeX base set)';
+  if (e.keyword === "required" && (missing === "name" || missing === "url"))
+    return 'a venue preset names its venue and links its call for papers: "name": "<the venue, as its call spells it>", "url": "https://<the call for papers>"';
+  if (e.keyword === "false schema")
+    return `a template family names no venue: drop "${e.dataPath.slice(1)}" — "name" and "url" belong to the venue presets that extend it`;
+  if (e.keyword === "maxProperties")
+    return 'the TeX base set holds "type" and "tex" only — a venue\'s or a family\'s settings go in its own preset';
+  return null;
+}
+
+/** The hints for every violation that has one, each once. Ajv's null `errors` has none. */
+export const identityHints = (
+  v: Readonly<Pick<Validate, "errors">>,
+): readonly string[] => [
+  ...new Set(
+    (v.errors ?? []).map(identityHint).filter((h): h is string => h !== null),
+  ),
+];
+
 /** A preset's JSONC text → its value, or an Error naming the syntax problem. */
 function jsoncOf(text: string, file: string): unknown {
   const parsed = typescript().parseConfigFileTextToJson(file, text);
@@ -331,12 +393,12 @@ export function parsePreset(
   const validate = validatorFor(dir);
   if (!matchesSchema(config, validate))
     throw new Error(
-      `${file} does not match ${SCHEMA_FILE}:\n  ${violations(file, validate).join("\n  ")}`,
+      `${file} does not match ${SCHEMA_FILE}:\n  ${[...identityHints(validate), ...violations(file, validate)].join("\n  ")}`,
     );
   const j = config;
   return {
+    identity: identityOf(j),
     extends: orNull(j.extends),
-    name: orNull(j.name),
     template: orNull(j.template),
     aliases: j.aliases ?? [],
     blind: orNull(j.blind),

package/src/tex-venue-rules.test.ts

@@ -20,6 +20,7 @@ import {
 } from "./tex-venue-rules.ts";
 import { resolvePreset } from "./presets.ts";
 import { buildConfig, SHIPPED_RULES } from "./cli.ts";
+import { venuePreset } from "../test/support.ts";
 
 const VENUES = presetsDir();
 const PAPER = "/work/papers/p";
@@ -136,13 +137,13 @@ describe("tex/template — the class and every option the preset names", () => {
       "[conference]{IEEEtran} — compsoc missing",
       "\\documentclass[conference]{IEEEtran}",
       ["tex/template:missingOption"],
-      /the class option `compsoc` is missing: aidc requires `\\documentclass\[conference,compsoc\]\{IEEEtran\}`/,
+      /the class option `compsoc` is missing: AIDC requires `\\documentclass\[conference,compsoc\]\{IEEEtran\}`/,
     ],
     [
       "{acmart} under an IEEE preset",
       "\\documentclass[sigconf]{acmart}",
       ["tex/template:wrongClass"],
-      /the class is `acmart`, and aidc requires/,
+      /the class is `acmart`, and AIDC requires/,
     ],
     [
       "[journal,compsoc]{IEEEtran} — conference missing",
@@ -183,7 +184,7 @@ describe("tex/template — the class line's states: missing, empty, commented ou
     expect(ids(fs)).toEqual(["tex/template:emptyClass"]);
     expect(fs[0]?.line).toBe(2);
     expect(fs[0]?.message).toBe(
-      "the \\documentclass names no class; aidc requires `\\documentclass[conference,compsoc]{IEEEtran}`",
+      "the \\documentclass names no class; AIDC requires `\\documentclass[conference,compsoc]{IEEEtran}`",
     );
   });
 
@@ -258,7 +259,7 @@ describe("tex/template — several \\documentclass lines behind a TeX switch", (
     // Line 4: the first candidate, after the comment, `\\def` and `\\if` lines.
     expect(fs[0]?.line).toBe(4);
     expect(fs[0]?.message).toBe(
-      "none of the 2 \\documentclass lines is `\\documentclass[conference,compsoc]{IEEEtran}`, which aidc requires: `\\documentclass{article}`, `\\documentclass[conference]{IEEEtran}`. The source picks one behind a TeX switch, which is not evaluated; make one of them the venue's",
+      "none of the 2 \\documentclass lines is `\\documentclass[conference,compsoc]{IEEEtran}`, which AIDC requires: `\\documentclass{article}`, `\\documentclass[conference]{IEEEtran}`. The source picks one behind a TeX switch, which is not evaluated; make one of them the venue's",
     );
   });
 
@@ -309,7 +310,12 @@ describe("tex/template — a project's own preset, and nothing to judge", () =>
         paper("\\documentclass{whatever}"),
         { extends: "./own.jsonc" },
         {
-          extra: { [own]: JSON.stringify({ tex: { packages: { x: ["x"] } } }) },
+          extra: {
+            [own]: JSON.stringify({
+              type: "family",
+              tex: { packages: { x: ["x"] } },
+            }),
+          },
         },
       ),
     ).toEqual([]);
@@ -325,6 +331,7 @@ describe("tex/template — a template the reader cannot read, a bare class name,
       {
         extra: {
           [own]: JSON.stringify({
+            type: "family",
             template: "\\documentclass[a]{}",
             tex: { packages: { x: ["x"] } },
           }),
@@ -341,6 +348,7 @@ describe("tex/template — a template the reader cannot read, a bare class name,
     const own = `${PAPER}/own.jsonc`;
     const extra = {
       [own]: JSON.stringify({
+        type: "family",
         template: "article",
         tex: { packages: { x: ["x"] } },
       }),
@@ -353,7 +361,9 @@ describe("tex/template — a template the reader cannot read, a bare class name,
       ids(lint(paper("\\documentclass{report}"), settings, { extra })),
     ).toEqual(["tex/template:wrongClass"]);
   });
+});
 
+describe("tex/template — nothing to judge", () => {
   it.each<[string, object | undefined, string]>([
     ["no paperlint.json", undefined, `${PAPER}/paper.tex`],
     [
@@ -428,7 +438,7 @@ describe("tex/required-section — what fails", () => {
     const fs = required(lint(tex, AIDC));
     expect(ids(fs)).toEqual(["tex/required-section:missing"]);
     expect(fs[0]?.message).toBe(
-      "aidc requires a section titled «LLM Usage Statement» and there is none — add `\\section*{LLM Usage Statement}` (the title exactly; a bold paragraph does not count)",
+      "AIDC requires a section titled «LLM Usage Statement» and there is none — add `\\section*{LLM Usage Statement}` (the title exactly; a bold paragraph does not count)",
     );
     // At `\end{document}`, where the section would go.
     expect(fs[0]?.line).toBe(tex.split("\n").indexOf("\\end{document}") + 1);
@@ -503,10 +513,12 @@ describe("tex/required-section — the edges", () => {
   it("a position other than last (none): anywhere will do; a child's list replaces its parent's", () => {
     const own = `${PAPER}/own.jsonc`;
     const extra = {
-      [own]: JSON.stringify({
-        extends: "paperlint:aidc",
-        required_sections: [{ title: "Ethics" }],
-      }),
+      [own]: JSON.stringify(
+        venuePreset("own", {
+          extends: "paperlint:aidc",
+          required_sections: [{ title: "Ethics" }],
+        }),
+      ),
     };
     const settings = { extends: "./own.jsonc", kind: "regular" };
     expect(
@@ -528,8 +540,8 @@ describe("tex/venue-leftover — another venue named in the text", () => {
     const tex = aidcPaper(`${INSTITUTION}\n${BODY}${STATEMENT}`);
     const fs = leftovers(lint(tex, AIDC));
     expect(fs.map((f) => f.message)).toEqual([
-      "«AISec» names aisec, and this paper extends aidc — a leftover from an earlier submission? A reviewer reads it before the abstract. Comments and citation keys are not reported; a sentence that names the other venue on purpose can keep it with a disable directive",
-      expect.stringContaining("«ACM CCS» names aisec"),
+      "«AISec» names AISec, and this paper extends AIDC — a leftover from an earlier submission? A reviewer reads it before the abstract. Comments and citation keys are not reported; a sentence that names the other venue on purpose can keep it with a disable directive",
+      expect.stringContaining("«ACM CCS» names AISec"),
     ]);
     const line = tex.split("\n").indexOf(INSTITUTION) + 1;
     expect(fs.map((f) => f.line)).toEqual([line, line]);
@@ -591,7 +603,7 @@ describe("tex/venue-leftover — a URL is not text, a definition body is", () =>
       );
       const fs = leftovers(lint(tex, AIDC));
       expect(fs.map((f) => [f.line, f.message.slice(0, 16)])).toEqual([
-        [4, "«AISec» names ai"],
+        [4, "«AISec» names AI"],
       ]);
     },
   );
@@ -622,11 +634,12 @@ describe("tex/venue-leftover — where names are found, and whose they are", ()
   it("a name a venue shares with this paper's own chain is not a leftover", () => {
     const own = `${PAPER}/own.jsonc`;
     const extra = {
-      [own]: JSON.stringify({
-        extends: "paperlint:aidc",
-        name: "AIDC 2027",
-        aliases: ["ACM CCS"],
-      }),
+      [own]: JSON.stringify(
+        venuePreset("AIDC 2027", {
+          extends: "paperlint:aidc",
+          aliases: ["ACM CCS"],
+        }),
+      ),
     };
     const tex = aidcPaper(`ACM CCS and AIDC 2027.\n${BODY}${STATEMENT}`);
     expect(
@@ -721,8 +734,8 @@ describe("otherVenues", () => {
     if (!aidc.ok) return;
     expect(otherVenues(aidc.value, deps).map((o) => o.label)).toEqual([
       "acm-sigconf",
-      "agenticdev",
-      "aisec",
+      "AgenticDev",
+      "AISec",
     ]);
   });
 });
@@ -790,7 +803,7 @@ describe("format/layout-override reports", () => {
       [13, "\\newgeometry"],
     ]);
     expect(overrides(tex)[0]?.message).toBe(
-      "`\\usepackage{geometry}` changes the page layout aidc's template sets (`\\documentclass[conference,compsoc]{IEEEtran}`) — a desk-reject reason at venues that check the format. Remove it; if the venue allows it, disable this line with a comment saying so",
+      "`\\usepackage{geometry}` changes the page layout AIDC's template sets (`\\documentclass[conference,compsoc]{IEEEtran}`) — a desk-reject reason at venues that check the format. Remove it; if the venue allows it, disable this line with a comment saying so",
     );
   });
   it("a definition's body counts: the length it sets is set wherever it is used", () => {
@@ -834,6 +847,7 @@ describe("format/layout-override stays silent", () => {
     expect(overrides(tex, { extends: null })).toEqual([]);
     const house = {
       [`${PAPER}/house.jsonc`]: JSON.stringify({
+        type: "family",
         tex: { packages: { ieeetran: ["IEEEtran.cls"] } },
       }),
     };

package/src/tex-venue-rules.ts

@@ -295,7 +295,8 @@ export const ruleDocsUrl = (
     | "register"
     | "contrast-frames"
     | "claim-emphasis"
-    | "relation-markers",
+    | "relation-markers"
+    | "heading-case",
 ): string =>
   `https://github.com/zernie/paperlint/blob/main/docs/rules/tex/${name}.md`;
 

package/src/venue-rules.test.ts

@@ -488,7 +488,7 @@ describe("format/page-limit", () => {
       "one body page over the short-paper limit",
       (f: Facts) => (f.body_pages = 6),
       ["format/page-limit:pages"],
-      /body pages: 6, over the limit 5 for agenticdev\/short/,
+      /body pages: 6, over the limit 5 for AgenticDev\/short/,
     ],
     [
       "one reference page over",
@@ -662,7 +662,7 @@ describe("the IEEE conference family and AIDC", () => {
     const fs = lint({ venue: short, facts: pages(7) });
     expect(ids(fs)).toEqual(["format/page-limit:pages"]);
     expect(fs[0]?.message).toBe(
-      "body pages (up to the references on page 8): 7, over the limit 6 for aidc/short — a desk reject; cut the text",
+      "body pages (up to the references on page 8): 7, over the limit 6 for AIDC/short — a desk reject; cut the text",
     );
   });
 
@@ -829,7 +829,7 @@ describe("format/page-limit on AIDC: the two signals of where the references sta
     });
     expect(ids(fs)).toEqual(["format/page-limit:unclear"]);
     expect(fs[0]?.message).toBe(
-      "could not tell where the body ends, so it was NOT counted against aidc's limit: the first bibliography entry is on page 14 (hyperref's destination), and no line on page 14 reads «References». Check the headings of the bibliography and the appendix, and that nothing before them reads «References» above a [1]",
+      "could not tell where the body ends, so it was NOT counted against AIDC's limit: the first bibliography entry is on page 14 (hyperref's destination), and no line on page 14 reads «References». Check the headings of the bibliography and the appendix, and that nothing before them reads «References» above a [1]",
     );
   });
 
@@ -906,9 +906,9 @@ describe("anonymity/identity — a blind venue (AIDC)", () => {
       }),
     });
     expect(fs.map((f) => f.message)).toEqual([
-      "PDF, page 1: «Ada Example» matches «Ada Example» in `identity`, and aidc reviews double-blind — remove it, or refer to your own work in the third person",
-      "PDF metadata: Author: «Ada Example» matches «Ada Example» in `identity`, and aidc reviews double-blind — remove it, or refer to your own work in the third person",
-      "link target on page 2 (https://github.com/adaexample/tool): «adaexample» matches «Ada Example» in `identity`, and aidc reviews double-blind — remove it, or refer to your own work in the third person",
+      "PDF, page 1: «Ada Example» matches «Ada Example» in `identity`, and AIDC reviews double-blind — remove it, or refer to your own work in the third person",
+      "PDF metadata: Author: «Ada Example» matches «Ada Example» in `identity`, and AIDC reviews double-blind — remove it, or refer to your own work in the third person",
+      "link target on page 2 (https://github.com/adaexample/tool): «adaexample» matches «Ada Example» in `identity`, and AIDC reviews double-blind — remove it, or refer to your own work in the third person",
     ]);
   });
 
@@ -949,6 +949,7 @@ describe("a project's own preset, and the facts' other spellings", () => {
   // tolerance, a reference range, two columns — and no page size and no font families.
   const HOUSE = {
     [`${PAPER}/house.jsonc`]: JSON.stringify({
+      type: "family",
       tex: { packages: { acmart: ["acmart.cls"] } },
       format: { columns: 2, body_pt: 9, ref_pt_min: 7, ref_pt_max: 8 },
     }),

package/templates/paper/paper.tex

@@ -2,7 +2,7 @@
 % this file exists. With `--venue`, the class below is the venue's (`tex/template` checks it);
 % without, it is yours. `paperlint build` compiles it to paper.pdf.
 \documentclass{article}
-\title{Working title for {{name}}}
+\title{Working Title for \texttt{{{name}}}}
 \begin{document}
 \maketitle
 Write the paper here.

package/skills/submit-paper/references/venues/agenticdev.md

@@ -1,171 +0,0 @@
----
-title: "AgenticDev @ ASE — venue card (data)"
----
-
-# AgenticDev @ ASE venue card
-
-> **This is a venue DATA file, not a skill.** Follow the `submit-paper` skill for the end-to-end
-> mechanics; the facts below are the venue-specific data. (Formerly the `submit-paper-agenticdev` skill;
-> demoted to a reference doc so venue data doesn't proliferate the skill namespace.) **Re-verify the
-> CFP each year** (`conf.researchr.org/home/ase-2026/agenticdev-2026`).
-
-## The facts (2026 edition)
-
-- **Venue**: Workshop on Agentic AI for Next-Generation Software Development, co-located with **ASE**
-  (Automated Software Engineering), Munich, Oct 2026.
-- **HotCRP**: `https://agenticdev2026.hotcrp.com/paper/new`.
-- **Deadline**: **July 15, 2026, AoE** (≈ 9 AM July 16 at UTC+5). Notify Aug 21, camera-ready Aug 28.
-- **Types / limits**: Full ≤10pp (mature); **Short ≤5pp** (WIP / vision / position); Demo/Tool ≤5pp.
-  Up to **2 extra pages of references** on top.
-- **Format**: ACM `\documentclass[sigconf,review,anonymous]{acmart}` → **double-blind**. Build:
-  `pdflatex; bibtex; pdflatex; pdflatex`; add `\microtypesetup{expansion=false}` (the #1 acmart crash).
-- **Archival**: accepted papers → **ASE workshop proceedings, DOI**. 🔴 **Correction 2026-08-26: the
-  earlier wording "ACM DL / IEEE Xplore" is FALSE — there is no dual publication.** ASE's publisher
-  **alternates by year**: ASEW '24 — ACM (`10.1145/3691621.*`, ISBN 979-8-4007-1249-4), ASE 2025
-  Workshops — **IEEE** (`csdl/proceedings/asew/2025`, ISBN 979-8-3315-8503-7). The main track does the
-  same: '22 ACM, '23 IEEE, '24 ACM, '25 IEEE. The `10.5555` prefix in ACM DL is a Guide catalog
-  entry, NOT an ACM publication. By the alternation pattern, **ACM is expected for 2026**, which
-  lines up with an APC even being charged — but ⚠️ **no verbatim statement from ASE 2026 about the
-  publisher was found**. If it turns out to be IEEE, the ACM-APC question is moot entirely. Confirm
-  with the chairs before paying; selected papers
-  invited to a **journal special issue**. This is real authorship-criterion evidence.
-- **⚠️ No supplementary-material upload field** on the HotCRP form (fields are just Title, Submission,
-  Abstract, Authors, ACM corresponding, Contacts, PC conflicts). → **Host the artifact externally** (OSF
-  anonymized view-only link) and `\url{}` it in the paper's Availability. See `submit-paper` §2.
-- **Remote presentation**: CFP doesn't state a policy; what counts is the indexed
-  publication, not attendance. Only ask organizers about remote _after_ acceptance (don't draw attention
-  pre-decision under double-blind).
-
-## 🔴 How to name the venue — what CAN and CANNOT be claimed
-
-The question came up on 2026-08-24 and will come up every time (a post, a site, a résumé, an
-application). Checked against primary sources, not a search-engine summary.
-
-**Facts:**
-
-- **ASE is CORE A\*** (top tier), together with ICSE and FSE it's software engineering's "big
-  three."
-- **AgenticDev is an ASE 2026 workshop**, officially listed on ASE's own _Co-Located Events_ page
-  (`conf.researchr.org/track/ase-2026/ase-2026-workshops`). It is not a third-party conference
-  that rented a room nearby, and it is not "sponsorship" — the workshop runs under ASE's umbrella.
-- **Proceedings:** accepted papers go into the **ASE 2026 Workshop Proceedings** (ACM DL, DOI).
-- **But it is NOT the ASE main track.** The main track has its own program, its own PC, and its
-  own selectivity; the workshop is reviewed separately and more leniently.
-
-| ✅ OK to write                                           | ❌ NOT OK                            |
-| -------------------------------------------------------- | ------------------------------------ |
-| "accepted at AgenticDev 2026, a workshop of ASE 2026"    | "accepted at ASE 2026"               |
-| "workshop paper, ASE 2026 workshop proceedings (ACM DL)" | "published at a CORE A\* conference" |
-| "ASE is CORE A\*; AgenticDev is one of its workshops"    | "my paper is CORE A\*"               |
-
-⚠️ **Why this isn't pedantry:** a mismatch in how the narrative is framed is a recorded reason
-reviewers reject any claimed credentials. A reviewer sees the "workshop vs. main track"
-distinction in one minute by checking the conference program, and the cost is trust in the whole
-application, not just one line. The phrasing "a workshop of ASE 2026" is not weaker — it carries
-ASE's weight on its own while staying accurate.
-
-## Attendance, registration, and proceedings — what affects what
-
-- **Traveling to present does NOT affect the credit.** What counts is _authorship of scholarly
-  articles_ — that is, **the publication**, not attendance. "Presented at a conference" isn't on
-  the list of countable achievements at all.
-- 🔴 **What DOES matter: whether payment becomes a condition of MAKING IT INTO proceedings.** Many
-  venues require at least one author to register, or the paper gets pulled from the proceedings.
-  In that case what disappears isn't the trip, it's the proof itself. That's the exact question
-  put to the chairs on 2026-08-24, and it matters more than the money.
-- Cost for 2026: **APC $350** (ACM went fully open-access as of 2026-01-01) + registration €350
-  (early rate through 08-31). The correspondence with the chairs is broken down in the author's
-  private notes (`<paper>/reviews/2026-08-24-perepiska-cheyry.md`).
-
-## PC members (for the "PC conflicts" field) — 2026
-
-Andrea Rosani (Free U Bozen/Bolzano) · Giuseppe Di Fatta (Free U Bozen/Bolzano) · Jean Marie Mottu
-(Nantes U) · Paolo Papotti (Eurecom) · Simos Gerasimou (Cyprus U of Technology). An independent author
-with no ties to any of them checks **none**. (List grows year to year — read the current PC page.)
-
-## Topic fit (foreground these in the framing)
-
-Trustworthiness / verification / validation of AI agents; benchmarking & empirical evaluation;
-integration into developer workflows; agent-based coding/testing. A cost-aware, correctness-gated
-_validation_ paper is dead-center — name those keywords in the abstract/intro.
-
-## After acceptance — the prestige upgrade
-
-AgenticDev is a workshop (lightest authorship tier, but it counts). Extend the accepted paper (≥30% new
-material) into a higher-prestige indexed venue as a **second** publication: **MSR 2027** (deadline
-~Oct 23, 2026) or **NeurIPS 2027 Evaluations & Datasets** (~May 2027). AgenticDev explicitly invites
-journal extensions. Don't dual-submit the same paper — extend it.
-
-## Provenance
-
-"Measuring the Wrong Number" submitted here 2026-07-13 (#20, ready-for-review), 4pp short paper, OSF
-anonymized artifact linked in Availability, PC-panel estimate ~85–90% accept.
-
-## Camera-ready (2026 edition)
-
-**The ACM mechanics are generic and live one level up: `../publishers/acm.md`** (eRights first,
-the preamble, the copyright block, CCS, source files). Here — only what's specific to AgenticDev:
-
-- **Camera-ready deadline**: **28 Aug 2026, 2 PM AoE** (≈ 7 AM on August 29 at UTC+5).
-- **DOI**: `10.1145/3843282.3843715` · **ACM ISBN**: `979-8-4007-2985-0/26/10`.
-- **Copyright block**: `AgenticDev '26, October 12–16, 2026, Munich, Germany`.
-- **No longer double-blind.** The submission used `[sigconf,review,anonymous]`; both options come
-  off for the final.
-- **Same page limit**: body ≤5 pp + up to 2 pp for references only. A sixth page taken up by the
-  bibliography still counts within the limit.
-- **Title changes are allowed** — the portal explicitly asks for it "exactly as it should appear
-  in the ACM DL." But decide before eRights (see the publisher card).
-
-## Attendance and the talk (2026 edition)
-
-**Every year: the deadline and the upload channel come from the parent conference's
-not-in-person page, not from this card.** Look that page up again for the new edition; the dates
-below are 2026's.
-
-**Remote is allowed, but there is no live slot.** On 2026-08-27 the chairs told accepted authors
-who cannot travel (by email) that the workshop adopts ASE 2026's
-[Not-in-Person Presentations](https://conf.researchr.org/track/ase-2026/ase-2026-not-in-person-presentations)
-policy. That page, verbatim:
-
-> ASE 2026 does not provide presentation slots for papers that are not presented in-person by one
-> of the authors.
-
-Instead the author sends:
-
-| artifact  | what the page says                                                                                                                | deadline (2026)                                                                    |
-| --------- | --------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------- |
-| video     | "made available via a dedicated page on the conference website (recommendation: 10 min duration, mp4 file format, HD resolution)" | 2026-10-08 (ASE page; the chairs first asked for 10-01, then deferred to the page) |
-| one-slide | "shown during one of the conference sessions"; no size or format stated                                                           | same as the video                                                                  |
-| poster    | optional for the workshop; ASE prints it                                                                                          | ASE page: 2026-09-21                                                               |
-
-**Where to upload.** The page says: "find the submission link on the submission page for your paper
-(see author-kit e-mail from Conference Publishing Consulting)". That is the same personal page used
-for the camera-ready. On it, the block "Optional Archive/Appendix/Video/Picture Submissions … Submit
-Material to ACM" uploads straight into the ACM system, once per file. "All submitted material will be
-published in the ACM DL if the publishing-rights agreement gives permission for this", so tick
-permission for auxiliary material when filling in eRights. Asked where to send the files, the
-chairs answered (2026-10-01) only with a link to the ASE page, so the page governs: channel and
-deadline both come from it, and email attachments are not needed.
-
-**The slot.** Per the chairs' email to all authors (2026-09-29), a short paper gets 10 minutes in
-total: approximately 6–7 for the presentation and 3–4 for questions. It is stated as approximate,
-with no minimum.
-
-**Q&A for a remote author.** No source requires live attendance or a live answer; none confirms
-email Q&A either. Put a contact address on the video's last slide and on the one-slide.
-
-**Registration is still required** and still a **publication gate**, not a travel expense:
-workshop-day registration (non-member) €350 through 08-31, €410 through 09-20, €460 on-site.
-If entry requires a visa, ask the chairs right after acceptance.
-
-The `talk` rules check the finished files against these numbers: `docs/talk.md`.
-
-## 🤖 Machine-readable format profile
-
-Read by ESLint rules over `<paper>/_build/paper.facts.json` (the facts are captured by
-`extract-pdf-facts.mjs`). **The numbers live here, not in code** — this venue has its own, the
-next one will have different ones. Source: the Conference Publishing author instructions
-(2026-08-25) and ACM's requirements.
-
-**The format profile is in [`agenticdev.yaml`](agenticdev.yaml)** next to this file. Data lives
-there, prose lives here.

package/skills/submit-paper/references/venues/aisec.md

@@ -1,105 +0,0 @@
----
-title: "AISec @ ACM CCS — venue card (data)"
----
-
-# AISec @ ACM CCS venue card
-
-> **This is a venue DATA file, not a skill.** Follow the `submit-paper` skill for the end-to-end
-> mechanics; the facts below are the venue-specific data. (Formerly the `submit-paper-aisec` skill;
-> demoted to a reference doc so venue data doesn't proliferate the skill namespace.) **Re-verify the
-> CFP each year** (`https://aisec.cc/`) — deadline, page limit, and tracks shift year to year.
-
-## The bar (read this first)
-
-AISec is **not** a first-edition welcoming workshop. It is the long-running AI-security workshop of
-**ACM CCS — a top-4 security conference** — so calibrate to a _harder_ bar than a fresh workshop:
-mature threat modeling, honest evaluation, and airtight ethics are table stakes, not bonuses. A
-security PC rejects on soundness and ethics grounds that a SE workshop would wave through.
-
-## The facts (2026 edition)
-
-- **Venue**: ACM Workshop on Artificial Intelligence and Security (**AISec**), co-located with **ACM
-  CCS** (Computer and Communications Security).
-- **Deadline**: **24 July 2026** (verify the AoE cutoff, and convert it into your own zone, on the CFP each cycle).
-- **Types / tracks**: **full research papers**; **benchmark papers** (new evaluation frameworks /
-  datasets **with artifact sharing** — a first-class track, not an afterthought); **position / SoK**
-  (systematization-of-knowledge) papers. Pick the track and pitch to _its_ bar.
-- **Format**: ACM double-column (`sigconf`), up to **~10pp**. Build:
-  `pdflatex; bibtex; pdflatex; pdflatex`; add `\microtypesetup{expansion=false}` (the #1 acmart crash).
-- **Blind model**: **double-blind** — `\documentclass[sigconf,review,anonymous]{acmart}`, author
-  `Anonymous Author(s)`. See `submit-paper` §0/§4 for de-anon hygiene.
-- **Archival**: accepted papers → **CCS workshop proceedings in the ACM Digital Library** (DOI). Real
-  indexed-authorship evidence, at a top-tier-security-adjacent venue.
-- **⚠️ No supplementary-material upload field** on the form. → **Host the artifact externally,
-  anonymized** (OSF private project + anonymized view-only link) and `\url{}` it in Availability. See
-  `submit-paper` §2 and `paper-pipeline/references/anonymization.md`.
-
-## Security-venue specifics that DECIDE acceptance (this is the whole game here)
-
-1. **Threat-model soundness.** Name the **attacker** explicitly and their **capabilities** (what they
-   observe, what they control, their goal, their budget). **Separate accidental failure from an
-   adaptive adversary** — "the model gets it wrong sometimes" and "a motivated attacker steers it" are
-   different papers; conflating them is the classic security-PC reject. Put the threat model up front,
-   not in a footnote.
-2. **Ethics / responsible disclosure — CRITICAL, a hard reject-vector.**
-   - **Anonymize studied third parties too**, not just yourself. Do **not** punch down on named
-     maintainers/projects — aggregate the stats and use anonymized IDs (e.g. `G01…G46`) for the
-     entities you studied.
-   - **Disclose findings to affected parties BEFORE any de-anonymized release.** The paper must state
-     the disclosure timeline and that a **release gate** blocks publishing de-anonymized data until
-     disclosure completes.
-   - No supplementary slot → the anonymized artifact on **OSF** must itself be leak-clean (the released
-     files, not just the PDF). A named-entity leak in the _artifact_ is invisible to a paper-only read
-     and is the single highest reject-vector — see Provenance.
-3. **Dual-use.** If you publish an **evasion / attack technique, publish its fix in the same paper** —
-   net-defensive framing. A security PC will reject a pure attack recipe with no mitigation as
-   irresponsible; the same result framed as "here is the weakness AND how to close it" is a
-   contribution.
-4. **GenAI-use disclosure.** ACM/CCS require disclosing how generative AI was used in producing the
-   work (writing, code, experiments). Add the disclosure statement; don't omit it.
-
-## Track fit (foreground these in the framing)
-
-Adversarial ML, ML for security / security for ML, LLM/agent safety and security, evaluation &
-benchmarking of AI-security defenses, poisoning/evasion/extraction, and **rigorous measurement of
-whether a claimed safety mechanism actually holds**. A benchmark/measurement paper that ships a
-reusable eval framework + an anonymized artifact is dead-center for the **benchmark track** — name
-those keywords in the abstract/intro and cite the track by name.
-
-## After acceptance — the prestige upgrade
-
-AISec@CCS is a workshop, but co-located with a top-4 venue it is the strongest workshop tier a
-dossier can hold. Extend the accepted paper (≥30% new material) into a higher-prestige indexed venue as
-a **second** publication — e.g. a full security conference or a journal. Don't dual-submit the same
-paper; extend it. Plan the **camera-ready de-anonymization + release gate** at acceptance (see
-`camera-ready`).
-
-## Provenance
-
-"Safety Theater in Agentic Coding" hardened for this venue (PC-panel estimate **~87–88%** accept). Its
-accept **hinged on closing an ethics reject-vector**: the released artifact had named **46 maintainers**
-— a paper-only review missed it; the `pc-panel-review` artifact-runner + ethics lens caught it. Fixed
-by **anonymized provenance (`G01–G46`)** plus a **release gate** blocking de-anonymized release until
-disclosure completes. Lesson baked into this card: at a security venue the two things that most move
-the decision — an ethics/disclosure contradiction and an anonymization leak — live in the **artifact**,
-so verify the shipped files, not just the PDF.
-
-## Compose with
-
-- `submit-paper` (mechanics: HotCRP form, OSF hosting, "ready for review", PDF-only, profile, dossier notes).
-- `camera-ready` (de-anonymization + the release gate after acceptance).
-- `pc-panel-review` — run it LAST as the gate, and specifically field its **ethics lens** and
-  **artifact-runner lens** (stress-test the release gate: plant a leak, confirm it's caught).
-- Canonical shared detail: `paper-pipeline/references/artifact-checklist.md` (artifact build) and
-  `paper-pipeline/references/anonymization.md` (de-anon deny-list + verify).
-
-## Camera-ready
-
-AISec is also **ACM** (a CCS workshop), so the final's mechanics are generic and live in
-**`../publishers/acm.md`**: eRights is filled in FIRST and requires the final title; the preamble
-is converted out of submission mode (`printacmref=false` / `setcopyright{none}` /
-`pagestyle{plain}` / the `review` option — all of it removed); Source files are mandatory
-alongside the PDF; CCS codes come from the 2012 CCS Browser.
-
-What's AISec's own — its own DOI/ISBN, its own venue line in the copyright block, and its own
-dates: fill those in here once they arrive (the card gets filled in from fact, not from memory).