Who is allowed to install software here
The condition is about administrative control, and administrative control belongs to a shorter list of people than it looks. On an ordinary computer, the account that can install a program can also install a program that watches. Those are not two powers that happen to travel together. They are one power described twice. So the question is not whether you trust the other people who can reach this machine. It is whether there are any.
Several ordinary arrangements make the answer no. A machine issued by an employer or a school is enrolled in remote management before it is handed over, so a console somewhere can push software to it without asking whoever is sitting in front of it. A machine shared in a household has other accounts on it, and administrative rights on one side of the login screen are rights on both. A machine carrying software you cannot remove is one where part of what runs was decided elsewhere.
None of that is an accusation. Remote management exists for dull and legitimate reasons, and a family computer is a family computer. Every later condition here quietly assumes that what happens on this machine is a matter between you and the machine. Wherever somebody else can install, that assumption is false, and no amount of care further along repairs it.
Why nothing sits above this one
This is a root. No arrow arrives here, and that is not an omission. Roots and endings collects the few cards in the same position. A root is a condition the map cannot take apart, because what it rests on is not another condition. It is a fact you walked in with: a physical object, and who administers it.
That has a practical consequence. Everywhere else on the map, a false card can be traced upward to another false card, and repairing the upper one repairs both. Here there is nothing upward. If this condition is false, the repair is a different machine, or a change in who administers this one. How to read a card treats the arrows as load bearing, and this is where that load reaches the floor.
What falls over when the machine is not yours
Four cards hang directly off this one, and they carry most of what follows.
The clock is close enough to right depends on it because a clock is a setting, and settings belong to whoever administers the machine. The time source can be pinned by policy, and a drift you can plainly see may be one you are not permitted to correct. A condition you can observe but cannot change is not a condition you hold.
Losing the device does not lose the account depends on it because a second copy has to be written somewhere. Where removable storage is blocked, or the only permitted destination is a store somebody else runs, the second copy either does not exist or fails at the same moment as the first.
The browser came from the Tor Project depends on it most directly of the four. Provenance is a claim about a file. If another party can write to the disk, the file you checked and the file you launch need not be the same file, and the check described history rather than the present.
A wallet exists and the keys are yours depends on it because key material sits on that disk, and the whole content of that card is that nobody else can move the value without you. A second administrator is a second person who can read that material, and therefore move it.
| Cannot hold | The reason it cannot |
|---|---|
| The clock is close enough to right | A clock you may read but not set is somebody else's clock. |
| Losing the device does not lose the account | A second copy needs write access, which is what a managed machine narrows. |
| The browser came from the Tor Project | Checking a download proves nothing if the installed program can be replaced after. |
| A wallet exists and the keys are yours | Keys are files on that disk, and another administrator is another holder. |
Those four cards are early, so the damage does not stop at them. Everything downstream of them inherits the same falsehood, which is most of the dependency map.
How a borrowed machine actually fails
The failure is quiet, and the quietness is the difficulty. Nothing on the screen changes when a machine is managed. There is no banner. Pages load, downloads finish, the browser opens. The condition is false and the machine behaves as it would if it were true.
What you notice, if anything, arrives out of order. An installer refuses and asks for a password that is not yours, and it reads as a bug rather than as an answer to the question this card asks. A setting reverts overnight and you assume you forgot to save it. A program you removed comes back. Each is the same fact seen through a different crack, and each alone is easy to explain away.
The confusion lands somewhere else. Later, something goes wrong further along, and the reader looks for the cause where the symptom appeared: in the browser, in the address, in the account. If this is false is built around that pattern. A false root does not announce itself at the root. It surfaces several stages away, and attention gets spent in the wrong stage.
A check you can run without asking anyone
Install something small and dull, then take it off again. Both halves matter, because both exercise the permission this card is about.
A pass looks like this. The install completes, and any password you are asked for is your own, known to nobody else. The removal completes too, and nothing quietly returns afterwards. A fail looks like being asked for credentials you do not have, or being told an administrator has blocked the action, or being allowed to install and not to remove.
The second half is enrolment. Every current desktop system lists remote management, device enrolment and the profiles that arrive with them somewhere in its settings. Read it. Empty is a pass. Any entry naming an organisation is a fail. Words used here keeps the vocabulary short. Neither half involves opening any address, because a machine can be questioned on its own.
Control is not safety
A machine you control is not a safe machine, and this card never says it is. It says the floor is yours. A machine you fully administer can still run something you installed and forgot, and it can still sit in a room where the screen is readable from the doorway, which is the separate matter of Nobody else can read the screen. This is the absence of one problem, not the presence of protection.