1. OCX on H1 acts on R1 because the run's `clone.server_code` and `clone.user` match H1's repository and user. OCX on H2 does nothing because the run's `clone.server_code` (`aaaa…a`) does not match H2's server-code (`bbbb…b`).

2. OCX on H3 does not act on R1 because the run's `clone.user` (`lab-1`) does not match H3's clone user (`lab-9`). If H3's clone user were `lab-1`, it would act because both the server-code and the user would match.

3. It does not count because the server's receipt names Mallory as the sender, but an `ended` message only counts if the receipt names the run's `clone.user` (`lab-1`) as the sender.

4. It does not count because the server's receipt names Stone as the sender, but a `started` message only counts if the receipt names the run's `clone.user` (`lab-1`) as the sender.

5. OCX on H1 does not act on R3 because the run's `clone.user` (`mallory`) does not match H1's clone user (`lab-1`). Mallory's `started` does not count because it must be sent by the run's `clone.user` and the run's sender must be a different user holding admin, setup, or `R`.

6. OCX on H1 ends the run as `refused` because Mallory does not hold admin, setup, or `R` on the server. This refusal counts because it is written as the run's `clone.user` (`lab-1`), satisfying the counting rules for `ended` messages.

7. No, because refusal 4 holds: the `process.user` cannot be the run's `clone.user` or any other clone's user. `lab-1` is already the clone's user for H1 and H2.

8. OCX on H2 refuses the run because of refusal 5. The `process.user` (`builder`) already works for the clone with server-code `aaaa…a` from run R1, and a process's user works for only one clone.

9. The capabilities of the clone's user (`lab-1`) on the server set the limit of what OCX on H1 can do. The clone's owner chose this user via `poll --login`.

10. `$$process_clone$$` is the repository created from the server's repository during the workspace's `clone` step. It is not the repository named in the run's `clone` key, as the process's clone is never the run's clone.

11. OCX on H1 will not act on the run because a repository made again by `fossil clone` gets a new server-code. The sender must send the run again using the new server-code.

12. A user holding admin or setup on the server, or the user holding `R` who sent the run, may send a `stop`. The message holds the keys `ocx`, `kind`, and `run`.