Interpretation of OK on the command completion stream

In a distributed setup, does an OK response on the completion stream mean that the transaction has successfully committed to the network (ie. consensus has happened)? Or does it merely indicate that the command as been successfully validated on my node and has been submitted to the network for committing?

The latter, it means that the command has been validated and executed on the local participant node. A transaction is produced, sent to the ledger for the distributed commit and once the participant receives an update on its status the completion service will tell you the actual outcome.

So I first get an OK upon successful submission and then again OK upon successful transaction commit? Or do they have different status? I thought only one success response is produced per submitted command.

You have a successful result coming back from the submission service and you can observe the successful commit on the completion service.

At least in the happy path, a successful submission of course does not imply a successful completion.

Ok I see. So as per my original question (I specifically ask about the completion stream), the answer is actual the former: an OK on the command completion means the transaction has been committed.

Exactly, that’s why I added the detail that to observe a successful commit you have to track the outcome of the command via the completion service.