# kb/comparisons/ - Collection Contract

Structured head-to-head evaluations of two or more things that already have pages here. A
comparison exists so that neither subject's own page has to argue against the other.

**Quality goal:** decidability - a reader with a concrete situation should be able to choose.
That needs named, checkable dimensions and a stated trade-off; a page that lists differences
without saying what they cost has described, not compared.

Inherits [kb/CONTRACT.md](../CONTRACT.md) - naming, tone, linking, provenance and confidence
are defined there and are not restated here.

## Types offered

`comparison` (`tools/wikitool types describe comparison`).

## Naming

The title reads as a comparison: `Go vs Rust.md`, `Traefik vs nginx.md`. Order the subjects as
they are most commonly spoken, not alphabetically.

## Requirements

- **Every subject must already have its own page.** A comparison is a view over existing
  knowledge, not a place to introduce it. Create the entity or concept pages first, then
  compare them.
- Compare on stated, checkable dimensions - a table with one row per dimension, one column per
  subject. Cite hard facts the same way any other page does.
- State the trade-off, not a winner. Where a recommendation is genuinely warranted, scope it:
  "for X workload", not "better".

## Outbound linking

A comparison links to every subject with `related to`, and each subject links back. Comparison
pages are **exempt from the orphan check** - they are reached through `index.md` rather than
through inbound prose links.

## What does not belong here

- A comparison of things this wiki does not otherwise cover.
- Feature-matrix dumps copied from a vendor page. If the material is a source, ingest it as one
  and compile the comparison from it.