1. OCX on H1 acts on R1 because its `clone.server_code` (`aaaa…a`) matches its own repository's server-code, and its `clone.user` (`lab-1`) is the same as the user it acts as. OCX on H2 does nothing with it since it doesn't match either condition.
2. OCX on H3 does not act on R1 because its `clone.server_code` (`aaaa…a`) matches, but its `clone.user` (`lab-9`) is different from the run's `clone.user` (`lab-1`). If H3's clone's user were lab-1, it would act.
3. Yes, mallory's `ended` counts because it meets all requirements for counting as per rule 3 of section 2.4.
4. Yes, stone's `started` counts because it meets all requirements for counting as per rule 3 of section 2.4.
5. OCX on H1 does not act on R3 since the process's user (`builder`) is a clone's user (lab-1). Mallory's `started` does not count because it doesn't meet the criteria for counting.
6. OCX on H1 does nothing with R4, and what it writes counts as per refusal 5 of section 2.14.
7. No, stone cannot name `"process": {"user": "lab-1"}` and have it run due to refusal 4 of section 2.14.
8. OCX on H2 does nothing with R5, and what it writes counts as per refusal 5 of section 2.14.
9. The most OCX on H1 can do on the server is `g`, `o` and `i`, which was chosen by the user who made the clone (lab-1).
10. $$process_clone$$ is `./clone`, and it is not the repository R1's key `clone` names.
11. OCX on H1 acts on the new run because its server-code matches, but its clone's user must be lab-1 for the sender to count.
12. Only a user holding admin or setup may send a `stop`, and it holds only `ocx` and `kind`.