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 both the server-code (`aaaa…a`) and default user (`lab-1`) match those in R1's repository.
   - The OCX on H2 does not act on R1 because, although its clone has the same server-code (`aaaa…a`), its default user is `lab-1`, not the one specified in R1.

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, the OCX on H3 does not act on R1 because while it shares the same server-code as the repository named in R1, its default user (`lab-9`) does not match that specified in R1.

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 the server received it from a user (`mallory`) who did not send the run (stone).

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?**
   - Yes, the OCX on H1 acts on R2 because both the server-code (`aaaa…a`) and default user (`zed`) match those in R2's repository.
   - No, zed's `started` does not count because it is a report from a user (`zed`) who did not send the run.

5. **Could a run name `"process": {"user": "lab-1"}` and be run? Why?**
   - Yes, a run could name `"process": {"user": "lab-1"}` and be run. The process user is chosen by the sender of the run, and in this case, stone, who has setup capability, can choose any user.

6. **What sets the most that OCX on H1 can do on the server, and who chose it?**
   - The repository's owner chooses what capabilities OCX on H1 can do on the server. Since stone holds setup capability, they chose lab-1 as the default user for this repository.

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$$` refers to the directory within the workspace where a new clone of the repository will be created. It is not the repository named in the run's `repository`.

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 is answered by no one because the server code has changed, so OCX on H1 does not act on it.

9. **Why does a run name `default_user` instead of OCX finding the user from the server-code?**
   - A run names the default user to ensure that only the user who owns the repository can send reports counting for its runs. This avoids unauthorized reports and maintains accountability.

10. **Who may send a `stop` for R1, and which keys does it hold?**
    - Any user holding admin or setup capability, or a user holding `R` that sent the run, may send a `stop`. A stop message holds: `"ocx": 2`, `"kind": "stop"`, and `"run": "the hash of R1 in full"`.