### 1.
- **H1's OCX acts on R1** because H1's clone matches both the server-code (`aaaa…a`) and default user (`lab-1`) specified in R1. 
- **H2's OCX ignores R1** since it does not match its own repository details.

### 2.
- **OCX on H3 does not act on R1** because although it has a clone with the same server-code, the default user is different (`lab-9` instead of `lab-1`).

### 3.
- **The ended message does not count**. It comes from `mallory`, who holds only check-in capability (`i`). Since `mallory` did not send R1 and the OCX cannot validate that the report came from the correct default user (though it's supposed to be lab-1), it is ignored.

### 4.
- **OCX on H1 does not act on R2** because the repository's default user in R2 (`zed`) differs from the default user of H1's clone (`lab-1`).
- **Zed's started message does not count**. It comes from `zed`, who holds only check-in capability (`i`). Since `zed` did not send R2 and the OCX cannot validate that the report came from the correct default user (though it's supposed to be lab-1), it is ignored.

### 5.
- **A run naming `"process": {"user": "lab-1"}` could be run**. This is because the server-code in R1 matches H1's repository, and the process user (`builder`) is not restricted by R1's capability requirements (since it does not name a default user that would hold admin or setup).

### 6.
- **The most OCX on H1 can do on the server** is determined by the capabilities of `lab-1`, who holds the repository's command line. This choice was made by whoever has that repository's command line.

### 7.
- **$$clone$$ refers to a directory named "clone" within the workspace**, and it is not the repository named in R1's `repository`.

### 8.
- **A new run naming the old server-code (`aaaa…a`) arrives**. OCX on H1 ignores this run because its default user (lab-9) differs from the default user specified in R1 (`lab-1`).

### 9.
- **A run names `default_user` instead of OCX finding it from the server-code** to ensure that only a specific user can validate and accept reports for that repository. This allows better control over who can submit results.

### 10.
- **Only users holding admin or setup, or the user holding `R` that sent R1**, can send a `stop` for R1. The `stop` message must include:
  - `"ocx": 2`
  - `"kind": "stop"`
  - `"run"` (the hash of R1)