1. OCX on H1 acts on R1, as stone has setup on the server. OCX on H2 ignores R1, as its clone's user is lab-1 but R1 names lab-1.

2. OCX on H3 does not act on R1, as H3's repository's server-code is aaaa…a and its clone's user is lab-9. If H3's clone's user were lab-1, it would act.

3. Yes, mallory's `ended` counts, as it meets all criteria.

4. Yes, stone's `started` counts, as it meets all criteria.

5. OCX on H1 acts on R3 and mallory's `started` counts, as it names lab-1 but is sent by user mallory holding check-in.

6. OCX on H1 does not act on R4, as the process's user builder works for another clone (H2). What it writes does not count.

7. No, a run cannot name "process": {"user": "lab-1"} and be run, as this would violate rule 4.

8. OCX on H2 ignores R5, as its clone server-code is bbbb…b and R5 names lab-1 but is sent by stone holding check-in.

9. OCX on H1 can do "g", "o" and "i". Stone chose it with `poll --login`.

10. $$process_clone$$ is H1's new repository, not the old one named aaaa…a.

11. A new run naming server-code aaaa…a arrives, but OCX on H1 ignores it, as its clone user is lab-1.

12. Only stone or zed may send a `stop` for R1; keys are `ocx`, `kind`, and `run`.