What holding it as characters means
This condition is about the form the address is in while it sits in your possession, not about the address itself. A string is a sequence of characters that is entirely visible. You can look at the whole of it at once, and everything it will ever do is written on its face. A control is an object you activate. Its destination is held behind it rather than printed on it, and you learn that destination by arriving there. The checking and the visiting happen in the wrong order, which means no checking happens.
Several ordinary things are controls in exactly this sense. A button with an address printed on it is still a button: the printing is a label, the destination is set elsewhere, and nothing requires the two to agree. A QR code has an encoding step in front of it, so the device that decodes the characters is the device that will act on them, and the decode and the visit collapse into one motion. A shortened link is a control by design. A link whose text reads as one address and whose target is another is the same substitution with fewer parts.
What is lost is not safety in the abstract. It is four operations, and each is used by a later card on this map. You cannot compare a control against a second copy, because there is nothing to lay side by side. You cannot retype it into a place of your own choosing. You cannot read it aloud, which is the cheapest way of getting a second pair of eyes on a string. And you cannot store it as itself, only a reference to it, and the reference decays with whatever is holding it.
| What you hold | What you can do before activating it |
|---|---|
| A string of characters | Read, count, compare, copy by hand, say aloud, write elsewhere |
| A button or tile | Read the label, which is not the destination |
| A QR code | Point a device at it, which is going there |
| A shortened link | Nothing. The destination is not in the object |
| A link whose text and target differ | Read the text, the part chosen to be read |
Why nothing on the map holds this one up
This card is a root. Nothing above it supplies it, and Roots and endings lists the small number of conditions in the same position. Being a root is not a statement about importance. It is a statement about where help comes from. The map can describe this condition and say what depends on it, but it cannot produce it for you, in the same way that the machine is one you actually control is something the map can only name.
That has a practical consequence. When a downstream card fails you can walk back up the chain and find the broken thing. When a root fails there is no walking back, and no repair elsewhere makes anything below it true. How to read a card sets out that argument.
The two conditions that cannot be checked without it
Two cards hang directly on this one, and they break differently. The first is the string has the shape an onion address has. That card is a counting exercise, and both of its questions are meaningless applied to a button. You can inspect the label on a tile, satisfy yourself that it has the right shape, and have learned something about the label and nothing about the destination. That is the trap in miniature: the shape test appears to pass, and what it passed on was a piece of text with no connection to where the object goes.
The second is the address arrived by a route you can use again. That card asks whether you can return to the source and set today against tomorrow. Comparison is a character operation too. If the source hands you a control on both occasions you have two objects you cannot look inside, and two tell you nothing that one did not. The route stays repeatable and the comparison it was meant to enable never arrives.
| Cannot hold | The reason it cannot |
|---|---|
| The string has the shape an onion address has | Counting characters requires characters. A label can be counted; a destination behind a label cannot |
| The address arrived by a route you can use again | Returning to a source only helps if the two things you fetched can be set against each other |
The damage does not stop there. Keeping the address and telling a mirror from a copy are operations on a string as well. Stage C is character work throughout, and this is where the characters come from.
Skipping it: the address you never actually saw
Skipping this one is comfortable, which is why it is common. You press the thing. Either a page appears or it does not. If a page appears you cannot say what you reached, then or later. Asked which address you used, the honest answer is the name of the page the button sat on, which is a much weaker fact.
If no page appears the confusion lands in the wrong place. What you know is that an object you never read did not produce a page. What it feels like is that the address is broken, and the reader starts working on the browser, on whether a circuit builds at all, on anything except the thing that was never established. The error text is the same for a mistyped string, a string that could never resolve and a network carrying you nowhere, so it points at the network by default. There is nothing else it could say.
Reading it aloud
The check is short and goes nowhere. Read the address out of whatever you are holding, character by character. Then type it by hand into a plain text editor, without copying and without pasting, and set your version against the source.
A pass looks like a boring couple of minutes and a line of text you produced yourself. A fail is the moment you notice there is nothing to read: you are hovering over a tile to make a preview appear, or opening a picture with a pattern in it. Hovering is worth doing, but it is a partial mitigation, because the preview comes from the same object you are inspecting.
The limit of this card
This is not an argument that hyperlinks are dangerous or that pressing things is a bad habit. Ordinary browsing is made of controls and works well. The rule applies to one string, because everything downstream of it is an operation on characters. It is also not a claim that a string you can read is a string that is correct. Reading is what makes the later checks possible.