1. **OCX on H1 acts on R1**, while OCX on H2 ignores it because R1's repository has different details (server-code bbbb…b).
2. **OCX on H3 does not act on R1** because the run's default user in R1 (lab-1) differs from the clone's default user (lab-9).
3. **mallory's ended counts**, as it meets all criteria: received by lab-1, names aaaa…a/lab-1, and was not sent by mallory.
4. **OCX on H1 acts on R2** because the run's repository details match H1's clone. zed's started does not count since zed is the sender of R2.
5. **A run could name `"process": {"user": "lab-1"}` and be run**, but it would act as lab-1, not as builder (the process user).
6. **The most OCX on H1 can do** on the server is set by whatever capabilities `lab-1` has, chosen by whoever holds that repository's command line.
7. **$$clone$$ refers to a directory within the workspace**, and it is **not** the same as the repository named in R1's `repository`.
8. **OCX on H1 would ignore the new run**, as its server-code differs from the old one (aaaa…a).
9. **A run names default_user instead of OCX finding the user** because the server records only the user who sent the artifact, and Fossil sync does not send the user information.
10. **A stop for R1 can be sent by anyone holding admin or setup**, but it must hold `ocx`, `kind`, `run` (R1's hash), and `repository` details (server-code aaaa…a, default_user lab-1).