1. **Which host's OCX acts on R1, and what does the other host's OCX do with it?**  
   The OCX on H1 acts on R1 because it matches the repository's server-code (`aaaa…a`) and default user (`lab-1`). The OCX on H2 ignores R1 as it does not match its own repository's details.

2. **A third host, H3, has a clone whose server-code is also aaaa…a (its file was copied from H1's) but whose default user is lab-9. Does OCX on H3 act on R1?**  
   No, OCX on H3 does not act on R1 because the repository's default user in H3 (`lab-9`) differs from that specified in R1 (`lab-1`).

3. **mallory, who holds only check-in (i), replies to R1 with an `ended`, `exited`, `exit` 0, naming R1 and repository aaaa…a, lab-1. Does it count?**  
   No, the report does not count because mallory did not send R1; he was receiving it as the run's default user.

4. **zed holds `R`. zed sends a run R2 naming `"repository": {"server_code": "aaaa…a", "default_user": "zed"}`, then posts a `started` for R2 itself. Does OCX on H1 act on R2? Does zed's `started` count?**  
   The OCX on H1 acts on R2 because it matches the repository's server-code (`aaaa…a`) and default user (`zed`). Zed's `started` does not count because it is sent by a user holding the `R` capability, which limits the scope of actions.

5. **Could a run name `"process": {"user": "lab-1"}` and be run? Why?**  
   No, OCX would ignore such a run because it specifies the repository's default user as `lab-1`, not the process user. The process user cannot hold admin or setup.

6. **What sets the most that OCX on H1 can do on the server, and who chose it?**  
   The most that OCX on H1 can do is set by the capabilities of `builder`, as specified in the run's `process`. Zed (who sent the run) chose these capabilities.

7. **A run's workspace has the step `{"step": "clone", "into": "$$workspace$$/clone"}`. What is `$$clone$$`, and is it the repository named in the run's `repository`?**  
   `$$clone$$` is a placeholder that represents the directory where the clone will be created within the workspace. It is not directly the repository specified in the run.

8. **H1's clone is deleted and made again with `fossil clone`. A new run naming the old server-code aaaa…a arrives. What happens?**  
   The new run will be refused by OCX on H1 because it names an outdated server-code, as the repository has been recreated.

9. **Why does a run name `default_user` instead of OCX finding the user from the server-code?**  
   A run specifies its default user to ensure that only authorized users can send reports for the run, preventing unauthorized actions based on server-code alone.

10. **Who may send a `stop` for R1, and which keys does it hold?**  
    Only a user holding admin or setup, or the user who sent R1 (stone in this case), may send a `stop`. The `stop` message holds `ocx`, `kind`, and `run`, with `run` being the hash of the forum post or ticket change containing the run.