Explanation pattern

Start with what happens or what the user should understand. Follow with one concrete example, then the mechanism and only the details needed to assess it. Name important uncertainty and a useful next action.

Example:

“The website sends instructions to your PC through a private queue. Your PC runs the installed CLI. If the PC is off, the instruction waits; closing the browser does not necessarily stop an already-running task.”

Then, if needed, map browser → durable command → companion → local file/CLI → evidence → owner review. Cite source paths for repository-specific claims. Explain what a connection badge, acknowledgement and passed check each prove rather than collapsing them into one success state.

For requested retained documentation use DOC with kind=explanation, source links, last verified evidence and freshness. Otherwise answer in chat. Do not create a file merely to make the explanation appear more substantial.