Choose the type closest to your main contribution, then adapt the plan. The seven possible editorial routes distinguish architecture, training/objectives, theory, empirical analysis, resources, efficiency and applications. These are not official NeurIPS tracks, and a paper can span several routes.
For a new design, start with a readable architecture or representation overview, a comparison table with matched conditions, and controls testing the changed component. Add pseudocode when state, iteration, sampling or gradient routing is otherwise ambiguous; add a theorem only when making a formal claim. Neither is required merely to resemble an oral paper.
Observed medians below describe the inspected source versions. Suggested artifact quantities are editorial starting packages, not measured prescriptions or submission requirements. Small categories are examples, not robust estimates of a conference-wide standard.
Architecture & representation
The central deliverable changes the model's representation, component arrangement, information flow or reusable inference pipeline. Data, objectives and efficiency can still be substantial supporting contributions.
Corpus context · 11 papers: median 5 main figures and 4 main tables; body span ≈ 9.53 pages; attached appendix span ≈ 6.13 pages (10 resolved boundaries). Separate source files: median Not resolved whole-file pages among 0 papers; these can repeat main text and are not appendix-only lengths. Extraction-assisted observations—not drafting targets.
Pattern to learn
The selected examples illustrate complementary writing choices: For adaptive modules, put a mechanism-specific falsification control next to a time-aligned diagnostic rather than relying only on an overall success gain. Bridge a mathematical prior to an implementable recurrence, then test the targeted capability alongside capabilities that might regress. These examples do not establish one outline followed by every category member.
Argument and section order
Task, available inputs and the failure of the current representation
One running example and input/output contract
Overview diagram, followed by each genuinely changed component
Training versus inference procedure and inherited components
Main comparisons and controlled component/representation tests
Efficiency, transfer, non-winning cases and scope limits
What to prepare for this type
Editorial starting package: choose artifacts that test your actual claims. Quantities below are planning suggestions, not counts inferred from all category members or conference rules.
Representation or architecture overview
Start with one overview; add insets only when they resolve different questions
Label inputs, outputs, inherited versus new components, frozen/trainable blocks and training-only paths.
When: Core when the novelty is computational organization; use a simple representation cartoon before the full diagram if the data object is unfamiliar.
Worked input/output or failure example
One compact example or aligned qualitative grid
Make the claimed representational problem visible and reuse the same example through the mechanism.
When: Especially useful for 3D geometry, multimodal tokens, articulated objects or structured outputs; do not add a gallery that does not test the claim.
Main comparison table
One focused table per incompatible task or information regime
Keep metric direction, data, backbone, reference inputs and refinement policy next to the results.
When: Separate single-model inference from per-instance optimization and privileged-input baselines.
Component/representation ablation
A compact switch table or matched diagnostic panels
Test the named reason for each component rather than removing modules without preserving compute or capacity.
When: Use matched controls when the mechanism claim depends on architecture rather than more parameters or more supervision.
Algorithm or mathematical statement
Only when the procedure or guarantee requires it
Expose iteration, state, branching or assumptions not recoverable from the diagram.
When: A feed-forward module does not require pseudocode or a theorem simply to look like an accepted paper.
Appendix plan
Layer and tensor specifications, training/data recipes, additional task-level results, ablation settings, input/refinement contracts, runtime definitions and failure cases. Keep the defining representation and actual changed computation intelligible in the main text.
For adaptive modules, put a mechanism-specific falsification control next to a time-aligned diagnostic rather than relying only on an overall success gain.
Bridge a mathematical prior to an implementable recurrence, then test the targeted capability alongside capabilities that might regress.
Boundary: This route contains 11 primary editorial assignments in the 68-paper inspected subset (106 inventory records). It is not an official track, a universal writing standard or evidence that these choices caused acceptance.
An EEG representation/alignment architecture with staged training and subject-aware evaluation, using a mechanism diagram and controlled component analysis.
The central deliverable is a promptable multi-animal reconstruction pipeline with instance queries, geometric tokens and set matching; the dataset supports that architectural claim.
Make an architectural invariant visible: identify what stays fixed, what scales, and which inference-time operations implement the intended property.
Training, objectives & optimization
The argument primarily changes a loss, supervision signal, optimization/update rule, distillation recipe or adaptation procedure. Some assigned methods update at inference time; the label refers to the objective-driven argument, not only offline training.
Corpus context · 10 papers: median 5 main figures and 4.5 main tables; body span ≈ 9.83 pages; attached appendix span ≈ 13.29 pages (10 resolved boundaries). Separate source files: median Not resolved whole-file pages among 0 papers; these can repeat main text and are not appendix-only lengths. Extraction-assisted observations—not drafting targets.
Pattern to learn
The selected examples illustrate complementary writing choices: For a conditional mechanism claim, include a compact assumptions-to-regimes table and evaluate predicted failure regimes as well as favorable ones. For a multi-loss alignment method, draw where each objective acts, ablate terms separately and distinguish local operation timing from end-to-end cost. These examples do not establish one outline followed by every category member.
Argument and section order
Observed failure or mismatch between objective and desired behavior
Notation, conventional objective and information access
Proposed loss/update with a reason for each term or branch
Executable procedure, sampling, schedules and approximations
Matched main comparisons plus mechanism-specific diagnostics
Sensitivity, overhead, supervision dependence and remaining failures
What to prepare for this type
Editorial starting package: choose artifacts that test your actual claims. Quantities below are planning suggestions, not counts inferred from all category members or conference rules.
Mechanism or gradient-flow diagram
One diagram when multiple paths or update stages matter
Mark teachers, students, pseudo-labels, frozen weights, detached gradients and inference-only operations.
When: Use gradient arrows or phase panels when an ordinary module diagram would hide the actual intervention.
Objective and update specification
An explicit objective; an algorithm box if iterative or stateful
Define variables, positive/negative samples, weights, updates and stopping rather than listing an unexplained weighted sum.
When: A short closed-form loss may need no pseudocode; a multistage update usually does.
Matched comparison table
One task-specific table or paired baseline/new-rule rows
Hold backbone, supervision and budget fixed where possible so a training-rule claim is not merely a larger-model claim.
When: Show unmatched leaderboard context separately from causal design comparisons.
Mechanism diagnostic
One appropriate panel per central explanatory claim
Measure the suspected mismatch: gradient behavior, confusing classes, reliability, alignment or temporal persistence.
When: Use the quantity the paper actually claims to improve, not an arbitrary feature visualization.
Ablation and sensitivity package
A compact control table and consequential parameter curves
Distinguish new supervision, loss terms, schedules and extra compute; retain collapse or negative runs.
When: Do not invent large sweeps for inconsequential parameters or hide tuning costs.
Formal guarantee
Optional
State assumptions and whether the implemented approximation satisfies them.
When: A proof is needed for a formal claim, not as decoration for an empirical improvement.
Appendix plan
Exact objectives and update order, full derivations where used, sampling and teacher/data provenance, schedules, tuning budget, seed-level results, alternative objectives, cost and sensitivity. Keep the motivation for each main loss term in the main paper.
For a multi-loss alignment method, draw where each objective acts, ablate terms separately and distinguish local operation timing from end-to-end cost.
Boundary: This route contains 10 primary editorial assignments in the 68-paper inspected subset (106 inventory records). It is not an official track, a universal writing standard or evidence that these choices caused acceptance.
The central algorithm changes graph construction before learning; the method-oriented training/representation category is the closest available editorial type, with substantial theory and empirical analysis.
For a multi-stage training recipe, show stage order once and use stage-to-stage evidence to expose both transfer and forgetting across domains.
Theory & formal analysis
A formal characterization, algebraic result, guarantee or theoretically derived explanation organizes the main argument, with algorithms and experiments testing consequences or practical approximations.
Corpus context · 19 papers: median 3 main figures and 0 main tables; body span ≈ 10.55 pages; attached appendix span ≈ 17.91 pages (17 resolved boundaries). Separate source files: median Not resolved whole-file pages among 0 papers; these can repeat main text and are not appendix-only lengths. Extraction-assisted observations—not drafting targets.
Pattern to learn
The selected examples illustrate complementary writing choices: For a theory paper, draw the construction that makes the theorem necessary and separate positive properties, counterexamples and empirical illustrations. A theorem-centered paper can use one carefully chosen construction figure; prioritize precise assumptions, scales and proof navigation over a conventional experimental section. These examples do not establish one outline followed by every category member.
Argument and section order
Precise question and closest existing limitation or guarantee
Definitions, assumptions and a worked geometric or algebraic example
Main result with its conditions and an interpretation
Proof roadmap or constructive step
Practical solver/update and departures from the idealized setting
Controlled consequences, boundary cases and complete proofs
What to prepare for this type
Editorial starting package: choose artifacts that test your actual claims. Quantities below are planning suggestions, not counts inferred from all category members or conference rules.
Worked example or construction diagram
One when it makes unfamiliar definitions operational
Connect algebraic symbols to camera geometry, representations or update behavior.
When: Prefer a reusable symbolic example over an unrelated network schematic.
Assumption/result roadmap
One short map or comparison table when several regimes are involved
Keep quantifiers, non-degeneracy conditions, approximation regimes and guarantee types visible.
When: Especially important when exact theory motivates an approximate practical solver.
Theorem and proof sketch
As many as the actual logical claims need
State what is proved and identify the central argument before full technical details.
When: No target theorem count; empirical observations must not be promoted to universal guarantees.
Theory-linked diagnostic
Only when there is an empirical consequence to test
Test the predicted difficult regime, scaling, geometry or optimizer behavior under stated assumptions.
When: A finite experiment illustrates or challenges a consequence; it does not prove an asymptotic statement.
Boundary or counterexample
Include where needed to prevent a tempting overgeneralization
Explain the role of assumptions and distinguish sufficient from necessary conditions.
When: A theoretical paper need not manufacture a broad benchmark leaderboard if it is irrelevant to the result.
Appendix plan
Section-matched proofs, notation, technical lemmas, numerical construction details, exact solver settings and differences between the theorem model and the experiment. Main text must retain essential assumptions and the meaning of the main result.
For a theory paper, draw the construction that makes the theorem necessary and separate positive properties, counterexamples and empirical illustrations.
A theorem-centered paper can use one carefully chosen construction figure; prioritize precise assumptions, scales and proof navigation over a conventional experimental section.
Boundary: This route contains 19 primary editorial assignments in the 68-paper inspected subset (106 inventory records). It is not an official track, a universal writing standard or evidence that these choices caused acceptance.
The main contribution is a characterization and separation of proper positive-only learnability, with randomness and stability results rather than a benchmarked architecture.
The contribution is a uniform-in-time weak propagation-of-chaos guarantee relating finite networks to mean-field dynamics under explicit decay/regularity assumptions.
The central contribution characterizes guarantees and counterexamples for additive and multiplicative approximate MDL through explicit theorem conditions.
The main contribution reduces no-regret learning to stability of a mixture in performative prediction and derives guarantees under changed assumptions.
The main argument compares synchronous and asynchronous optimization through assumption-specific wall-clock complexity bounds, with experiments illustrating the regimes.
A reduced dynamical description of learning in low-rank RNNs organizes the paper; controlled tasks test the exact linear and qualified nonlinear analyses.
The paper defines a calibration measure and proves joint decision-theoretic and finite-sample guarantees; synthetic experiments illustrate rather than establish those formal properties.
A principled multiscale geometry and its information interpretation are the central contribution, tested on neural recordings.
Empirical analysis, diagnosis & auditing
The main new knowledge is a controlled measurement, diagnostic, comparison, failure analysis or audit. A proposed remedy, model or tool can follow from that evidence.
Corpus context · 7 papers: median 5 main figures and 1 main tables; body span ≈ 9.39 pages; attached appendix span ≈ 9.93 pages (5 resolved boundaries). Separate source files: median Not resolved whole-file pages among 0 papers; these can repeat main text and are not appendix-only lengths. Extraction-assisted observations—not drafting targets.
Pattern to learn
The selected examples illustrate complementary writing choices: Align the uncertainty calculation with the hierarchy that generated the data, and show how a reporting choice changes a concrete model-selection decision. When proposing evaluation metrics, show why a familiar metric misses the phenomenon, validate the new dimensions, and report where metric-guided changes help. These examples do not establish one outline followed by every category member.
Argument and section order
Question, surprising observation and scope
Operational definitions and the unit of analysis
Controlled protocol: what varies and what stays fixed
Finding-led sections with evidence, interpretation and competing explanations
Remedy or practical consequence if supported
Transfer, counterexamples, measurement limitations and reproducibility
What to prepare for this type
Editorial starting package: choose artifacts that test your actual claims. Quantities below are planning suggestions, not counts inferred from all category members or conference rules.
Study/control diagram or protocol table
One compact view
Expose information access, sampling, intervention and matched controls.
When: Essential when teacher labels, dataset splits, task direction or model access determine the interpretation.
Primary phenomenon plot or table
One clear entry point
Display the relationship, denominator and variability before a proposed explanation.
When: Show representative ranges rather than selected successes alone.
Alternative-explanation controls
One destination per central explanatory claim
Distinguish the proposed mechanism from compute, label quality, dataset composition or evaluation artifacts.
When: Correlation and a fitted trend require different language from a controlled causal intervention.
Case or failure gallery
A small aligned set with selection criteria
Make measured failures inspectable and include ambiguous/negative cases where relevant.
When: Qualitative cases illustrate a study; they do not replace prevalence estimates.
Transfer and resource summary
As needed by generalization or practicality claims
Repeat the protocol on different tasks/models/settings and report the actual cost.
When: Keep missing, unavailable or diverged results distinct from zero.
Appendix plan
Full control matrices, data and prompt construction, thresholds, seed-level measurements, tuning and compute accounting, alternative metrics, all model/dataset results and known false-positive or selection effects.
Align the uncertainty calculation with the hierarchy that generated the data, and show how a reporting choice changes a concrete model-selection decision.
When proposing evaluation metrics, show why a familiar metric misses the phenomenon, validate the new dimensions, and report where metric-guided changes help.
Boundary: This route contains 7 primary editorial assignments in the 68-paper inspected subset (106 inventory records). It is not an official track, a universal writing standard or evidence that these choices caused acceptance.
Placed in the empirical-analysis writing family because a new explanation procedure is argued through explicitly separated faithfulness/localization questions and multi-architecture evaluation; this is an editorial writing classification, not an official paper track.
The paper develops a representation-similarity diagnostic and analyzes what different geometries reveal across learning regimes and dynamical/generative models, with supporting metric properties.
The principal argument diagnoses a quantization failure mode and tests its explanation with matched token interventions; the penalty is a consequence of that analysis.
Datasets, benchmarks & measurement
A new corpus, acquisition/annotation process, evaluation suite or measurement protocol is the primary reusable deliverable. A companion model demonstrates utility without replacing the need to validate the resource.
Corpus context · 10 papers: median 6.5 main figures and 1 main tables; body span ≈ 9.64 pages; attached appendix span ≈ 17.45 pages (9 resolved boundaries). Separate source files: median Not resolved whole-file pages among 0 papers; these can repeat main text and are not appendix-only lengths. Extraction-assisted observations—not drafting targets.
Pattern to learn
The selected examples illustrate complementary writing choices: A dataset story should carry its taxonomy through collection, metrics and failure analysis, with explicit trial counts and inapplicable baseline cells. A synthetic-data paper needs a generation diagram, composition/attrition table, independent quality audit and downstream evidence, with different validation claims kept distinct. These examples do not establish one outline followed by every category member.
Argument and section order
What existing resources cannot measure or cover
Unit of data/annotation and intended use
Collection or generation, verification, provenance and split design
Composition, challenge taxonomy and protocol definitions
Baselines with matched inputs and resource-specific metrics
Biases, limitations, access and maintenance/reproducibility
What to prepare for this type
Editorial starting package: choose artifacts that test your actual claims. Quantities below are planning suggestions, not counts inferred from all category members or conference rules.
Coverage/comparison table
One compact resource table
Compare capabilities, annotation units, acquisition conditions and evaluation tasks, not only total size.
When: Use explicit partial or unavailable coverage rather than forcing binary superiority.
Collection and annotation pipeline
One process diagram with examples
Show raw inputs, transformations, human/machine verification and final annotations.
When: Distinguish generated labels, human corrections and measured ground truth.
Composition and split visualization
A distribution, hierarchy or protocol matrix suited to the labels
Show subjects/scenes/classes, long tails, acquisition diversity and what is held out.
A dataset story should carry its taxonomy through collection, metrics and failure analysis, with explicit trial counts and inapplicable baseline cells.
A synthetic-data paper needs a generation diagram, composition/attrition table, independent quality audit and downstream evidence, with different validation claims kept distinct.
Boundary: This route contains 10 primary editorial assignments in the 68-paper inspected subset (106 inventory records). It is not an official track, a universal writing standard or evidence that these choices caused acceptance.
A benchmark/data contribution whose central writing tasks are corpus coverage, probabilistic task definition, split design, licensing/provenance and heterogeneous evaluation.
The central contribution is a reliance measurement framework with construct validation and a controlled user study rather than a new predictive architecture.
The controlled pretraining corpus and matched language-model sandbox are the central reusable artifacts; the capability experiments demonstrate their value for studying knowledge exposure.
Efficiency, inference & systems
The central contribution changes execution, inference, memory, acquisition cost or resource scaling while preserving a stated quality or correctness contract.
Corpus context · 5 papers: median 4 main figures and 6 main tables; body span ≈ 9.2 pages; attached appendix span ≈ 23.91 pages (5 resolved boundaries). Separate source files: median Not resolved whole-file pages among 0 papers; these can repeat main text and are not appendix-only lengths. Extraction-assisted observations—not drafting targets.
Pattern to learn
The selected examples illustrate complementary writing choices: For test-time reasoning systems, show accuracy versus monetary cost, disclose pricing date, and validate the grader rather than treating its score as ground truth. For a new agent runtime, distinguish formal possibility, implementation semantics and observed behavior, and publish source values and cost conventions for each headline plot. These examples do not establish one outline followed by every category member.
Argument and section order
Workload and measured bottleneck
Quality/correctness contract and existing computation
Changed representation, execution, acquisition or reuse policy
Implementation, device and timing protocol
Component accounting plus end-to-end quality/resource comparisons
Scaling, operating-point sensitivity and unfavorable regimes
What to prepare for this type
Editorial starting package: choose artifacts that test your actual claims. Quantities below are planning suggestions, not counts inferred from all category members or conference rules.
Bottleneck profile or oracle diagnostic
One focused breakdown or controlled comparison
Explain which stage is costly and why the proposed decision variable could help.
When: Use matched budgets when an oracle analysis motivates an approximate implementation.
Execution/data-flow diagram
One overview with needed stage or memory insets
Mark preprocessing, cache/reuse, training versus inference, hardware calls and synchronization.
When: The figure should expose added overhead as well as removed work.
Quality–resource table or frontier
One panel per materially different workload
Pair quality with latency, throughput, memory or acquisition effort at comparable operating points.
When: State hardware, precision, batch/sequence/image size and what the timer includes.
End-to-end and component cost accounting
A table or stacked breakdown
Show whether an isolated saving survives the entire pipeline.
When: Do not substitute FLOPs, token count or number of steps for wall-clock measurements without qualification.
Scaling and sensitivity
Curves only for the dimensions the system claims to scale
Measure view/frame count, problem size, cache refresh or device constraints and retain adverse regimes.
When: Changing hardware or input capacity is a different comparison from identical-workload acceleration.
Algorithm or correctness explanation
As needed for the execution contract
Make reuse, selection, fallback, stopping and approximation explicit.
When: A claimed exact or distribution-preserving procedure needs a precise argument beyond similar output scores.
Appendix plan
Hardware/software configuration, workload sizes, baseline settings, preprocessing and warm-up treatment, timing repeats, memory definitions, tuning budget, approximation sensitivity and failure regimes. Include overhead introduced by the method.
For test-time reasoning systems, show accuracy versus monetary cost, disclose pricing date, and validate the grader rather than treating its score as ground truth.
For a new agent runtime, distinguish formal possibility, implementation semantics and observed behavior, and publish source values and cost conventions for each headline plot.
Boundary: This route contains 5 primary editorial assignments in the 68-paper inspected subset (106 inventory records). It is not an official track, a universal writing standard or evidence that these choices caused acceptance.
For an efficiency contribution, draw the legal unit of compression and report accuracy, training cost, deployment cost and compatibility as separate evidence.
The intervention replaces inference-time diffusion sampling without retraining, preserving an explicit generative-quality and text-alignment contract. The category denotes inference design, not a demonstrated universal latency improvement.
Domain-grounded methods & physical systems
The primary argument is a task-specific capability, physical measurement/reconstruction system or domain-grounded method whose validity depends on real acquisition, task assumptions and domain-appropriate evidence.
Corpus context · 6 papers: median 5 main figures and 3 main tables; body span ≈ 9.55 pages; attached appendix span ≈ 14.41 pages (6 resolved boundaries). Separate source files: median Not resolved whole-file pages among 0 papers; these can repeat main text and are not appendix-only lengths. Extraction-assisted observations—not drafting targets.
Pattern to learn
The selected examples illustrate complementary writing choices: For an interactive system, pair task outcomes with human burden and a staged failure decomposition that identifies where the proposed component can actually help. For an applied representation paper, connect the acquisition constraints to the architecture and give each downstream evaluation its own question, protocol and unit of analysis. These examples do not establish one outline followed by every category member.
Argument and section order
Domain problem and why ordinary assumptions fail
Measurement/data provenance, task inputs and ground-truth limitations
Physical or domain model and changed method
Implementation, acquisition and evaluation protocol
Domain-appropriate main results and mechanism controls
Deployment cost, failure regimes and limits of interpretation
What to prepare for this type
Editorial starting package: choose artifacts that test your actual claims. Quantities below are planning suggestions, not counts inferred from all category members or conference rules.
Acquisition or domain-contract figure
One setup or input/output view
Show sensors/modalities, calibration, measured versus generated quantities and what is available at use time.
When: Essential when hardware, multimodal cohorts or nonstandard labels determine the claim.
Mechanism/physical model diagram
One overview with necessary physical or anatomical labels
Connect variables, modules and losses to the domain problem rather than only showing generic network boxes.
Compare matched scenes/patients/objects with relevant maps, spectra, overlays or error views.
When: Label simulation, real data, pseudo-ground-truth and unavailable measurements; an appealing image is not independent validation.
Task-specific quantitative table
One table per incompatible endpoint
Report the relevant physical/clinical/behavioral metric, units, uncertainty and evaluation split.
When: Separate image quality from geometry, survival discrimination, calibration or downstream behavior.
Ablation and independent validation
Controls chosen for the proposed mechanism
Test key physical assumptions, modality use or pipeline components; include an independent reference when feasible.
When: Do not label a model-derived pseudo-label as independent truth or infer clinical benefit from a technical benchmark.
Cost and limitations panel
As appropriate to the deployment claim
State calibration, capture, annotation, compute and failure requirements.
When: A successful laboratory demonstration does not establish unrestricted field or clinical reliability.
Appendix plan
Acquisition/calibration details, specimen or cohort preparation, split and metric definitions, physical derivations, implementation settings, supplementary real/synthetic comparisons and failure cases. Keep pivotal ground-truth limitations in the main text.
For an interactive system, pair task outcomes with human burden and a staged failure decomposition that identifies where the proposed component can actually help.
For an applied representation paper, connect the acquisition constraints to the architecture and give each downstream evaluation its own question, protocol and unit of analysis.
Boundary: This route contains 6 primary editorial assignments in the 68-paper inspected subset (106 inventory records). It is not an official track, a universal writing standard or evidence that these choices caused acceptance.
For an applied representation paper, connect the acquisition constraints to the architecture and give each downstream evaluation its own question, protocol and unit of analysis.
An application/problem-formulation contribution centered on a virtual-identity provisioning pipeline, supported by geometry, generation and verification experiments.
An algorithmic application of model-specific inference-use control, organized around a precise deployment setting, conditional analysis and experimental validation.
The contribution is a mechanism-aware conditioning interface for data-limited physical extreme-event emulation, supported by a mathematical proxy and controlled domain-specific evidence.