Seven questions, for people and agents, to check your reading of OCX's words; nothing requires it, and no score is kept (the maintainer, 2026-10-16: "always opt-in to a refresher"). Each answer links to the definition, which wins where they differ.

Questions

1. Where may a run be written?

• a. Only as a thread's first post.
• b. In any forum post, first or reply, or ticket change, as an OCX message whose kind is run.
• c. Only in a wiki page run/NAME.
• d. Only in a post its node writes.

2. A running session's hears names you; you are neither its run's user nor a node user, and you post unmoderated. You reply anywhere in its thread, with no OCX message. Who may read your reply, and is the session given it?

• a. Only the session.
• b. Every user who may read the forum; the session is given it if its node pulls it whole and its watcher passes it.
• c. Only you, until the node accepts it.
• d. Every user; the session is given it only if you reply to the run's post.

3. A daemon serves a node's clone. An admin posts a nonmanual run for it on Fossil's forum page. What has the node act on it?

• a. OCX's after-receive hook.
• b. Fossil's chat answer wakes the daemon; it pulls whole, checks the server's receipts and hands the run to a watcher.
• c. Nothing until the admin calls ocx2 run.
• d. A watcher already waiting for new runs.

4. A run that is not a session runs make test, with limits {"wall": "1h"}. How long does its watcher live?

• a. As long as the daemon that started it.
• b. Until make test exits, a stop, or the hour passes; then it writes ended and exits.
• c. As long as its host is up.
• d. Until an admin stops the run.

5. A run/mcp-tunnel run, offering OCX's tools to a remote agent, started under release A; then release B, adding tools, is accepted. Which tools does it offer?

• a. B's, at once.
• b. A's, for as long as this run lasts.
• c. None, until the server restarts.
• d. B's, after the node's next check.

6. A run names a node on a build machine. How does that node learn of the run?

• a. The server pushes it.
• b. The server's hook calls it.
• c. The machine's daemon pulls its clone after a chat answer and decides.
• d. A watcher on the server forwards it.

7. An agent's run checks out trunk; the agent has not saved yet. Where can you read the branch save will commit on?

• a. In the run's message.
• b. In the run's started, among its values.
• c. From context, called in that checkout.
• d. Nowhere: save picks it at random.

Answers

1. b. A run is any OCX message whose kind is run; a run/NAME page holds a pattern (GLOSSARY.md, "Run").
2. b. Users holding 2 read forum posts; a session is given what passes its subscription, as its node acts on it (GLOSSARY.md, "Forum thread", "Subscription", "Delivery").
3. b. The daemon pulls whole and the watcher decides again under the run lock (How a post reaches an agent).
4. b. A watcher exits once its process exits, is stopped or passes a limit (GLOSSARY.md, "Watcher").
5. b. B reaches the tunnel only with another run (GLOSSARY.md, "Release"; remote-agents.md, "The pattern run/mcp-tunnel").
6. c. The daemon pulls before deciding, at start and after each chat answer (GLOSSARY.md, "Node").
7. c. No run or started names the working branch; context shows it (GLOSSARY.md, "Working branch").