Skip to content

ICML 2026 — writing by contribution type

Plan the evidence before polishing the format

Choose the route closest to your main contribution, then adapt it. Architecture, objective, theory, analysis, resource, system, application and position arguments carry different evidence obligations. Only types present in this inspected corpus appear below. These editorial routes do not replace the conference's official track definitions.

For a new design, prepare a readable computation or representation overview, a comparison with matched conditions, and controls that test the changed component. Add pseudocode when iteration, state, sampling or gradient routing would otherwise be ambiguous. Add a theorem only when making a formal claim. A position paper instead needs a defensible thesis, substantive alternatives and implications; it is not required to pretend to be a leaderboard method.

Observed medians describe source versions. Suggested display packages are conditional editorial starting points, not official requirements or evidence of a necessary number of figures. Small groups provide 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 · 22 papers: median 6 main figures and 4 main tables; body span ≈ 9.11 pages; attached appendix span ≈ 12.91 pages (21 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

Make the representation change legible before the leaderboard, then test its claimed mechanism separately from additional capacity. Name the obstacle, show the intermediate representation or symmetry operation, and include a matched-capacity or matched-operator control. Exact discrete symmetry, empirical robustness, effective rank and downstream accuracy support different claims. These are lessons from the named examples, not frequency estimates for every member.

Argument and section order

  1. Task, available inputs and the failure of the current representation
  2. One running example and input/output contract
  3. Overview diagram, followed by each genuinely changed component
  4. Training versus inference procedure and inherited components
  5. Main comparisons and controlled component/representation tests
  6. 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.

Examples behind the synthesis

Boundary: This route contains 22 primary editorial assignments in the 168-paper inspected subset (168 inventory records). It is not an official track, a universal writing standard or evidence that these choices caused acceptance.

See inline examples of these artifact styles · Compare every member in the measurement ledger

All 22 category members and classification rationale

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 · 35 papers: median 6 main figures and 3 main tables; body span ≈ 8.83 pages; attached appendix span ≈ 11.91 pages (35 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

Keep the ideal objective, implemented estimator and behavioral failure mode visibly separate. Trace the diagnosed problem into the objective and estimator, disclose approximation or skipping rules, and test the intervention under a matched evaluation contract. An objective-derived limit need not describe finite-compute implementation; eliciting a prior is not injecting missing knowledge. These are lessons from the named examples, not frequency estimates for every member.

Argument and section order

  1. Observed failure or mismatch between objective and desired behavior
  2. Notation, conventional objective and information access
  3. Proposed loss/update with a reason for each term or branch
  4. Executable procedure, sampling, schedules and approximations
  5. Matched main comparisons plus mechanism-specific diagnostics
  6. 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.

Examples behind the synthesis

Boundary: This route contains 35 primary editorial assignments in the 168-paper inspected subset (168 inventory records). It is not an official track, a universal writing standard or evidence that these choices caused acceptance.

See inline examples of these artifact styles · Compare every member in the measurement ledger

All 35 category members and classification rationale

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 · 38 papers: median 3.5 main figures and 0.5 main tables; body span ≈ 9.05 pages; attached appendix span ≈ 18.88 pages (37 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

State the comparison contract before presenting an upper/lower-bound contrast. Define input domain, computational model, access, rounding or delay assumptions alongside each theorem; use the appendix as an explicit proof map. Statistical optimality need not imply efficient computation, and a finite-precision expressivity theorem is not a training guarantee. These are lessons from the named examples, not frequency estimates for every member.

Argument and section order

  1. Precise question and closest existing limitation or guarantee
  2. Definitions, assumptions and a worked geometric or algebraic example
  3. Main result with its conditions and an interpretation
  4. Proof roadmap or constructive step
  5. Practical solver/update and departures from the idealized setting
  6. 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.

Examples behind the synthesis

Boundary: This route contains 38 primary editorial assignments in the 168-paper inspected subset (168 inventory records). It is not an official track, a universal writing standard or evidence that these choices caused acceptance.

See inline examples of these artifact styles · Compare every member in the measurement ledger

All 38 category members and classification rationale

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 · 23 papers: median 6 main figures and 2 main tables; body span ≈ 9.04 pages; attached appendix span ≈ 14.91 pages (23 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

Organize evidence around competing explanations and retain informative nulls or collapse regimes. Factor the intervention, distinguish uncertainty from checkpoint training versus evaluation resampling, and report the scope of unsuccessful or negative controls. Selected models, seeds and evaluation perturbations do not establish universal mechanism or causal law. These are lessons from the named examples, not frequency estimates for every member.

Argument and section order

  1. Question, surprising observation and scope
  2. Operational definitions and the unit of analysis
  3. Controlled protocol: what varies and what stays fixed
  4. Finding-led sections with evidence, interpretation and competing explanations
  5. Remedy or practical consequence if supported
  6. 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.

Examples behind the synthesis

Boundary: This route contains 23 primary editorial assignments in the 168-paper inspected subset (168 inventory records). It is not an official track, a universal writing standard or evidence that these choices caused acceptance.

See inline examples of these artifact styles · Compare every member in the measurement ledger

All 23 category members and classification rationale

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 · 17 papers: median 6 main figures and 3 main tables; body span ≈ 9.14 pages; attached appendix span ≈ 23.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

Expose the construct, label-production process and evaluation access before treating a score as capability. Turn the motivating taxonomy into testable axes, document oracle or simulator assistance, and connect failures back to those axes. Oracle-assisted human judgments, robot execution, process monitoring and outcome prediction are different evaluation contracts. These are lessons from the named examples, not frequency estimates for every member.

Argument and section order

  1. What existing resources cannot measure or cover
  2. Unit of data/annotation and intended use
  3. Collection or generation, verification, provenance and split design
  4. Composition, challenge taxonomy and protocol definitions
  5. Baselines with matched inputs and resource-specific metrics
  6. 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.

When: Avoid conflating frames, tracks, objects, rendered variants and independent subjects.

Baseline results by challenge

Focused tables with the same taxonomy used in the protocol

Demonstrate what the resource reveals and expose non-dominating models or hard subgroups.

When: A high average score alone does not validate label quality or benchmark relevance.

Quality/reliability study

One verification analysis when annotation or metric validity is a claim

Document agreement, quality checks, adversarial controls, contamination checks or calibration.

When: Select the check that addresses this resource's actual failure risks; do not imply a single check proves complete validity.

Appendix plan

Annotation instructions and interfaces, full templates where needed, inclusion/exclusion rules, split lists or generation settings, quality-control sampling, dataset statistics, baseline configuration, access conditions and detailed limitations.

Examples behind the synthesis

  • RoboMME: Benchmarking and Understanding Memory for Robotic Generalist Policies · Human incremental VideoQA protocol and robot execution, pp. 5-8

    Make the benchmark's construct unavoidable by design, then cross representation and integration choices while separating oracle and executable protocols.

  • Monitoring Monitorability · Positive filtering as a stopgap, Appendix D.3, p. 30

    Separate the construct, observation access and labeling mechanism before plotting scaling trends, and explain when aggregation changes the evaluated subset.

Boundary: This route contains 17 primary editorial assignments in the 168-paper inspected subset (168 inventory records). It is not an official track, a universal writing standard or evidence that these choices caused acceptance.

See inline examples of these artifact styles · Compare every member in the measurement ledger

All 17 category members and classification rationale

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 · 16 papers: median 5 main figures and 3 main tables; body span ≈ 8.98 pages; attached appendix span ≈ 15.91 pages (15 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

Define the cost boundary and quality operating point as part of the result. Separate proxies from elapsed time, list excluded work, show workload regimes, and pair acceleration with the accuracy or optimality lost at that setting. A sub-second GPU region is not full user-visible latency; a pruned solver does not inherit an exact parent formulation's guarantee. These are lessons from the named examples, not frequency estimates for every member.

Argument and section order

  1. Workload and measured bottleneck
  2. Quality/correctness contract and existing computation
  3. Changed representation, execution, acquisition or reuse policy
  4. Implementation, device and timing protocol
  5. Component accounting plus end-to-end quality/resource comparisons
  6. 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.

Examples behind the synthesis

Boundary: This route contains 16 primary editorial assignments in the 168-paper inspected subset (168 inventory records). It is not an official track, a universal writing standard or evidence that these choices caused acceptance.

See inline examples of these artifact styles · Compare every member in the measurement ledger

All 16 category members and classification rationale

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 · 8 papers: median 5.5 main figures and 3 main tables; body span ≈ 9.04 pages; attached appendix span ≈ 9.91 pages (8 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

Write the domain's actual inputs, interventions and human work into the comparison contract. Show the workflow and access assumptions, assess domain-relevant outcomes, and preserve the failure or coverage cost of optimizing a preferred proxy. Chemical plausibility scores, medical task benchmarks or reviewed constraint graphs are not experimental or clinical deployment validation. These are lessons from the named examples, not frequency estimates for every member.

Argument and section order

  1. Domain problem and why ordinary assumptions fail
  2. Measurement/data provenance, task inputs and ground-truth limitations
  3. Physical or domain model and changed method
  4. Implementation, acquisition and evaluation protocol
  5. Domain-appropriate main results and mechanism controls
  6. 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.

When: Keep measured inputs, latent physical quantities and predicted outputs visually distinct.

Aligned qualitative diagnostic

A compact grid or profile plot

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.

Examples behind the synthesis

Boundary: This route contains 8 primary editorial assignments in the 168-paper inspected subset (168 inventory records). It is not an official track, a universal writing standard or evidence that these choices caused acceptance.

See inline examples of these artifact styles · Compare every member in the measurement ledger

All 8 category members and classification rationale

Position & research agenda

The main contribution is a defensible stance or proposed change in research practice, not necessarily a new algorithm or benchmark. Official position-track obligations remain edition-specific.

Corpus context · 9 papers: median 2 main figures and 0 main tables; body span ≈ 9.04 pages; attached appendix span ≈ 5.92 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

Turn a thesis into an explicit evidence standard while stating what it does not prohibit. Define the conceptual distinction, connect supporting examples to evidence levels, and answer serious alternative views with concessions and a bounded response. These are writing lessons from Position Track papers; the edition-specific Alternative Views requirement belongs in official rules, and illustrative stress tests are not comprehensive safety assessments. These are lessons from the named examples, not frequency estimates for every member.

Argument and section order

  1. State a clear, contestable thesis and define its scope
  2. Explain the stakes and distinguish the proposed position from current practice
  3. Build the supporting argument using attributable evidence and concrete cases
  4. Present substantive alternative views and answer the strongest objections
  5. Identify who can act, what changes and how progress could be assessed
  6. Separate supported conclusions, normative judgments and open questions

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.

Argument or stakeholder map

One compact map if relationships are otherwise difficult to follow

Show how premises support recommendations and who bears the benefits, costs and obligations.

When: Useful for multi-party proposals; a simple thesis does not need a decorative flowchart.

Evidence and alternatives table

A focused comparison when precise distinctions matter

Compare assumptions, evidence, benefits, trade-offs and unresolved objections without caricaturing opposing views.

When: Use published facts or explicitly labeled reasoning; do not invent numerical support for a normative claim.

Concrete case, counterexample or diagnostic

Selected cases with stated selection limits

Make the problem and implications inspectable, and distinguish illustrative cases from representative samples.

When: A counterexample can refute a universal claim but cannot establish how common a failure is.

Action and evaluation plan

A concise plan or table if several actors and steps are involved

Connect proposed changes to feasible actions, responsible actors, costs and observable success criteria.

When: Do not present proposed outcomes as measured results. A method leaderboard is not required merely to resemble a conventional ML paper.

Appendix plan

Supporting cases, extended evidence, definitions, survey or search methods, and qualified implementation scenarios. Keep the central thesis and strongest alternatives in the main argument. Check the actual conference track's required sections; ICML 2026 Position Papers specifically require Alternative Views.

Examples behind the synthesis

Boundary: This route contains 9 primary editorial assignments in the 168-paper inspected subset (168 inventory records). It is not an official track, a universal writing standard or evidence that these choices caused acceptance.

See inline examples of these artifact styles · Compare every member in the measurement ledger

All 9 category members and classification rationale