Memory is one copy with no warning light
The condition is narrow and it is about copies rather than strength. Somewhere you can reach later, and that is not your own recall, a record of the password for this account has to exist. That is the whole of it. Not a particular product, not a particular medium. The requirement is arithmetic: the number of independent copies has to be greater than one.
A password held only in memory is a single copy of something that cannot be reissued. Elsewhere, forgetting is an inconvenience with a recovery path attached. Here there is no address to send a reset to and nobody who can identify you by any means other than the credential you just lost. The account does not go anywhere. It sits there intact and you are outside it permanently. A large share of accounts lost for good are lost this way, with no attacker involved at any point.
Memory also fails without notice, and it does not degrade in a way you can watch. Recall of a string you typed daily for weeks feels identical right up to the session where it does not come back. The only thing separating a password you still know from one you are about to lose is whether a second copy exists while you still know it.
What the record rests on
Losing the device does not lose the account supplies the principle: nothing you need in order to get back in may exist in only one place. That card is about single copies in general. This one applies the rule to the copy that is hardest to see, since a copy in your head does not look like a copy. It looks like knowing something.
The account name is used nowhere else supplies the other half of what has to be stored. A password with no name attached opens nothing, and if the handle is one you will abandon, the record refers to an account you will not use. The store is then full and useless at once.
Both upstream cards are satisfied by one act. Writing the name and the password together, somewhere that is not the machine you registered from, meets the single copy rule and keeps the pair intact.
The whole stage waits on one arrow
Only one card is directly downstream: You can log in a second time. That looks like a small blast radius until you look at what the card carries. On the Dependency map it is the gate everything later sits behind, and this condition is one of the three things it is made of. A missing password does not stop you at a login form. It stops you at everything the login form was for.
| Cannot hold | The reason it cannot |
|---|---|
| You can log in a second time | The second occasion is the one memory does not cover. The first login happens while the string is still fresh; the second happens after the gap, and the gap is what removes recall. |
| You hold the coin this order is priced in | What an order is priced in is read inside the account. An account you cannot enter cannot tell you what to hold. |
| The listing is one you have actually read | The listing text lives behind the login and is not repeated anywhere else, so the reading cannot happen from outside. |
| You can come back tomorrow and still be you | The last card assumes the session can be reconstructed. A password that existed only in a memory which has faded is the commonest reason it cannot. |
One arrow into a gate is not a small thing. Everything in the value and order stages sits on the far side of a session, so a lost password costs the account, whatever it held, and the time that went into it. The remedy is not recovery, because there is none. It is registering again as a stranger, which means going back through The account name is used nowhere else for another clean string.
Nobody on the far side has a way to establish that you are the person who registered. That absence is a design property rather than an oversight, so asking is not a step that exists.
What losing it looks like from the login form
It rarely looks like a blank. It looks like near misses. You type the string you are confident about and the form rejects it. You try it with a different capital, then with the number at the other end. Each attempt feels closer than the last, which is the trap, because the feeling of getting warmer comes from trying and not from anything coming back. A wrong password and a wrong name produce the same refusal, so you cannot tell which half is broken.
Then the worse phase, where you reconstruct from a rule: it was probably built the way I usually build them. That is a large space of candidates with no way to search it. Somewhere in there the confusion moves and you start doubting the address, the browser or the network, when the string kept under The address is kept somewhere that outlives the browser was fine throughout.
Producing it from the store, not from recall
The check is a gap and a retrieval. Leave the account alone long enough that you are no longer typing it from muscle memory. Then, without trying to recall anything first, produce the name and the password from the store. A pass is that the store hands you both, complete, on a machine you might not have registered from. A fail is any of these: the password is there and the name is not, the store lives on the machine you would lose, or you caught yourself recalling the password instead of reading it. Recall during the test invalidates the test.
| Half true in this way | What is still missing |
|---|---|
| Written down on the machine you log in from | One event removes the machine and the record together, so the count of independent copies is still one. |
| In a reachable store, in a room other people use | Meets this card and fails Nobody else can read the screen, which is a separate card and is not cancelled by this one. |
| Two copies, both derived from a remembered rule | Not two copies. One rule written twice, and the rule is the thing that fades. |
Not a recommendation of any store
This card names no manager, no medium and no method, and it does not prefer paper to software. It pulls against the room condition above, and that tension does not resolve into a rule. The thing people substitute for it is password strength: a long random password you cannot retrieve fails this condition as completely as a short one.