Nearly every site in the Warrior Network publishes chords: the hub and its instrument satellites draw them on a neck or a keyboard, the theory site explains how harmony works, and the style sites play the progressions their music is made of. None of them measures the distance between two chords voice by voice — which tones are shared, which voices step and in which direction, and how many semitones the whole lead costs. Chord Warrior exists to take that measurement, and nothing else.
The calculator
Enter two chord symbols and the calculator reads each as a set of pitch classes. It then tries every one-to-one pairing of the first chord’s voices with the second’s, adds up the semitones each voice travels the shorter way round the octave, and ranks the pairings from the cheapest up. Each result names the common tones, the signed step of every other voice, and the total. The same engine answers a second question with no key in it: which chords sit one small step away from this one.
What it does not do
It never explains why smooth voice leading works; that is the theory site’s page. It draws no fretboard and no keyboard, and it never publishes a page per chord root or per pair of chords: the pitch-class answer is the same on every instrument and in every key, so a page per key would only repeat itself twelve times. It reads a chord symbol it does not recognise as unread, never as a guess.
How it is checked
Every number the calculator states will be derived, never typed. Continuous integration recomputes each cheapest pairing by brute force over every permutation of voices, for every pair of chord types with the same number of notes and in all twelve transpositions, independently of the code that renders the pages, and fails the build if a single count disagrees.