Files
chemenu/kb/comparisons/COLLECTION.md
T
torben 18ae28f918
CI / verify (push) Failing after 32s
Release / release (push) Successful in 38s
Chemenu 2.1.0 - deterministischer Wissenskompiler
Chemenu kompiliert Rohnotizen zu einem verlinkten, quellengebundenen Wiki:
raw/ -> types/ + tools/ -> kb/ -> reports/. Was mechanisch ist, macht
tools/wikitool; was Urteil braucht, macht ein Agent unter Contracts, deren
Grenzen in Code durchgesetzt sind statt im Prompt.

Dieser Commit ist der Startpunkt der oeffentlichen Historie. Die vorherige
Entwicklung fand in einer privaten Instanz statt und ist nicht Teil dieses
Repositorys; ihre Erzaehlung steht vollstaendig in CHANGES.md, das mit 44
Eintraegen von 0.1.0 bis 2.1.0 erhalten geblieben ist.

Der mitgelieferte Korpus ist ein Testbett und eine Demo: 170 Seiten ueber den
Stack selbst - Gates, Lint, Versionierung, Suche, das Wiki-Muster. Er
dokumentiert das Werkzeug mit den eigenen Mitteln des Werkzeugs.

Lizenz: AGPL-3.0 fuer den Stack (tools/, types/), CC-BY-4.0 fuer die Inhalte.
Die Grenze zwischen beiden ist der Dateiplan, den dist export berechnet -
siehe NOTICE.
2026-09-01 16:26:14 +02:00

1.8 KiB

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 - 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.