Original fictional labels. Not a person's password and not a computed digest. No password-hashing function was run. Do not reuse the candidate labels.

Words on this card
Password: the candidate that is offered.
Salt: a unique label stored beside the result. Here it is a name, not a generated random value.
Password-hashing method: a deliberately costly operation applied to the candidate and salt. Argon2id is one suitable method when configured appropriately. The password hash is its stored result. Fast SHA-256 alone is unsuitable for password storage.
Stored verifier: the label this card keeps for the result. NIST uses verifier for the service that checks a sign-in. That is a different use of the word.
Dump: a copy of stored salts and results. This card is not a copy of real values.
Guessing: trying candidates away from the sign-in page. This lesson does not practice it.

Worked comparison
Account: mina
Candidate offered: lamp-42
Salt label: salt-mina
Stored result label: verifier-mina
Label assigned to the combination of lamp-42 and salt-mina: verifier-mina
The labels match, so this card accepts the candidate.
Stored columns: salt-mina and verifier-mina. lamp-42 is not a stored column.

Other candidate: lamp-7 with salt-mina
Label assigned to that combination: verifier-other
The labels do not match, so this card rejects lamp-7.

Activity comparison
Account: noor
Candidate offered: cedar-9
Salt label: salt-noor
Stored result label: verifier-noor
Label assigned to cedar-9 and salt-noor: verifier-other
The labels do not match.
Check: the stored column remains verifier-noor. cedar-9 is not stored.

Same candidate, different salt
If account ada also offered lamp-42, and ada's salt label was salt-ada, the assigned result label would differ from verifier-mina.
The salt does not make lamp-42 hard to guess. It stops one result label from standing for every account that offered the same candidate.