Publishing a Vv is "final" in that you won't be able to edit (change the content or annotations of) that particular Vv after publishing. This is akin to printing out a large sheet of paper.
Once it's printed...
... it's printed.
Think of a published Vv as a snapshot of your work, no matter what stage it's at. A Vv is a snapshot that you want to share and get feedback on.
As an example, suppose that you want to get feedback on your early progress from a few folks. Go ahead and publish your Vv (ideally with appropriate annotations). Make sure that the folks you want to get feedback from are added to the project as one of the end-user roles (Stakeholder or Viewer). When you publish the Vv, they will get an email inviting them to experience your designs in an immersive way, from the comfort of their own phone.
When it's time to incorporate their feedback, you can either start with a brand-new, fresh Vv, populated with new images and annotations, or you can build off of the Vv you already published. To start with the existing Vv, go back to the web portal and duplicate the Vv. All of the images and text descriptions will be copied over. Voice+ gaze annotations will not be copied over with the duplicated Vv as annotations are typically fine tuned for a particular project snapshot.
After making needed changes to the duplicated Vv, add new annotations, and publish to the appropriate set of end-users.
If you are finding that you want to share early stage, in process Vvs with your co-workers, while you are still fine-tuning the content, you can invite your co-workers to be project owners (instead of Stakeholders or Viewers). Project owners for your project are able to open Vvs that are in Annotate mode, before they are published.
For more information: